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] [PATCH] Fix hvm vcpu hotplug bug

To: "Liu, Jinsong" <jinsong.liu@xxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] Fix hvm vcpu hotplug bug
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Fri, 20 Aug 2010 14:23:23 +0100
Cc: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Li, Xin" <xin.li@xxxxxxxxx>
Delivery-date: Fri, 20 Aug 2010 06:24:13 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BC00F5384FCFC9499AF06F92E8B78A9E16509730BB@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
Newsgroups: chiark.mail.xen.devel
References: <BC00F5384FCFC9499AF06F92E8B78A9E0B0007FD20@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <19554.43920.11785.97567@xxxxxxxxxxxxxxxxxxxxxxxx> <BC00F5384FCFC9499AF06F92E8B78A9E164C8CB703@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <19563.58860.249044.209893@xxxxxxxxxxxxxxxxxxxxxxxx> <BC00F5384FCFC9499AF06F92E8B78A9E165097298D@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <19565.17092.616097.195948@xxxxxxxxxxxxxxxxxxxxxxxx> <BC00F5384FCFC9499AF06F92E8B78A9E16509730BB@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Liu, Jinsong writes ("RE: [Xen-devel] [PATCH] Fix hvm vcpu hotplug bug"):
> ospm will do. Its sequence is (i.e. linux 2.6.32, ospm dispatch
> control method case)

"ospm" is "OS power management" ie in our case the guest kernel I take
it ?

> 1). clear pge_en x by writing '0' to the bit;
> 2). asynchronic call control method;
> 3). clear gpe_sts x by writing '1' to the bit;
> 4). re-enable gpe_en x by writing '1' to the bit;

So the code in qemu should never clear gpe_sts itself.

Ian.

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