[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.0902242012360.12697@gandalf.stny.rr.com>
Date: Tue, 24 Feb 2009 20:15:01 -0500 (EST)
From: Steven Rostedt <rostedt@...dmis.org>
To: Mathieu Desnoyers <compudj@...stal.dyndns.org>
cc: Masami Hiramatsu <mhiramat@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Frederic Weisbecker <fweisbec@...il.com>,
Theodore Tso <tytso@....edu>,
Arjan van de Ven <arjan@...radead.org>,
Pekka Paalanen <pq@....fi>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Jason Baron <jbaron@...hat.com>,
Martin Bligh <mbligh@...gle.com>,
"Frank Ch. Eigler" <fche@...hat.com>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Jens Axboe <jens.axboe@...cle.com>
Subject: Re: [PATCH 0/4][RFC] event tracer
On Tue, 24 Feb 2009, Mathieu Desnoyers wrote:
> * Steven Rostedt (rostedt@...dmis.org) wrote:
> >
> > On Tue, 24 Feb 2009, Masami Hiramatsu wrote:
> > > >
> > > > #undef TPFMT
> > > > #define TPFMT(fmt, args...) \
> > > > "(%s)" fmt "\n", #call, ##args
> > > >
> > > > and then I could do
> > > >
> > > > event_printk(fmt);
> > >
> > > Why don't you do as below? :)
> > > event_printk_line("(" #call ")" ##fmtandargs);
> >
> > Still need to sneak that "\n" in ;-)
> >
>
> Why do you need the \n ? Having all event format strings ending with \0
> should be enough to tell event_printk to generate a \n each time it
> encounters a format string \0. Doing so would save 1 byte per format
> string.
Because currently event_printk uses a generic function that acts pretty
much like ftrace_printk.
I like having fmt and args separate. This way, we can add more stuff to
the end if we ever want to. For now it's a '\n'. We can deal with
those extra bytes.
-- Steve
--
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