Re: [PATCH 14/14] cpumask: don't recommend set_cpus_allowed hackin Documentation/cpu-hotplug.txt

[Gautham R Shenoy]

Hi Rusty,

On Tue, Nov 03, 2009 at 02:59:06PM +1030, Rusty Russell wrote:
> Signed-off-by: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
> Cc: Gautham R Shenoy <ego@xxxxxxxxxx>
> Cc: Ashok Raj <ashok.raj@xxxxxxxxx>
> ---
>  Documentation/cpu-hotplug.txt |   49 ++++++++++++++----------------------------
>  1 file changed, 17 insertions(+), 32 deletions(-)
> 
> diff --git a/Documentation/cpu-hotplug.txt b/Documentation/cpu-hotplug.txt
> --- a/Documentation/cpu-hotplug.txt
> +++ b/Documentation/cpu-hotplug.txt
> @@ -309,41 +309,26 @@ A: The following are what is required fo
> 
>  Q: I need to ensure that a particular cpu is not removed when there is some
>     work specific to this cpu is in progress.
> -A: First switch the current thread context to preferred cpu
> +A: There are two ways.  If your code can be run in interrupt context, use
> +   smp_call_function_single(), otherwise use work_on_cpu().  Note that
> +   work_on_cpu() can fail due to out of memory:
> 
>  	int my_func_on_cpu(int cpu)
>  	{
> +		int err;
> +		cpu_hotplug_lock();
		^^^^^^^^^^^^^^^^^^^
This needs to be get_online_cpus();
> +		if (!cpu_online(cpu))
> +			err = -EINVAL;
> +		else
> +#if NEEDS_BLOCKING
> +			err = work_on_cpu(cpu, __my_func_on_cpu, NULL);
> +#else
> +			smp_call_function_single(cpu, __my_func_on_cpu, &err,
> +						 true);
> +#endif
> +		cpu_hotplug_unlock();
		^^^^^^^^^^^^^^^^^^^^^
And this one should be put_online_cpus();

> +		return err;
> +	}
> 
>  Q: How do we determine how many CPUs are available for hotplug.
>  A: There is no clear spec defined way from ACPI that can give us that

-- 
Thanks and Regards
gautham
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/