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 09:30:56 +0000 [thread overview]
Message-ID: <C79AD050.9EBB%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <C8EDE645B81E5141A8C6B2F73FD926511BFBA581F6@shzsmsx501.ccr.corp.intel.com>
On 12/02/2010 09:25, "Jiang, Yunhong" <yunhong.jiang@intel.com> wrote:
>> 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.
>
> Yes. I only saw \_SB definition in system supporting CPU hotplug. In fact, in
> that system, the processor is defined under an container object in \_SB. As
> currently all system in our lab is shutdown for CNY, I can't find more system
> to check. And I suspect that we need care \_PR soluation, legacy OS support is
> an important usage model for virtualization.
>
> One thing I noticed in my system is, there is a ACPI version option in my
> desktop system, and I remember I saw that option in other system also. So one
> possible solution is, place all processor definition under a seperated SSDT
> file. An option is provided so that build.c can select different SSDT based on
> user's input. But that make thing tricky still.
You can see that xen-unstable tip can do this now. But I don't want to start
dumping in loads of alternative DSDTs, as each one is a fair size. What I'm
hoping is that this Linux regression is fixed fairly swiftly, and we can
hence ignore it. :-) If not, we can think about what to do.
-- Keir
next prev parent reply other threads:[~2010-02-12 9: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
2010-02-12 9:25 ` Jiang, Yunhong
2010-02-12 9:30 ` Keir Fraser [this message]
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=C79AD050.9EBB%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).