On Wed, 15 Jan 2014 13:14:26 -0500
Vivek Goyal wrote:
> On Wed, Jan 15, 2014 at 09:54:31AM -0800, H. Peter Anvin wrote:
> > On 01/15/2014 09:47 AM, Vivek Goyal wrote:
> > > On Wed, Jan 15, 2014 at 09:26:14AM -0800, H. Peter Anvin wrote:
> > >> On 01/15/2014 09:05 AM, Vivek Goyal wrote:
> > >>>
>
On Wed, 15 Jan 2014 13:14:26 -0500
Vivek Goyal vgo...@redhat.com wrote:
On Wed, Jan 15, 2014 at 09:54:31AM -0800, H. Peter Anvin wrote:
On 01/15/2014 09:47 AM, Vivek Goyal wrote:
On Wed, Jan 15, 2014 at 09:26:14AM -0800, H. Peter Anvin wrote:
On 01/15/2014 09:05 AM, Vivek Goyal wrote:
On 01/15/2014 10:14 AM, Vivek Goyal wrote:
>
> For large amount of info like memory map, I agree that passing on command
> line is not a good idea. (/me taks the blame for doing that). That's why
> in new patches I want to move to pass new map on bootparams and pass
> saved_max_pfn on command
On Wed, Jan 15, 2014 at 09:54:31AM -0800, H. Peter Anvin wrote:
> On 01/15/2014 09:47 AM, Vivek Goyal wrote:
> > On Wed, Jan 15, 2014 at 09:26:14AM -0800, H. Peter Anvin wrote:
> >> On 01/15/2014 09:05 AM, Vivek Goyal wrote:
> >>>
> >>> I think this is a reasonable approach to solve the issue. Use
On 01/15/2014 09:47 AM, Vivek Goyal wrote:
> On Wed, Jan 15, 2014 at 09:26:14AM -0800, H. Peter Anvin wrote:
>> On 01/15/2014 09:05 AM, Vivek Goyal wrote:
>>>
>>> I think this is a reasonable approach to solve the issue. Use a command
>>> line to not bring up specific cpu in second kernel which
On Wed, Jan 15, 2014 at 09:26:14AM -0800, H. Peter Anvin wrote:
> On 01/15/2014 09:05 AM, Vivek Goyal wrote:
> >
> > I think this is a reasonable approach to solve the issue. Use a command
> > line to not bring up specific cpu in second kernel which can create
> > problems.
> >
> > Acked-by:
On 01/15/2014 09:05 AM, Vivek Goyal wrote:
>
> I think this is a reasonable approach to solve the issue. Use a command
> line to not bring up specific cpu in second kernel which can create
> problems.
>
> Acked-by: Vivek Goyal
>
> hpa, I know you are not excited about this approach. If you
On Wed, Jan 15, 2014 at 03:44:58PM +0900, HATAYAMA Daisuke wrote:
> Add disable_cpu_apicid kernel parameter. To use this kernel parameter,
> specify an initial APIC ID of the corresponding CPU you want to
> disable.
>
> This is mostly used for the kdump 2nd kernel to disable BSP to wake up
>
On Wed, Jan 15, 2014 at 03:44:58PM +0900, HATAYAMA Daisuke wrote:
Add disable_cpu_apicid kernel parameter. To use this kernel parameter,
specify an initial APIC ID of the corresponding CPU you want to
disable.
This is mostly used for the kdump 2nd kernel to disable BSP to wake up
multiple
On 01/15/2014 09:05 AM, Vivek Goyal wrote:
I think this is a reasonable approach to solve the issue. Use a command
line to not bring up specific cpu in second kernel which can create
problems.
Acked-by: Vivek Goyal vgo...@redhat.com
hpa, I know you are not excited about this approach.
On Wed, Jan 15, 2014 at 09:26:14AM -0800, H. Peter Anvin wrote:
On 01/15/2014 09:05 AM, Vivek Goyal wrote:
I think this is a reasonable approach to solve the issue. Use a command
line to not bring up specific cpu in second kernel which can create
problems.
Acked-by: Vivek Goyal
On 01/15/2014 09:47 AM, Vivek Goyal wrote:
On Wed, Jan 15, 2014 at 09:26:14AM -0800, H. Peter Anvin wrote:
On 01/15/2014 09:05 AM, Vivek Goyal wrote:
I think this is a reasonable approach to solve the issue. Use a command
line to not bring up specific cpu in second kernel which can create
On Wed, Jan 15, 2014 at 09:54:31AM -0800, H. Peter Anvin wrote:
On 01/15/2014 09:47 AM, Vivek Goyal wrote:
On Wed, Jan 15, 2014 at 09:26:14AM -0800, H. Peter Anvin wrote:
On 01/15/2014 09:05 AM, Vivek Goyal wrote:
I think this is a reasonable approach to solve the issue. Use a command
On 01/15/2014 10:14 AM, Vivek Goyal wrote:
For large amount of info like memory map, I agree that passing on command
line is not a good idea. (/me taks the blame for doing that). That's why
in new patches I want to move to pass new map on bootparams and pass
saved_max_pfn on command line
Add disable_cpu_apicid kernel parameter. To use this kernel parameter,
specify an initial APIC ID of the corresponding CPU you want to
disable.
This is mostly used for the kdump 2nd kernel to disable BSP to wake up
multiple CPUs without causing system reset or hang due to sending INIT
from AP to
Add disable_cpu_apicid kernel parameter. To use this kernel parameter,
specify an initial APIC ID of the corresponding CPU you want to
disable.
This is mostly used for the kdump 2nd kernel to disable BSP to wake up
multiple CPUs without causing system reset or hang due to sending INIT
from AP to
16 matches
Mail list logo
