Re: [PATCH v2 2/2] x86, apic: Disable BSP if boot cpu is AP

2013-10-22 Thread HATAYAMA Daisuke
(2013/10/19 2:36), Vivek Goyal wrote: On Wed, Oct 16, 2013 at 10:26:44AM +0900, HATAYAMA Daisuke wrote: [..] I am wondering if there is any attribute of cpu which we can pass to second kernel on command line. And tell second kernel not to bring up that specific cpu. (Say exclude_cpu=)? If this

Re: [PATCH v2 2/2] x86, apic: Disable BSP if boot cpu is AP

2013-10-22 Thread HATAYAMA Daisuke
(2013/10/19 2:36), Vivek Goyal wrote: On Wed, Oct 16, 2013 at 10:26:44AM +0900, HATAYAMA Daisuke wrote: [..] I am wondering if there is any attribute of cpu which we can pass to second kernel on command line. And tell second kernel not to bring up that specific cpu. (Say exclude_cpu=cpu_attr)?

Re: [PATCH v2 2/2] x86, apic: Disable BSP if boot cpu is AP

2013-10-18 Thread Vivek Goyal
On Wed, Oct 16, 2013 at 10:26:44AM +0900, HATAYAMA Daisuke wrote: [..] > >I am wondering if there is any attribute of cpu which we can pass to > >second kernel on command line. And tell second kernel not to bring up > >that specific cpu. (Say exclude_cpu=)? If this works, then > >if ACPI or other

Re: [PATCH v2 2/2] x86, apic: Disable BSP if boot cpu is AP

2013-10-18 Thread Vivek Goyal
On Wed, Oct 16, 2013 at 10:26:44AM +0900, HATAYAMA Daisuke wrote: [..] I am wondering if there is any attribute of cpu which we can pass to second kernel on command line. And tell second kernel not to bring up that specific cpu. (Say exclude_cpu=cpu_attr)? If this works, then if ACPI or other

Re: [PATCH v2 2/2] x86, apic: Disable BSP if boot cpu is AP

2013-10-15 Thread HATAYAMA Daisuke
(2013/10/16 4:30), Vivek Goyal wrote: On Tue, Oct 15, 2013 at 02:43:27PM +0900, HATAYAMA Daisuke wrote: Currently, on x86 architecture, if crash happens on AP in the kdump 1st kernel, the 2nd kernel fails to wake up multiple CPUs. The typical behaviour we actually see is immediate system reset

Re: [PATCH v2 2/2] x86, apic: Disable BSP if boot cpu is AP

2013-10-15 Thread Vivek Goyal
On Tue, Oct 15, 2013 at 02:43:27PM +0900, HATAYAMA Daisuke wrote: > Currently, on x86 architecture, if crash happens on AP in the kdump > 1st kernel, the 2nd kernel fails to wake up multiple CPUs. The typical > behaviour we actually see is immediate system reset or hang. > > This comes from the

Re: [PATCH v2 2/2] x86, apic: Disable BSP if boot cpu is AP

2013-10-15 Thread HATAYAMA Daisuke
(2013/10/16 4:30), Vivek Goyal wrote: On Tue, Oct 15, 2013 at 02:43:27PM +0900, HATAYAMA Daisuke wrote: Currently, on x86 architecture, if crash happens on AP in the kdump 1st kernel, the 2nd kernel fails to wake up multiple CPUs. The typical behaviour we actually see is immediate system reset

Re: [PATCH v2 2/2] x86, apic: Disable BSP if boot cpu is AP

2013-10-15 Thread Vivek Goyal
On Tue, Oct 15, 2013 at 02:43:27PM +0900, HATAYAMA Daisuke wrote: Currently, on x86 architecture, if crash happens on AP in the kdump 1st kernel, the 2nd kernel fails to wake up multiple CPUs. The typical behaviour we actually see is immediate system reset or hang. This comes from the

[PATCH v2 2/2] x86, apic: Disable BSP if boot cpu is AP

2013-10-14 Thread HATAYAMA Daisuke
Currently, on x86 architecture, if crash happens on AP in the kdump 1st kernel, the 2nd kernel fails to wake up multiple CPUs. The typical behaviour we actually see is immediate system reset or hang. This comes from the hardware specification that the processor with BSP flag is jumped at BIOS

[PATCH v2 2/2] x86, apic: Disable BSP if boot cpu is AP

2013-10-14 Thread HATAYAMA Daisuke
Currently, on x86 architecture, if crash happens on AP in the kdump 1st kernel, the 2nd kernel fails to wake up multiple CPUs. The typical behaviour we actually see is immediate system reset or hang. This comes from the hardware specification that the processor with BSP flag is jumped at BIOS