From: Steven Rostedt <rostedt@goodmis.org>
To: Chase Douglas <chase.douglas@canonical.com>
Cc: linux-kernel@vger.kernel.org,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 1/3] Add tracing_off_event() to stop tracing when a bug or warning occur
Date: Thu, 18 Mar 2010 10:56:07 -0400 [thread overview]
Message-ID: <1268924167.32426.90.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1268920132-30512-1-git-send-email-chase.douglas@canonical.com>
[ Expanded the Cc list ]
On Thu, 2010-03-18 at 09:48 -0400, Chase Douglas wrote:
> The tracing_off_event() function calls tracing_off() to stop tracing
> when an event occurs. By default, only BUG-type events stop tracing,
> while WARNING type events do not. This is controlled through the
> tracing_off={none,warn,bug} commandline parameter.
>
> Call this function from bug and warning event handlers to enable a user
> to debug their kernel by starting a trace, hitting an event, and then
> retrieving trace info knowing that the trace was stopped right after the
> event was hit.
>
> Signed-off-by: Chase Douglas <chase.douglas@canonical.com>
> ---
> include/linux/kernel.h | 5 +++++
> kernel/trace/ring_buffer.c | 34 ++++++++++++++++++++++++++++++++++
> 2 files changed, 39 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/kernel.h b/include/linux/kernel.h
> index 7f07074..107091f 100644
> --- a/include/linux/kernel.h
> +++ b/include/linux/kernel.h
> @@ -478,16 +478,21 @@ static inline char *pack_hex_byte(char *buf, u8 byte)
> *
> * Most likely, you want to use tracing_on/tracing_off.
> */
> +#define TRACE_EVENT_BUG 0
> +#define TRACE_EVENT_WARN 1
This should probably be an enum.
> +
> #ifdef CONFIG_RING_BUFFER
> void tracing_on(void);
> void tracing_off(void);
> /* trace_off_permanent stops recording with no way to bring it back */
> void tracing_off_permanent(void);
> +void tracing_off_event(long event);
> int tracing_is_on(void);
> #else
> static inline void tracing_on(void) { }
> static inline void tracing_off(void) { }
> static inline void tracing_off_permanent(void) { }
> +static inline void tracing_off_event(long event) { }
> static inline int tracing_is_on(void) { return 0; }
> #endif
> #ifdef CONFIG_TRACING
> diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
> index 0287f9f..b148862 100644
> --- a/kernel/trace/ring_buffer.c
> +++ b/kernel/trace/ring_buffer.c
> @@ -193,6 +193,40 @@ void tracing_off_permanent(void)
> set_bit(RB_BUFFERS_DISABLED_BIT, &ring_buffer_flags);
> }
>
> +static long tracing_event_mask = TRACE_EVENT_BUG;
That's a bad name. It does not seem to be a mask but seems to be a
control setting. Maybe call it tracing_event_off_ctrl ?
-- Steve
> +
> +/**
> + * tracing_off_event - turn off tracing depending on event type
> + *
> + * This function checks the event type to determine whether tracing should be
> + * disabled. Useful for disabling tracing on bugs or warnings.
> + */
> +void tracing_off_event(long event)
> +{
> + if (event <= tracing_event_mask)
> + tracing_off();
> +}
> +EXPORT_SYMBOL_GPL(tracing_off_event);
> +
> +static int __init tracing_off_event_setup(char *str)
> +{
> + if (!strcmp("none", str))
> + tracing_event_mask = -1;
> + else if (!strcmp("bug", str))
> + tracing_event_mask = TRACE_EVENT_BUG;
> + else if (!strcmp("warn", str))
> + tracing_event_mask = TRACE_EVENT_WARN;
> + else
> + {
> + printk(KERN_NOTICE "Invalid value passed for tracing_off parameter\n");
> + return 1;
> + }
> +
> + return 0;
> +}
> +
> +__setup("tracing_off=", tracing_off_event_setup);
> +
> /**
> * tracing_is_on - show state of ring buffers enabled
> */
next prev parent reply other threads:[~2010-03-18 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 13:48 Chase Douglas
2010-03-18 13:48 ` [PATCH 2/3] Add tracing_off_event() calls to BUG() and WARN() paths Chase Douglas
2010-03-18 13:48 ` [PATCH 3/3] Stop tracing on a schedule bug Chase Douglas
2010-03-18 14:56 ` Steven Rostedt [this message]
2010-03-18 16:27 ` [PATCH 1/3] Add tracing_off_event() to stop tracing when a bug or warning occur Chase Douglas
2010-03-22 16:14 ` Randy Dunlap
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=1268924167.32426.90.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=chase.douglas@canonical.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®