[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111117145502.GA18437@somewhere>
Date: Thu, 17 Nov 2011 15:55:07 +0100
From: Frederic Weisbecker <fweisbec@...il.com>
To: Johannes Berg <johannes@...solutions.net>
Cc: Steven Rostedt <rostedt@...dmis.org>,
Christoph Hellwig <hch@...radead.org>,
LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...hat.com>
Subject: Re: [PATCH] printk: add console output tracing
On Wed, Nov 16, 2011 at 10:25:19PM +0100, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@...el.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@...el.com>
> ---
> include/trace/events/printk.h | 44 ++++++++++++++++++++++++++++++++++++++++++
> kernel/printk.c | 3 ++
> kernel/trace/Makefile | 1
> kernel/trace/printk-trace.c | 14 +++++++++++++
> 4 files changed, 62 insertions(+)
<snip>
> --- /dev/null 1970-01-01 00:00:00.000000000 +0000
> +++ b/kernel/trace/printk-trace.c 2011-11-16 21:22:20.000000000 +0100
> @@ -0,0 +1,14 @@
> +/*
> + * printk trace points
> + *
> + * Copyright (C) 2011 Johannes Berg <johannes.berg@...el.com>
> + */
> +
> +#include <linux/string.h>
> +#include <linux/types.h>
> +#include <linux/workqueue.h>
> +#include <linux/sched.h>
> +#include <linux/module.h>
> +
> +#define CREATE_TRACE_POINTS
> +#include <trace/events/printk.h>
Why not defining the tracepoint in kernel/printk.c ?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists