From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Jiang, Yunhong" <yunhong.jiang@intel.com>,
"Liu, Jinsong" <jinsong.liu@intel.com>,
xen-devel <xen-devel@lists.xensource.com>
Subject: Re: RE: [PATCH 1/2] Vcpu hotplug: Move ACPI processor from \_PR to \_SB
Date: Fri, 12 Feb 2010 08:30:10 +0000 [thread overview]
Message-ID: <C79AC212.9EAA%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <C8EDE645B81E5141A8C6B2F73FD926511BA551B8DB@shzsmsx501.ccr.corp.intel.com>
On 12/02/2010 02:57, "Jiang, Yunhong" <yunhong.jiang@intel.com> wrote:
> However, according to ACPI spec, the _PR is for ACPI1.0 compatible. We have no
> idea which OS is ACPI 1.0 OS. As HeQing found ACPI 1.0 bugs in Win2K, so we
> assume W2K is ACPI 1.0. We test shows W2K guest is ok with the _SB definition
> in our testing. Maybe Win98/WinMe is ACPI 1.0, but we have no image for these
> OS. But yes, that's a main issue for _SB method and we need more consideration
> here.
>
> In fact, we have internal argue to choose _PR or _SB method before Jinsong's
> initial patch sent out. Later _PR method is chosen because of the ACPI 1.0
> compatible benifit, and kernel 30 version is ok. (IIRC, .32 kernel is not
> released at that time).
Well, that's tricky. 2.6.32 is supposed to be a long-term maintained kernel,
so presumably there will be a 2.6.32.x along in the not-too-far future which
fixes this Linux bug? I feel we're a bit close to the wire to make this
change now.
I'd be a bit more comfortable if we had the cover of lots of other modern
systems putting their processor objects under \_SB, but actually I've never
seen one. Then again I haven't been looking at high-end systems supporting
CPU hotplug and the like.
-- Keir
next prev parent reply other threads:[~2010-02-12 8:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 17:38 [PATCH 1/2] Vcpu hotplug: Move ACPI processor from \_PR to \_SB Liu, Jinsong
2010-02-11 18:36 ` Keir Fraser
2010-02-12 2:57 ` Jiang, Yunhong
2010-02-12 8:30 ` Keir Fraser [this message]
2010-02-12 9:25 ` Jiang, Yunhong
2010-02-12 9:30 ` Keir Fraser
2010-02-12 9:38 ` Jiang, Yunhong
2010-02-12 9:50 ` Liu, Jinsong
2010-02-12 10:03 ` Keir Fraser
2010-02-12 10:07 ` Liu, Jinsong
2010-02-12 10:29 ` Keir Fraser
2010-02-12 20:46 ` Liu, Jinsong
2010-02-12 21:57 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C79AC212.9EAA%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=jinsong.liu@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=yunhong.jiang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).