From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx1.redhat.com ([209.132.183.28]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1Xj6DH-0001vT-CO for kexec@lists.infradead.org; Tue, 28 Oct 2014 12:49:28 +0000 Message-ID: <544F90B1.1070102@redhat.com> Date: Tue, 28 Oct 2014 08:48:49 -0400 From: Prarit Bhargava MIME-Version: 1.0 Subject: Re: [PATCH V4] kernel, add bug_on_warn References: <1414155207-29839-1-git-send-email-prarit@redhat.com> <20141028121636.GC3274@tassilo.jf.intel.com> <544F8A78.9070008@redhat.com> <20141028122900.GA10632@redhat.com> <20141028124425.GD3274@tassilo.jf.intel.com> In-Reply-To: <20141028124425.GD3274@tassilo.jf.intel.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "kexec" Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: Andi Kleen Cc: Jonathan Corbet , kexec@lists.infradead.org, jason.wessel@windriver.com, Rusty Russell , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Fabian Frederick , isimatu.yasuaki@jp.fujitsu.com, "H. Peter Anvin" , Masami Hiramatsu , Andrew Morton , linux-api@vger.kernel.org, Vivek Goyal On 10/28/2014 08:44 AM, 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" KDB is not on all kernels. This would require me to go to great lengths to explain to a user how to set it up, etc., rather than saying "Hi, please add panic_on_warn as a kernel parameter/echo 1 into /proc/sys/kernel/panic_on_warn and on the next time you see that WARN() the system will panic and kdump. Send me that kdump." > > But it would be a generic facility instead of a special purpose hack. Generic to KDB be configured on and it is in no way trivial to use. P. _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec From mboxrd@z Thu Jan 1 00:00:00 1970 From: Prarit Bhargava Subject: Re: [PATCH V4] kernel, add bug_on_warn Date: Tue, 28 Oct 2014 08:48:49 -0400 Message-ID: <544F90B1.1070102@redhat.com> References: <1414155207-29839-1-git-send-email-prarit@redhat.com> <20141028121636.GC3274@tassilo.jf.intel.com> <544F8A78.9070008@redhat.com> <20141028122900.GA10632@redhat.com> <20141028124425.GD3274@tassilo.jf.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20141028124425.GD3274-KWJ+5VKanrL29G5dvP0v1laTQe2KTcn/@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "kexec" Errors-To: kexec-bounces+glkk-kexec=m.gmane.org-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org To: Andi Kleen Cc: Jonathan Corbet , kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, jason.wessel-CWA4WttNNZF54TAoqtyWWQ@public.gmane.org, Rusty Russell , linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Fabian Frederick , isimatu.yasuaki-+CUm20s59erQFUHtdCDX3A@public.gmane.org, "H. Peter Anvin" , Masami Hiramatsu , Andrew Morton , linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Vivek Goyal List-Id: linux-api@vger.kernel.org On 10/28/2014 08:44 AM, 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" KDB is not on all kernels. This would require me to go to great lengths to explain to a user how to set it up, etc., rather than saying "Hi, please add panic_on_warn as a kernel parameter/echo 1 into /proc/sys/kernel/panic_on_warn and on the next time you see that WARN() the system will panic and kdump. Send me that kdump." > > But it would be a generic facility instead of a special purpose hack. Generic to KDB be configured on and it is in no way trivial to use. P. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751999AbaJ1Mtk (ORCPT ); Tue, 28 Oct 2014 08:49:40 -0400 Received: from mx1.redhat.com ([209.132.183.28]:52462 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750727AbaJ1Mti (ORCPT ); Tue, 28 Oct 2014 08:49:38 -0400 Message-ID: <544F90B1.1070102@redhat.com> Date: Tue, 28 Oct 2014 08:48:49 -0400 From: Prarit Bhargava User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131028 Thunderbird/17.0.10 MIME-Version: 1.0 To: Andi Kleen CC: Vivek Goyal , linux-kernel@vger.kernel.org, Jonathan Corbet , Andrew Morton , Rusty Russell , "H. Peter Anvin" , Masami Hiramatsu , Fabian Frederick , isimatu.yasuaki@jp.fujitsu.com, linux-doc@vger.kernel.org, kexec@lists.infradead.org, linux-api@vger.kernel.org, jason.wessel@windriver.com Subject: Re: [PATCH V4] kernel, add bug_on_warn References: <1414155207-29839-1-git-send-email-prarit@redhat.com> <20141028121636.GC3274@tassilo.jf.intel.com> <544F8A78.9070008@redhat.com> <20141028122900.GA10632@redhat.com> <20141028124425.GD3274@tassilo.jf.intel.com> In-Reply-To: <20141028124425.GD3274@tassilo.jf.intel.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/28/2014 08:44 AM, 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" KDB is not on all kernels. This would require me to go to great lengths to explain to a user how to set it up, etc., rather than saying "Hi, please add panic_on_warn as a kernel parameter/echo 1 into /proc/sys/kernel/panic_on_warn and on the next time you see that WARN() the system will panic and kdump. Send me that kdump." > > But it would be a generic facility instead of a special purpose hack. Generic to KDB be configured on and it is in no way trivial to use. P.