From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Anton Blanchard <anton@samba.org>
Cc: mingo@elte.hu, paulus@samba.org, fweisbec@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [patch 0/5] Various perfcounter fixes
Date: Thu, 16 Jul 2009 16:16:32 +0200 [thread overview]
Message-ID: <1247753792.6586.21.camel@laptop> (raw)
In-Reply-To: <20090716104247.536695580@samba.org>
On Thu, 2009-07-16 at 20:42 +1000, Anton Blanchard wrote:
> Here are a few more perfcounter fixes, and one patch that changes the
> call graph option to be consistent between perf record and perf report.
> Perhaps I'm too late on that one, but I thought I'd give it a try :)
Nice catch on 1, and agreed on the others as well. Thanks!
I'll see what I can do to make this land in .31.
prev parent reply other threads:[~2009-07-16 14:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 10:42 [patch 0/5] Various perfcounter fixes Anton Blanchard
2009-07-16 10:42 ` [patch 1/5] perf_counter: Make sure we dont leak kernel memory to userspace Anton Blanchard
2009-07-18 9:50 ` [tip:perfcounters/urgent] " tip-bot for Anton Blanchard
2009-07-16 10:42 ` [patch 2/5] perf_counter: Synthesize VDSO mmap event Anton Blanchard
2009-07-18 9:50 ` [tip:perfcounters/urgent] " tip-bot for Anton Blanchard
2009-07-16 10:42 ` [patch 3/5] perf_counter: Log vfork as a fork event Anton Blanchard
2009-07-18 9:50 ` [tip:perfcounters/urgent] " tip-bot for Anton Blanchard
2009-07-16 10:42 ` [patch 4/5] perf_counter: Add perf record option to log addresses Anton Blanchard
2009-07-18 9:50 ` [tip:perfcounters/urgent] " tip-bot for Anton Blanchard
2009-07-16 10:42 ` [patch 5/5] perf_counter: Make call graph option consistent Anton Blanchard
2009-07-16 14:49 ` Frederic Weisbecker
2009-07-18 9:50 ` [tip:perfcounters/urgent] " tip-bot for Anton Blanchard
2009-07-16 14:16 ` Peter Zijlstra [this message]
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=1247753792.6586.21.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=anton@samba.org \
--cc=fweisbec@gmail.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 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.