WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] please revert c/s 17686

To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>, "Jan Beulich" <jbeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] please revert c/s 17686
From: "Wei, Gang" <gang.wei@xxxxxxxxx>
Date: Fri, 13 Jun 2008 21:12:15 +0800
Cc: "Yu, Ke" <ke.yu@xxxxxxxxx>
Delivery-date: Fri, 13 Jun 2008 06:12:47 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C477ED5C.19C30%keir.fraser@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <48524817.76E4.0078.0@xxxxxxxxxx> <C477ED5C.19C30%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcjNLu7hLVdb1TkiEd2YlgAWy6hiGQAJ9npg
Thread-topic: [Xen-devel] please revert c/s 17686
On Friday, June 13, 2008 4:25 PM, Keir Fraser wrote:
> On 13/6/08 09:12, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:
> 
>>>> I missed that warning printk. It does indeed look odd.
>>> 
>>> As to this warning printk, we can simply replace it with an assert.
>> 
>> That would make things worse, not better - the condition simply must
be
>> allowed (as said before, otherwise you won't be able to bring all
CPUs
>> at once into C3).
> 
> I think that C2/C3 are entered with IRQs disabled, but IRQ pending
will
> kick the CPU out of C2/C3 nonetheless. That CPU will then execute
> hpet_broadcast_exit() before local_irq_enable() and hence the warning
> printk will never actually fire. So it would be correct as a BUG_ON().
> 
> Is this correct, Wei?

Absolutely right. And we will look into whether it is better to move
hpet_broadcast_exit() after local_irq_enable().

Jimmy

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>