LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ftrace: ftrace_dump_on_oops=[tracer]
Date: Sat, 1 Nov 2008 14:43:06 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0811011441210.13362@gandalf.stny.rr.com> (raw)
In-Reply-To: <1225544744.21456.38.camel@lappy.programming.kicks-ass.net>
On Sat, 1 Nov 2008, Peter Zijlstra wrote:
> seems useful to debug crashes that happen before I read userspace.
Hmm, I think it might be better to separate this from the dump_on_oops.
How about a ftrace_default_tracer parameter?
If one is defined, it is activated as soon as it is initialized. This way
we decouple the dump_on_oops, which we may not always want, and a way to
start tracers before the switch to user space.
-- Steve
next prev parent reply other threads:[~2008-11-01 18:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-01 13:05 Peter Zijlstra
2008-11-01 18:43 ` Steven Rostedt [this message]
2008-11-01 18:57 ` Peter Zijlstra
2008-11-01 19:13 ` Steven Rostedt
2008-11-03 8:14 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.1.10.0811011441210.13362@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--subject='Re: [PATCH] ftrace: ftrace_dump_on_oops=[tracer]' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).