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

[Xen-devel] RE: [PATCH 1/4] x86/HPET: fix initialization order

To: Jan Beulich <JBeulich@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] RE: [PATCH 1/4] x86/HPET: fix initialization order
From: "Wei, Gang" <gang.wei@xxxxxxxxx>
Date: Sat, 12 Mar 2011 17:29:12 +0800
Accept-language: zh-CN, en-US
Acceptlanguage: zh-CN, en-US
Cc: "Wei, Gang" <gang.wei@xxxxxxxxx>
Delivery-date: Sat, 12 Mar 2011 01:30:04 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D7A4ED60200007800035EA1@xxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4D7A4ED60200007800035EA1@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcvgAYvdqoe8k29vSMKVVsENdAXBLAAlCsGQ
Thread-topic: [PATCH 1/4] x86/HPET: fix initialization order
Jan Beulich wrote on 2011-03-11:
> At least the legacy path can enter its interrupt handler callout while 
> initialization is still in progress - that handler checks whether
> ->event_handler is non-NULL, and hence all other initialization must
> happen before setting this field.
> 
> Do the same to the MSI initialization just in case (and to keep the code in 
> sync).
> 
> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>

Acked-by: Wei Gang <gang.wei@xxxxxxxxx>

The only bogus case for old code should be: one PIT interrupt came to a 
non-boot cpu before the boot cpu changes HPET to legacy mode, and this PIT 
interrupt was pending until boot cpu initialized the .event_handler with the 
spin lock & rw lock uninitialized. But it is still a possible bug. I support 
make the fix go into 4.1 and 4.0.

Jimmy

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

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