Re: Lockdep warning with init_espfix_ap()

[H. Peter Anvin]

On 10/15/2014 09:03 AM, Prarit Bhargava wrote:
>>
>> It is kind of a messy situation, because this code needs to allocate
>> memory but is run before the secondary CPU is fully up.  As such, it is
>> a false positive, at least in some ways.
> 
> Interesting -- FWIW, I can reproduce this 100% of the time on _one_ system.  It
> isn't a big deal and likely just worth noting at this point.  I *always* see it
> when bringing up CPU 64 (of 128).
> 

... because that is the first CPU which needs to allocate memory.

	-hpa


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