xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Liu, Jinsong" <jinsong.liu@intel.com>,
	"Jiang, Yunhong" <yunhong.jiang@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 10:03:04 +0000	[thread overview]
Message-ID: <C79AD7D8.9F6E%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <EB8593BCECAB3D40A8248BE0B6400A3845F38F1F@shzsmsx502.ccr.corp.intel.com>

On 12/02/2010 09:50, "Liu, Jinsong" <jinsong.liu@intel.com> wrote:

>> 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
> 
> Yes, we hope so :)
> Compared with linux 2.6.30, 2.6.32 change a lot at processor_hotplug path, but
> still not clean to support \_PR processor, while both versions seems work well
> for \_SB processor. Win2k8 is similar situation.

Win2k8 has a similar problem?

 -- Keir

  reply	other threads:[~2010-02-12 10:03 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
2010-02-12  9:38           ` Jiang, Yunhong
2010-02-12  9:50           ` Liu, Jinsong
2010-02-12 10:03             ` Keir Fraser [this message]
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=C79AD7D8.9F6E%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).