Re: [RFC PATCH V2 1/2] x86/cpu hotplug: make apicid <--> cpuid mapping persistent

ping... Any comments or suggestions are welcomed. Regards, Gu On 05/14/2015 07:33 PM, Gu Zheng wrote: > Yasuaki Ishimatsu found that with node online/offline, cpu<->node > relationship is established. Because workqueue uses a info which > was established at boot time, but it may be changed by n

Re: [RFC PATCH V2 1/2] x86/cpu hotplug: make apicid <--> cpuid mapping persistent

Hi Ishimatsu, On 05/15/2015 12:44 AM, Yasuaki Ishimatsu wrote: > Hi Gu, > > Before 8 months, I posted the following patch to relate > cpuid to apicid. > > https://lkml.org/lkml/2014/9/3/1120 > > Could you try this patch? Thanks for your reminder. It seems similar to the https://lkml.org/lkml

Re: [RFC PATCH V2 1/2] x86/cpu hotplug: make apicid <--> cpuid mapping persistent

Hi Gu, Before 8 months, I posted the following patch to relate cpuid to apicid. https://lkml.org/lkml/2014/9/3/1120 Could you try this patch? Thanks, Yasuaki Ishimatsu On Thu, 14 May 2015 19:33:33 +0800 Gu Zheng wrote: > Yasuaki Ishimatsu found that with node online/offline, cpu<->node > rel

[RFC PATCH V2 1/2] x86/cpu hotplug: make apicid <--> cpuid mapping persistent

Yasuaki Ishimatsu found that with node online/offline, cpu<->node relationship is established. Because workqueue uses a info which was established at boot time, but it may be changed by node hotpluging. Once pool->node points to a stale node, following allocation failure happens. == SLUB: U