From: David Ahern <dsahern@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: acme@ghostprotocols.net, linux-kernel@vger.kernel.org,
Robert Richter <robert.richter@amd.com>
Subject: Re: [PATCH 0/3] perf: precise mode and exclude_guest
Date: Mon, 10 Sep 2012 11:01:04 -0600 [thread overview]
Message-ID: <504E1CD0.8040306@gmail.com> (raw)
In-Reply-To: <1347296241.2124.32.camel@twins>
On 9/10/12 10:57 AM, Peter Zijlstra wrote:
> On Mon, 2012-09-10 at 10:40 -0600, David Ahern wrote:
>> Hopefully thi wraps up the precise mode-exclude_guest dependency.
>> I'm sure someone will let me know if I screwed up the attribution
>> in the second patch.
>
>
> I'll wait with applying until we have the IBS stuff sorted, other than
> that, thanks for collecting this..
>
Robert recently confirmed that this series should not have an impact on
AMD as it currently stands -- exclude attributes are ignored. And then
his patch to require they be unset works fine with the first patch in
this set because of the existing EINVAL fallback handling in perf-record
and perf-top.
Did you have something else in mind that needs to be done?
David
next prev parent reply other threads:[~2012-09-10 17:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 16:40 [PATCH 0/3] perf: precise mode and exclude_guest David Ahern
2012-09-10 16:40 ` [PATCH 1/3] perf tool: precise mode requires exclude_guest David Ahern
2012-09-10 17:23 ` Peter Zijlstra
2012-09-10 16:40 ` [PATCH 2/3] perf: require exclude_guest to use PEBS - kernel side enforcement David Ahern
2012-09-10 17:24 ` Peter Zijlstra
2012-09-10 16:40 ` [PATCH 3/3] perf tool: give user better message if precise is not supported David Ahern
2012-09-11 9:20 ` Robert Richter
2012-09-11 13:22 ` David Ahern
2012-09-11 14:01 ` Robert Richter
2012-09-11 14:32 ` David Ahern
2012-09-11 15:11 ` Robert Richter
2012-09-12 14:59 ` David Ahern
2012-09-10 16:57 ` [PATCH 0/3] perf: precise mode and exclude_guest Peter Zijlstra
2012-09-10 17:01 ` David Ahern [this message]
2012-09-10 17:13 ` 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=504E1CD0.8040306@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=robert.richter@amd.com \
/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;
as well as URLs for NNTP newsgroup(s).