Re: [RESEND PATCH v5 5/5] x86, acpi, cpu-hotplug: Set persistent cpuid <-> nodeid mapping when booting.

2016-03-02 Thread Zhu Guihua
On 03/03/2016 10:11 AM, kbuild test robot wrote: Hi Gu, [auto build test ERROR on tip/x86/core] [also build test ERROR on v4.5-rc6 next-20160302] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url:

Re: [RESEND PATCH v5 5/5] x86, acpi, cpu-hotplug: Set persistent cpuid <-> nodeid mapping when booting.

2016-03-02 Thread Zhu Guihua
On 03/03/2016 10:11 AM, kbuild test robot wrote: Hi Gu, [auto build test ERROR on tip/x86/core] [also build test ERROR on v4.5-rc6 next-20160302] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url:

Re: [RESEND PATCH v5 5/5] x86, acpi, cpu-hotplug: Set persistent cpuid <-> nodeid mapping when booting.

2016-03-02 Thread kbuild test robot
Hi Gu, [auto build test ERROR on tip/x86/core] [also build test ERROR on v4.5-rc6 next-20160302] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url:

Re: [RESEND PATCH v5 5/5] x86, acpi, cpu-hotplug: Set persistent cpuid <-> nodeid mapping when booting.

2016-03-02 Thread kbuild test robot
Hi Gu, [auto build test ERROR on tip/x86/core] [also build test ERROR on v4.5-rc6 next-20160302] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url:

[RESEND PATCH v5 5/5] x86, acpi, cpu-hotplug: Set persistent cpuid <-> nodeid mapping when booting.

2016-03-02 Thread Zhu Guihua
From: Gu Zheng The whole patch-set aims at making cpuid <-> nodeid mapping persistent. So that, when node online/offline happens, cache based on cpuid <-> nodeid mapping such as wq_numa_possible_cpumask will not cause any problem. It contains 4 steps: 1. Enable apic

[RESEND PATCH v5 5/5] x86, acpi, cpu-hotplug: Set persistent cpuid <-> nodeid mapping when booting.

2016-03-02 Thread Zhu Guihua
From: Gu Zheng The whole patch-set aims at making cpuid <-> nodeid mapping persistent. So that, when node online/offline happens, cache based on cpuid <-> nodeid mapping such as wq_numa_possible_cpumask will not cause any problem. It contains 4 steps: 1. Enable apic registeration flow to handle

[PATCH v5 5/5] x86, acpi, cpu-hotplug: Set persistent cpuid <-> nodeid mapping when booting.

2016-01-20 Thread Tang Chen
From: Gu Zheng The whole patch-set aims at making cpuid <-> nodeid mapping persistent. So that, when node online/offline happens, cache based on cpuid <-> nodeid mapping such as wq_numa_possible_cpumask will not cause any problem. It contains 4 steps: 1. Enable apic registeration flow to handle

[PATCH v5 5/5] x86, acpi, cpu-hotplug: Set persistent cpuid <-> nodeid mapping when booting.

2016-01-20 Thread Tang Chen
From: Gu Zheng The whole patch-set aims at making cpuid <-> nodeid mapping persistent. So that, when node online/offline happens, cache based on cpuid <-> nodeid mapping such as wq_numa_possible_cpumask will not cause any problem. It contains 4 steps: 1. Enable apic