[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] [PATCH] Add cpu hotplug support for 2.6.32 branch


  • To: Jan Beulich <JBeulich@xxxxxxxxxx>
  • From: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
  • Date: Thu, 19 Aug 2010 13:02:10 +0800
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Wed, 18 Aug 2010 22:03:14 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acs+u1Oe3AQ2bDhZT862sjVjAaHVrgAiaFXw
  • Thread-topic: [Xen-devel] [PATCH] Add cpu hotplug support for 2.6.32 branch

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@xxxxxxxxxx]
>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@xxxxxxxxx> 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


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.