On Tue, Oct 28, 2014 at 05:44:25AM -0700, Andi Kleen wrote: > > > 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"
So does it already work or proposal is to make something like this work with kdb? What about the case of enabling it post boot and using a /sys file for that. Thanks Vivek -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
