Re: Re: [PATCH 5/6]ACPI based Physical CPU hotplug

[Keshavamurthy Anil S <anil.s.keshavamurthy-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>]

On Thu, Sep 09, 2004 at 11:40:03PM +0300, Mika Penttil? wrote:
> I don't see how the acpi_processor_start() stuff (which was formerly in 
> acpi_processor_add()) gets executed in the plain non-hotplug case. It's 
> only called from the hotplug notifications.
Hi Mika,
	Firstly thanks for your time looking at the code and let me clarify you concerns.
If you look at acpi_bus_driver_init() function from where the ops.add() is getting called, 
once the ops.add() gets passed, and if the driver has .start function defined 
then ops.start() is called. In our case the processor driver is setting
.start to acpi_processor_start function in its acpi_processor_driver structure.

Let me know if you have any other concerns.

Thanks,
Anil Keshavamurthy



-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. 
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php