Re: [PATCH 2.6.20] tasks cannot run on cpus onlined after boot

[Ingo Molnar]

* Nathan Lynch <ntl@xxxxxxxxx> wrote:

> Commit 5c1e176781f43bc902a51e5832f789756bff911b ("sched: force
> /sbin/init off isolated cpus") sets init's cpus_allowed to a subset of
> cpu_online_map at boot time, which means that tasks won't be scheduled
> on cpus that are added to the system later.
> 
> Make init's cpus_allowed a subset of cpu_possible_map instead.  This 
> should still preserve the behavior that Nick's change intended.
> 
> Thanks to Giuliano Pochini for reporting this and testing the fix:
> 
> http://ozlabs.org/pipermail/linuxppc-dev/2006-December/029397.html
> 
> Signed-off-by: Nathan Lynch <ntl@xxxxxxxxx>

nicely spotted!

> -	cpus_andnot(non_isolated_cpus, cpu_online_map, cpu_isolated_map);
> +	cpus_andnot(non_isolated_cpus, cpu_possible_map, cpu_isolated_map);

Acked-by: Ingo Molnar <mingo@xxxxxxx>

	Ingo
-
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/