From: Frederic Weisbecker <fweisbec@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Chase Douglas <chase.douglas@canonical.com>,
linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: [PATCH 3/3] Stop tracing on a schedule bug
Date: Fri, 16 Apr 2010 01:10:54 +0200 [thread overview]
Message-ID: <20100415231052.GA15570@nowhere> (raw)
In-Reply-To: <alpine.LFD.2.00.1004160051390.3625@localhost.localdomain>
On Fri, Apr 16, 2010 at 01:01:50AM +0200, Thomas Gleixner wrote:
> > I tend to think of the TRACE_EVENT_* as an indication of severity and
> > whether we want to stop the trace by default. From a distro
> > standpoint, the likelihood that we want to continue tracing after a
> > __schedule_bug is pretty low. It's easiest if we don't have to tell
>
> Well, scheduling while atomic is a BUG, but one of the category which
> allows the kernel to continue. So in fact it's treated like a WARN_ON.
> So the tracing_off_event() qualifier should be *_WARN.
>
> That's independent of the question whether you want to stop tracing in
> that very case
Exactly.
next prev parent reply other threads:[~2010-04-15 23:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 16:20 [PATCH 1/3 v4] Add tracing_off_event() to stop tracing when a bug or warning occur Chase Douglas
2010-04-14 16:20 ` [PATCH 2/3] Add tracing_off_event() calls to BUG() and WARN() paths Chase Douglas
2010-04-15 20:57 ` Frederic Weisbecker
2010-04-15 21:49 ` Chase Douglas
2010-04-15 23:15 ` Frederic Weisbecker
2010-04-16 4:13 ` Chase Douglas
2010-04-14 16:20 ` [PATCH 3/3] Stop tracing on a schedule bug Chase Douglas
2010-04-15 21:03 ` Frederic Weisbecker
2010-04-15 21:45 ` Chase Douglas
2010-04-15 23:01 ` Thomas Gleixner
2010-04-15 23:10 ` Frederic Weisbecker [this message]
2010-04-15 23:27 ` Chase Douglas
2010-04-15 23:50 ` Thomas Gleixner
2010-04-16 0:21 ` Thomas Gleixner
2010-04-16 1:49 ` Frederic Weisbecker
2010-04-16 16:41 ` Steven Rostedt
2010-04-16 4:01 ` Chase Douglas
2010-04-16 16:46 ` Steven Rostedt
2010-04-16 17:14 ` Chase Douglas
2010-04-16 18:14 ` Frederic Weisbecker
2010-04-16 19:58 ` Thomas Gleixner
2010-04-19 22:30 ` Chase Douglas
2010-04-16 3:52 ` Chase Douglas
2010-04-15 20:13 ` [PATCH 1/3 v4] Add tracing_off_event() to stop tracing when a bug or warning occur Frederic Weisbecker
-- strict thread matches above, loose matches on Subject: below --
2010-03-18 13:48 [PATCH 1/3] " Chase Douglas
2010-03-18 13:48 ` [PATCH 3/3] Stop tracing on a schedule bug Chase Douglas
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=20100415231052.GA15570@nowhere \
--to=fweisbec@gmail.com \
--cc=chase.douglas@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.