[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1321541877.3997.31.camel@jlt3.sipsolutions.net>
Date: Thu, 17 Nov 2011 15:57:57 +0100
From: Johannes Berg <johannes@...solutions.net>
To: Frederic Weisbecker <fweisbec@...il.com>
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 Thu, 2011-11-17 at 15:55 +0100, Frederic Weisbecker wrote:
> > +++ 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 ?
Is that even possible? Do you then have to do something like
#include <.../printk.h>
#define CREATE_TRACE_POINTS
#include <.../printk.h>
or how else? In any case it seemed more common to not do that.
johannes
--
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