On Thursday 02 April 2009 06:23:16 pm Yasunori Goto wrote: > > On Thursday 02 April 2009 07:56:28 am Thomas Renninger wrote: > > > I remember these two guys helped me testing on memory hotplug. > > > They only had a simulator, but might want to give the latest kernel a try if > > > you come to clean up acpi_memhotplug.c: > > > kamezawa.hiroyu@xxxxxxxxxxxxxx > > > Yasunori Goto <y-goto@xxxxxxxxxxxxxx> > > I can use real machine which can memory hotplug. > In our case, notify method is called for container device (NUMA node), > and memory and processor devices are added under acpi_bus_scan(). > > I'll book it to test this patch in next week. > It must be good test. :-) Thomas is right; I don't think it's worth your time to do much testing right now. These patches only affect device notifications, and I think the container/memory/processor stuff you're referring to depends on the system notifications. So this series should not affect the hotplug path. I am working on some changes to the hotplug path, but that looks much more difficult, so it'll probably be a while before anything comes of it. Thanks for the tip; I'll make sure to CC: you when I post patches. Bjorn -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
