LKML Archive on
help / color / mirror / Atom feed
From: Steven Rostedt <>
To: Peter Zijlstra <>
Cc: Ingo Molnar <>, linux-kernel <>
Subject: Re: [PATCH] ftrace: ftrace_dump_on_oops=[tracer]
Date: Sat, 1 Nov 2008 14:43:06 -0400 (EDT)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

  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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: [PATCH] ftrace: ftrace_dump_on_oops=[tracer]' \

* 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).