From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758116Ab0DOXPd (ORCPT ); Thu, 15 Apr 2010 19:15:33 -0400 Received: from mail-wy0-f174.google.com ([74.125.82.174]:61479 "EHLO mail-wy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757971Ab0DOXPb (ORCPT ); Thu, 15 Apr 2010 19:15:31 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=fiyX7PMay528JMqkEgoVoD8olF0xLsLgGUkOTqEgef2MdPn6TrmWFBfbW9QtSAjben QUBFGzhe9IVTemaSyHqzeBPwYqlnH8i9fAFjIcrcK6LcJCUgEwPeL6CN55AmmjoqxgFK Em1xQIuWb5sVJXDpjMBEfFnrklc62XxsG/cMY= Date: Fri, 16 Apr 2010 01:15:30 +0200 From: Frederic Weisbecker To: Chase Douglas Cc: linux-kernel@vger.kernel.org, Steven Rostedt , Ingo Molnar , Thomas Gleixner , Randy Dunlap Subject: Re: [PATCH 2/3] Add tracing_off_event() calls to BUG() and WARN() paths Message-ID: <20100415231529.GB15570@nowhere> References: <1271262016-18650-1-git-send-email-chase.douglas@canonical.com> <1271262016-18650-2-git-send-email-chase.douglas@canonical.com> <20100415205739.GF5069@nowhere> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 15, 2010 at 02:49:05PM -0700, Chase Douglas wrote: > On Thu, Apr 15, 2010 at 1:57 PM, Frederic Weisbecker wrote: > > On Wed, Apr 14, 2010 at 12:20:15PM -0400, Chase Douglas wrote: > >> This change adds tracing_off_event() calls, which stop debug tracing, > >> when a BUG() or WARN() function is called. The stoppage depends on > >> commandline paramenter tracing_off={bug,warn,none}. The default is > >> "bug", so only the BUG() paths will stop tracing. > >> > >> Signed-off-by: Chase Douglas > > > > > > ACK > > > > But I can't find where we call oops_enter() from panic() > > I see it called in x86 from oops_begin() that is called > > in various places like die(), but couldn't find how it > > ends up beeing called from panic(). > > I did not test the panic() path, but when that happens the system goes > down anyways. You won't be able to get the ftrace unless you enable > the ftrace on oops option, in which case the end of the trace will > likely be close enough to what you are looking for anyways. Yeah but there is also a sysrq that can trigger an ftrace dump. So if you forgot ftrace dump on oops and you want to use the sysrq then you don't want the tracing to continue between the panic and the time for your fingers to reach the keyboard (that notwithstanding the time to remember the right combination...which I always forget).