From: Ingo Molnar <mingo@elte.hu>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Steven Rostedt <rostedt@goodmis.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Jason Baron <jbaron@redhat.com>,
linux-kernel@vger.kernel.org, paulus@samba.org
Subject: Re: [PATCH 0/2] perf_counter: add tracepoint support
Date: Fri, 10 Jul 2009 05:53:19 +0200 [thread overview]
Message-ID: <20090710035319.GA5077@elte.hu> (raw)
In-Reply-To: <1247126283.9777.318.camel@twins>
* Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> On Thu, 2009-07-09 at 05:10 +0200, Frederic Weisbecker wrote:
> > (RFD parenthesis: why not using the one in kernel/trace for all
> > perf events? Now that it is lockless, it would fit nicely
> > inside: no fear about NMI context).
>
> because that one doesn't have a single-buffer mode you can mmap().
Yeah, the ring-buffer code could certainly be abstracted out better
to allow this. Once that is done it would allow us to do a couple of
nice things: such as splice support (which could perhaps be faster
than mmap for perf record) and the sampling of tracepoints would
become a whole lot easier a well. But it's certainly not a trivial
job!
Ingo
next prev parent reply other threads:[~2009-07-10 3:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 21:11 [PATCH 0/2] perf_counter: add tracepoint support Jason Baron
2009-07-06 21:11 ` [PATCH 1/2] perf_counter: cleanup kernel perf counter support for tracepoints Jason Baron
2009-07-06 21:12 ` [PATCH 2/2] perf_counter: add support to the 'perf' tool " Jason Baron
2009-07-07 8:29 ` Peter Zijlstra
2009-07-08 20:17 ` [PATCH 3/2] perf_counters: add debugfs dir option Jason Baron
2009-07-09 0:47 ` Frederic Weisbecker
2009-07-09 14:45 ` Jason Baron
2009-07-10 4:17 ` Ingo Molnar
2009-07-13 7:15 ` [PATCH 2/2] perf_counter: add support to the 'perf' tool for tracepoints Ingo Molnar
2009-07-09 3:10 ` [PATCH 0/2] perf_counter: add tracepoint support Frederic Weisbecker
2009-07-09 7:58 ` Peter Zijlstra
2009-07-10 3:53 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-07-21 16:20 Jason Baron
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=20090710035319.GA5077@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.