Re: [PATCH] x86: correct socket_cpumask allocation for AP

[Chao Peng <chao.p.peng@linux.intel.com>]

On Wed, Jul 08, 2015 at 05:32:11PM +0100, Jan Beulich wrote:
> >>> On 08.07.15 at 18:17, <dario.faggioli@citrix.com> wrote:
> > I think it has to do with the fact that I've got CPU #0 on socket #1,
> > while Boris' (and perhaps Chao's too) test box have it on socket #0.
> 
> Ah, yes, this is indeed a case I didn't consider when validating
> Chao's analysis.

I apologize, this is what I have made the wrong assumption on
from the beginning. While looks the fix is simple, just change
'zalloc_cpumask_var(socket_cpumask)' to
'zalloc_cpumask_var(socket_cpumask + cpu_to_socket(0))'
for booting cpu in smp_prepare_cpus().

Chao