[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <64a6c1c0-9514-e823-3507-a131c7daa578@canonical.com>
Date: Wed, 11 Mar 2020 09:46:45 -0300
From: "Guilherme G. Piccoli" <gpiccoli@...onical.com>
To: Andrew Morton <akpm@...ux-foundation.org>,
Randy Dunlap <rdunlap@...radead.org>
Cc: linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
mcgrof@...nel.org, keescook@...omium.org, yzaikin@...gle.com,
tglx@...utronix.de, kernel@...ccoli.net
Subject: Re: [PATCH] panic: Add sysctl/cmdline to dump all CPUs backtraces on
oops event
On 10/03/2020 22:26, Andrew Morton wrote:
> On Tue, 10 Mar 2020 13:59:15 -0700 Randy Dunlap <rdunlap@...radead.org> wrote:
>
>>> +oops_all_cpu_backtrace:
>>> +================
>>> +
>>> +Determines if kernel should NMI all CPUs to dump their backtraces when
>>
>> I would much prefer that to be written without using NMI as a verb.
>
> "Non maskably interrupt" ;)
>
> I think it's OK. Concise and the meaning is clear.
Hi Andrew, good idea heheh
Thank you and all that reviewed the grammar/wording, certainly I can
change that and resubmit.
>
>
> Why do we need the kernel boot parameter? Isn't
> /proc/sys/kernel/oops_all_cpu_backtrace sufficient?
>
I kept the kernel parameter as a consistency thing - every sysctl
"*_all_cpubacktrace" has a respective kernel parameter, so I did the
same (and if we get an oops booting a new kernel, this is maybe useful
depending on the point we get the oops). But if it's a problem for you,
I can remove the kernel parameter, your choice.
Cheers,
Guilherme
Powered by blists - more mailing lists