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
Date: Fri, 12 Dec 2008 06:57:17 +0100 [thread overview]
Message-ID: <20081212055717.GB12451@elte.hu> (raw)
In-Reply-To: <1229013723-8191-1-git-send-email-robert.richter@amd.com>
* 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
next prev parent reply other threads:[~2008-12-12 5:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 16:41 Robert Richter
2008-12-11 16:41 ` [PATCH 1/9] oprofile: adding cpu buffer r/w access functions Robert Richter
2008-12-11 16:41 ` [PATCH 2/9] oprofile: adding cpu_buffer_write_commit() Robert Richter
2008-12-11 16:41 ` [PATCH 3/9] oprofile: adding cpu_buffer_entries() Robert Richter
2008-12-11 16:41 ` [PATCH 4/9] oprofile: moving cpu_buffer_reset() to cpu_buffer.h Robert Richter
2008-12-11 16:41 ` [PATCH 5/9] ring_buffer: add remaining cpu functions to ring_buffer.h Robert Richter
2008-12-11 19:23 ` Steven Rostedt
2008-12-11 16:42 ` [PATCH 6/9] oprofile: port to the new ring_buffer Robert Richter
2008-12-11 19:48 ` Steven Rostedt
2008-12-16 17:23 ` Robert Richter
2008-12-16 19:38 ` Steven Rostedt
2008-12-16 9:37 ` Andrew Morton
2008-12-11 16:42 ` [PATCH 7/9] oprofile: remove nr_available_slots() Robert Richter
2008-12-11 16:42 ` [PATCH 8/9] oprofile: fix lost sample counter Robert Richter
2008-12-11 16:42 ` [PATCH 9/9] ring_buffer: adding EXPORT_SYMBOLs Robert Richter
2008-12-11 17:19 ` [PATCH 0/9] oprofile: port to the new ring buffer Steven Rostedt
2008-12-12 5:57 ` Ingo Molnar [this message]
2008-12-16 23:49 ` Andrew Morton
2008-12-17 5:03 ` Pekka Enberg
2008-12-22 23:53 ` Carl Love
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081212055717.GB12451@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=oprofile-list@lists.sourceforge.net \
--cc=robert.richter@amd.com \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®