Date: Fri, 12 Dec 2008 06:57:17 +0100
From: Ingo Molnar <mingo@elte.hu>
To: Robert Richter <robert.richter@amd.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
       oprofile-list <oprofile-list@lists.sourceforge.net>,
       Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH 0/9] oprofile: port to the new ring buffer
Message-ID: <20081212055717.GB12451@elte.hu>
References: <1229013723-8191-1-git-send-email-robert.richter@amd.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1229013723-8191-1-git-send-email-robert.richter@amd.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1312
Lines: 29


* Robert Richter <robert.richter@amd.com> wrote:

> This patch set ports cpu buffers in oprofile to the new ring buffer 
> provided by the tracing framework. The motivation here is to leave the 
> pain of implementing ring buffers to others. Oh, no, there are more 
> advantages. Main reason is the support of different sample sizes that 
> could be stored in the buffer. Use cases for this are IBS and Cell spu 
> profiling. Using the new ring buffer ensures valid and complete samples 
> and allows copying the cpu buffer stateless without knowing its 
> content. Second it will use generic kernel API and also reduce code 
> size. And hopefully, there are less bugs.
> 
> The patch set is also available here:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git ring_buffer

Pulled into tip/oprofile, thanks Robert - very nice stuff!

I've changed the exports to _GPL because these are really internal APIs 
with a high flux, so the practical requirement for code relying on it to 
be in-tree (or at least be source-available) is evident.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/