From: Frederic Weisbecker <fweisbec@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Christoph Hellwig <hch@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH v2] printk: add console output tracing
Date: Fri, 18 Nov 2011 19:44:06 +0100 [thread overview]
Message-ID: <20111118184401.GA24787@somewhere.redhat.com> (raw)
In-Reply-To: <1321543268.3997.40.camel@jlt3.sipsolutions.net>
On Thu, Nov 17, 2011 at 04:21:08PM +0100, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> Add a printk.console trace point to record any printk
> messages into the trace, regardless of the current
> console loglevel. This can help correlate (existing)
> printk debugging with other tracing.
>
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> ---
> v2: remove extra file
>
> include/trace/events/printk.h | 44 ++++++++++++++++++++++++++++++++++++++++++
> kernel/printk.c | 5 ++++
> 2 files changed, 49 insertions(+)
>
> --- /dev/null 1970-01-01 00:00:00.000000000 +0000
> +++ b/include/trace/events/printk.h 2011-11-16 23:18:35.000000000 +0100
> @@ -0,0 +1,44 @@
> +#undef TRACE_SYSTEM
> +#define TRACE_SYSTEM printk
> +
> +#if !defined(_TRACE_PRINTK_H) || defined(TRACE_HEADER_MULTI_READ)
> +#define _TRACE_PRINTK_H
> +
> +#include <linux/tracepoint.h>
> +
> +TRACE_EVENT_CONDITION(console,
> + TP_PROTO(const char *log_buf, unsigned start, unsigned end,
> + unsigned log_buf_len),
> +
> + TP_ARGS(log_buf, start, end, log_buf_len),
> +
> + TP_CONDITION(start != end),
> +
> + TP_STRUCT__entry(
> + __dynamic_array(char, msg,
> + ((end - start + log_buf_len) &
> + (log_buf_len - 1)) + 1)
Is all that care about log_buf_len necessary? It seems that
printk ensures that log_end - con_start never exceeds log_buf_len,
looking at emit_log_char()
Thanks.
> + ),
> +
> + TP_fast_assign(
> + if ((start & (log_buf_len - 1)) > (end & (log_buf_len - 1))) {
> + memcpy(__get_dynamic_array(msg),
> + log_buf + (start & (log_buf_len - 1)),
> + log_buf_len - (start & (log_buf_len - 1)));
> + memcpy((char *)__get_dynamic_array(msg) +
> + log_buf_len - (start & (log_buf_len - 1)),
> + log_buf, end & (log_buf_len - 1));
> + } else
> + memcpy(__get_dynamic_array(msg),
> + log_buf + (start & (log_buf_len - 1)),
> + (end - start + log_buf_len) & (log_buf_len - 1));
> + ((char *)__get_dynamic_array(msg))[(end - start + log_buf_len) &
> + (log_buf_len - 1)] = 0;
> + ),
> +
> + TP_printk("%s", __get_str(msg))
> +);
> +#endif /* _TRACE_PRINTK_H */
> +
> +/* This part must be outside protection */
> +#include <trace/define_trace.h>
> --- a/kernel/printk.c 2011-11-16 22:25:43.000000000 +0100
> +++ b/kernel/printk.c 2011-11-17 16:19:19.000000000 +0100
> @@ -44,6 +44,9 @@
>
> #include <asm/uaccess.h>
>
> +#define CREATE_TRACE_POINTS
> +#include <trace/events/printk.h>
> +
> /*
> * Architectures can override it:
> */
> @@ -542,6 +545,8 @@ MODULE_PARM_DESC(ignore_loglevel, "ignor
> static void _call_console_drivers(unsigned start,
> unsigned end, int msg_log_level)
> {
> + trace_console(&LOG_BUF(0), start, end, log_buf_len);
> +
> if ((msg_log_level < console_loglevel || ignore_loglevel) &&
> console_drivers && start != end) {
> if ((start & LOG_BUF_MASK) > (end & LOG_BUF_MASK)) {
>
>
next prev parent reply other threads:[~2011-11-18 18:44 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 10:18 [PATCH] tracing: add trace console Johannes Berg
2011-11-16 14:15 ` Steven Rostedt
2011-11-16 14:25 ` Peter Zijlstra
2011-11-16 14:30 ` Johannes Berg
2011-11-16 14:41 ` Peter Zijlstra
2011-11-16 14:48 ` Steven Rostedt
2011-11-16 14:50 ` Peter Zijlstra
2011-11-16 14:51 ` Johannes Berg
2011-11-16 15:17 ` Steven Rostedt
2011-11-16 14:32 ` Thomas Gleixner
2011-11-16 14:35 ` Frederic Weisbecker
2011-11-16 15:09 ` [PATCH v2] " Johannes Berg
2011-11-16 15:17 ` Peter Zijlstra
2011-11-16 15:19 ` Steven Rostedt
2011-11-16 15:10 ` [PATCH] " Christoph Hellwig
2011-11-16 15:17 ` Johannes Berg
2011-11-16 16:41 ` Steven Rostedt
2011-11-16 16:45 ` Johannes Berg
2011-11-16 17:00 ` Steven Rostedt
2011-11-16 17:05 ` Steven Rostedt
2011-11-16 18:33 ` Johannes Berg
2011-11-16 19:57 ` Steven Rostedt
2011-11-16 20:12 ` Johannes Berg
2011-11-16 21:25 ` [PATCH] printk: add console output tracing Johannes Berg
2011-11-17 1:01 ` Steven Rostedt
2011-11-17 14:55 ` Frederic Weisbecker
2011-11-17 14:57 ` Johannes Berg
2011-11-17 15:00 ` Frederic Weisbecker
2011-11-17 15:17 ` Steven Rostedt
2011-11-17 15:21 ` [PATCH v2] " Johannes Berg
2011-11-18 18:44 ` Frederic Weisbecker [this message]
2011-11-18 18:46 ` Johannes Berg
2011-11-18 18:54 ` Frederic Weisbecker
2011-11-18 18:59 ` Johannes Berg
2011-11-23 13:16 ` Frederic Weisbecker
2011-11-24 13:21 ` Johannes Berg
2011-11-24 15:45 ` Frederic Weisbecker
2011-11-24 19:00 ` Johannes Berg
2011-11-25 17:43 ` Frederic Weisbecker
2011-11-25 18:11 ` Johannes Berg
2011-11-24 19:03 ` [PATCH v3] " Johannes Berg
2011-11-25 17:41 ` Frederic Weisbecker
2011-12-02 18:05 ` Steven Rostedt
2012-02-13 17:30 ` Steven Rostedt
2012-02-13 17:33 ` Johannes Berg
2012-02-13 17:42 ` Steven Rostedt
2012-02-17 13:52 ` [tip:perf/core] printk/tracing: Add " tip-bot for Johannes Berg
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=20111118184401.GA24787@somewhere.redhat.com \
--to=fweisbec@gmail.com \
--cc=hch@infradead.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
/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