[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1287579993.16971.552.camel@gandalf.stny.rr.com>
Date: Wed, 20 Oct 2010 09:06:33 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH 2/5] ring-buffer: Bind time extend and data events
together
On Tue, 2010-10-19 at 22:46 +0200, Thomas Gleixner wrote:
> On Tue, 19 Oct 2010, Steven Rostedt wrote:
> > Suggested-by: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
> > Cc: Thomas Gleixner <tglx@...utronix.de>
> > Signed-off-by: Steven Rostedt <rostedt@...dmis.org>
> > ---
> > include/linux/ring_buffer.h | 12 --
> > kernel/trace/ring_buffer.c | 283 +++++++++++++++++++++++--------------------
> > 2 files changed, 154 insertions(+), 141 deletions(-)
>
> Is there no way to make this change a bit more finegrained,
> i.e. incremental patches ?
>
> Thanks,
There's probably a little I can add incrementally, but the main change
that this does is that the ring buffer can return either a data type or
time extend type (which has a data type appended to it).
Luckily, the interface to the ring buffer has all be encapsulated, so
the only changes need to be made in ring_buffer.[ch]. All interfaces
that take a event type needs to check if it is a data or time extend.
Which is why the patch looks so big. But these changes are contained in
this file.
But there's some clean ups that this patch did, I can pull them out and
submit again.
Thanks,
-- 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