On 11/29/2017 10:40 AM, Thadeu Lima de Souza Cascardo wrote:
> Ping. Any further reviews/comments? Or any chance of this getting
> applied soon?
>
> Thanks.
> Cascardo.
>
Cross-referencing 2 threads on the same topic:
https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-November/166328.html
L
Ping. Any further reviews/comments? Or any chance of this getting
applied soon?
Thanks.
Cascardo.
On 11/17/2017 03:26 PM, Thadeu Lima de Souza Cascardo wrote:
> On Thu, Nov 16, 2017 at 07:26:43PM -0200, Guilherme G. Piccoli wrote:
>> On 11/06/2017 03:34 PM, Thadeu Lima de Souza Cascardo wrote:
>>> From: Mahesh Salgaonkar
>>>
>>> The kernel boot parameter 'nr_cpus=' allows one to specify numb
On Thu, Nov 16, 2017 at 07:26:43PM -0200, Guilherme G. Piccoli wrote:
> On 11/06/2017 03:34 PM, Thadeu Lima de Souza Cascardo wrote:
> > From: Mahesh Salgaonkar
> >
> > The kernel boot parameter 'nr_cpus=' allows one to specify number of
> > possible cpus in the system. In the normal scenario the
On 11/06/2017 03:34 PM, Thadeu Lima de Souza Cascardo wrote:
> From: Mahesh Salgaonkar
>
> The kernel boot parameter 'nr_cpus=' allows one to specify number of
> possible cpus in the system. In the normal scenario the first cpu (cpu0)
> that shows up is the boot cpu and hence it gets covered unde
From: Mahesh Salgaonkar
The kernel boot parameter 'nr_cpus=' allows one to specify number of
possible cpus in the system. In the normal scenario the first cpu (cpu0)
that shows up is the boot cpu and hence it gets covered under nr_cpus
limit.
But this assumption will be broken in kdump scenario
