From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Cc: Paul Mackerras <paulus@samba.org>, Mike Galbraith <efault@gmx.de>,
Arjan van de Ven <arjan@infradead.org>,
Wu Fengguang <fengguang.wu@intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: [RFC][PATCH 0/3] more perf_counter stuff
Date: Wed, 25 Mar 2009 22:04:19 +0100 [thread overview]
Message-ID: <20090325210419.408653980@chello.nl> (raw)
mostly compile tested.. :-)
--
next reply other threads:[~2009-03-25 21:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 21:04 Peter Zijlstra [this message]
2009-03-25 21:04 ` [RFC][PATCH 1/3] perf_counter: event overlow handling Peter Zijlstra
2009-03-25 21:04 ` [RFC][PATCH 2/3] perf_counter: executable mmap() information Peter Zijlstra
2009-03-26 5:52 ` Paul Mackerras
2009-03-26 10:00 ` Ingo Molnar
2009-03-26 10:57 ` Paul Mackerras
2009-03-26 11:13 ` Paul Mackerras
2009-03-25 21:04 ` [RFC][PATCH 3/3] perf_counter: kerneltop: parse the mmap data stream Peter Zijlstra
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=20090325210419.408653980@chello.nl \
--to=a.p.zijlstra@chello.nl \
--cc=arjan@infradead.org \
--cc=efault@gmx.de \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.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