All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jiang, Yunhong" <yunhong.jiang@intel.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	Xen-devel <xen-devel@lists.xensource.com>
Subject: RE: [PATCH] Add cpu hotplug support for 2.6.32	 branch
Date: Thu, 19 Aug 2010 13:02:10 +0800	[thread overview]
Message-ID: <789F9655DD1B8F43B48D77C5D306597329D953BD@shsmsx501.ccr.corp.intel.com> (raw)
In-Reply-To: <4C6BCA050200007800010996@vpn.id2.novell.com>

In .32 both the hotplug through container/processor will all go-through the acpi_bus_add =>acpi_processor_driver.add, so we only need change the .add function to achive the purpose.

After checking the code, I think in .31 kernel, the changes to the acpi_processor_hotplug_notify() code path is not needed.

Thanks
--jyh

>-----Original Message-----
>From: Jan Beulich [mailto:JBeulich@novell.com]
>Sent: Wednesday, August 18, 2010 5:55 PM
>To: Jiang, Yunhong
>Cc: Jeremy Fitzhardinge; Xen-devel
>Subject: Re: [Xen-devel] [PATCH] Add cpu hotplug support for 2.6.32 branch
>
>>>> On 18.08.10 at 05:04, "Jiang, Yunhong" <yunhong.jiang@intel.com> wrote:
>> Add cpu hotplug support for 2.6.32 branch
>>
>> Add physical CPU hotplug support to origin/xen/next-2.6.32 branch.
>
>What is the reason this is no longer done through the
>acpi_processor_hotplug_notify() code path?
>
>Jan

  reply	other threads:[~2010-08-19  5:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18  3:04 [PATCH] Add cpu hotplug support for 2.6.32 branch Jiang, Yunhong
2010-08-18  9:54 ` Jan Beulich
2010-08-19  5:02   ` Jiang, Yunhong [this message]
2010-08-18 19:41 ` Jeremy Fitzhardinge
2010-08-20  3:45   ` Jiang, Yunhong
2010-08-21  0:45     ` Jeremy Fitzhardinge
2010-08-23  3:02       ` Jiang, Yunhong

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=789F9655DD1B8F43B48D77C5D306597329D953BD@shsmsx501.ccr.corp.intel.com \
    --to=yunhong.jiang@intel.com \
    --cc=JBeulich@novell.com \
    --cc=jeremy@goop.org \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.