[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141028124425.GD3274@tassilo.jf.intel.com>
Date: Tue, 28 Oct 2014 05:44:25 -0700
From: Andi Kleen <ak@...ux.intel.com>
To: Vivek Goyal <vgoyal@...hat.com>
Cc: Prarit Bhargava <prarit@...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
> > I suppose ... but that would mean I would have to explain to an end user the
> > elaborate process of enabling kdb, inserting a break point, etc. The whole
> > purpose of this is to let an end user panic on WARN() easily.
> >
> > Asking an end user to enable kdb is magnitudes worse than asking them to
> > recompile a kernel.
>
> Agreed. Asking a customer to setup and run kdb and put breakpoints is much
> more pain than simply asking to reboot kernel with a command line option.
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"
But it would be a generic facility instead of a special purpose hack.
-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