on 03/06/2011 18:13 Andriy Gapon said the following:
>
> I wonder if anybody uses kdb_stop_cpus with non-default value.
I would like to go ahead and remove kdb_stop_cpus tunable/sysctl if nobody
objects.
> If, yes, I am very interested to learn about your usecase for it.
>
> I think that the d
on 04/06/2011 11:22 Andriy Gapon said the following:
> commit 458ebd9aca7e91fc6e0825c727c7220ab9f61016
>
> generic_stop_cpus: move timeout detection code from under DIAGNOSTIC
>
> ... and also increase it a bit.
> IMO it's better to detect and report the (rather serious) condition and
on 04/06/2011 12:11 Robert N. M. Watson said the following:
>
> On 4 Jun 2011, at 09:22, Andriy Gapon wrote:
>> commit 458ebd9aca7e91fc6e0825c727c7220ab9f61016
>>
>> generic_stop_cpus: move timeout detection code from under DIAGNOSTIC
>>
>> ... and also increase it a bit. IMO it's better to dete
on 05/06/2011 01:35 Attilio Rao said the following:
> 2011/6/4 Andriy Gapon :
>> commit 458ebd9aca7e91fc6e0825c727c7220ab9f61016
>>
>>generic_stop_cpus: move timeout detection code from under DIAGNOSTIC
>>
>>... and also increase it a bit.
>>IMO it's better to detect and report the (rat
2011/6/4 Andriy Gapon :
> on 03/06/2011 20:57 Robert N. M. Watson said the following:
>>
>> On 3 Jun 2011, at 16:13, Andriy Gapon wrote:
>>
>>> I wonder if anybody uses kdb_stop_cpus with non-default value. If, yes, I
>>> am very interested to learn about your usecase for it.
>>
>> The issue that p
2011/6/3 Nathan Whitehorn :
> On 06/03/11 10:13, Andriy Gapon wrote:
>>
>> I wonder if anybody uses kdb_stop_cpus with non-default value.
>> If, yes, I am very interested to learn about your usecase for it.
>>
>> I think that the default kdb behavior is the correct one, so it doesn't
>> make sense
On 4 Jun 2011, at 09:22, Andriy Gapon wrote:
> on 03/06/2011 20:57 Robert N. M. Watson said the following:
>>
>> On 3 Jun 2011, at 16:13, Andriy Gapon wrote:
>>
>>> I wonder if anybody uses kdb_stop_cpus with non-default value. If, yes, I
>>> am very interested to learn about your usecase for i
on 03/06/2011 20:57 Robert N. M. Watson said the following:
>
> On 3 Jun 2011, at 16:13, Andriy Gapon wrote:
>
>> I wonder if anybody uses kdb_stop_cpus with non-default value. If, yes, I
>> am very interested to learn about your usecase for it.
>
> The issue that prompted the sysctl was non-NMI
On 3 Jun 2011, at 16:13, Andriy Gapon wrote:
> I wonder if anybody uses kdb_stop_cpus with non-default value.
> If, yes, I am very interested to learn about your usecase for it.
The issue that prompted the sysctl was non-NMI IPIs being used to enter the
debugger or reboot following a core hangi
on 03/06/2011 18:28 Nathan Whitehorn said the following:
> On 06/03/11 10:13, Andriy Gapon wrote:
>>
>> I wonder if anybody uses kdb_stop_cpus with non-default value.
>> If, yes, I am very interested to learn about your usecase for it.
>>
>> I think that the default kdb behavior is the correct one,
On 06/03/11 10:13, Andriy Gapon wrote:
I wonder if anybody uses kdb_stop_cpus with non-default value.
If, yes, I am very interested to learn about your usecase for it.
I think that the default kdb behavior is the correct one, so it doesn't make
sense
to have a knob to turn on incorrect behavio
I wonder if anybody uses kdb_stop_cpus with non-default value.
If, yes, I am very interested to learn about your usecase for it.
I think that the default kdb behavior is the correct one, so it doesn't make
sense
to have a knob to turn on incorrect behavior.
But I may be missing something obvious
12 matches
Mail list logo
