From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Liu, Jinsong" Subject: RE: [PATCH] Fix hvm vcpu hotplug bug Date: Sun, 22 Aug 2010 13:00:46 +0800 Message-ID: References: <19554.43920.11785.97567@mariner.uk.xensource.com> <19563.58860.249044.209893@mariner.uk.xensource.com> <19565.17092.616097.195948@mariner.uk.xensource.com> <19566.33227.5055.515834@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <19566.33227.5055.515834@mariner.uk.xensource.com> Content-Language: en-US List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Jackson Cc: "Jiang, Yunhong" , Keir Fraser , "xen-devel@lists.xensource.com" , "Li, Xin" List-Id: xen-devel@lists.xenproject.org Ian Jackson wrote: > Liu, Jinsong writes ("RE: [Xen-devel] [PATCH] Fix hvm vcpu hotplug > bug"):=20 >> ospm will do. Its sequence is (i.e. linux 2.6.32, ospm dispatch >> control method case) >=20 > "ospm" is "OS power management" ie in our case the guest kernel I take > it ? hmm, 'ospm' is just a generial speaking, more accurate speaking is 'acpica'= . i.e. hvm linux 2.6.32 handle sci/gpe at: drivers/acpi/acpica/evsci.c drivers/acpi/acpica/evgpe.c >=20 >> 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; >=20 > So the code in qemu should never clear gpe_sts itself. >=20 > Ian. No, that's just what qemu should do, to simulate hardware behavior. Thanks, Jinsong