[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <544F97C4.8000203@redhat.com>
Date: Tue, 28 Oct 2014 09:19:00 -0400
From: Prarit Bhargava <prarit@...hat.com>
To: Andi Kleen <ak@...ux.intel.com>
CC: Vivek Goyal <vgoyal@...hat.com>, linux-kernel@...r.kernel.org,
Jonathan Corbet <corbet@....net>,
Andrew Morton <akpm@...ux-foundation.org>,
Rusty Russell <rusty@...tcorp.com.au>,
"H. Peter Anvin" <hpa@...or.com>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
Fabian Frederick <fabf@...net.be>,
isimatu.yasuaki@...fujitsu.com, linux-doc@...r.kernel.org,
kexec@...ts.infradead.org, linux-api@...r.kernel.org,
jason.wessel@...driver.com
Subject: Re: [PATCH V4] kernel, add bug_on_warn
On 10/28/2014 08:56 AM, Andi Kleen wrote:
>>> If you have a command line option to execute kdb commands you still
>>> would only have a command line option, just a slightly longer one.
>>>
>>> kdb="on, bp warn_slowpath_common sr c, go"
>>
>> KDB is not on all kernels. This would require me to go to great lengths to
>
> Repeating incorrect statements doesn't suddenly make them correct.
It does when you're introducing unnecessary complexity here Andi. You're not
listening to the original statement: I do not want to provide a modified kernel
to an end user for this simple situation anymore.
>
> Assuming KDB is compiled in the only setup needed would be the line above.
That's a HUGE assumption. It isn't and I'm still stuck in the same mess of
explaining how to recompile a kernel and/or providing a modified kernel to an
end user. That isn't a good solution.
P.
>
> -Andi
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists