From: Cyrill Gorcunov <gorcunov@openvz.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>, Jiri Olsa <jolsa@redhat.com>,
Lin Ming <ming.m.lin@intel.com>, rostedt <rostedt@goodmis.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH] perf, p4: Add format attributes
Date: Wed, 28 Mar 2012 02:03:43 +0400 [thread overview]
Message-ID: <20120327220343.GG16537@moon> (raw)
In-Reply-To: <20120327151250.GG11875@moon>
On Tue, Mar 27, 2012 at 07:12:50PM +0400, Cyrill Gorcunov wrote:
>
> Ah, I see thanks for the reference, Peter!
>
> > I've still not actually read the P4-PMU specs, so I don't know if
> > there's anything more convenient we can do on P4. If there's a
> > better/more useful format representation possible, don't hesitate to
> > send a patch! :-)
>
> Sure, I'll try to find some time tonight to read this brand
> new stuff. And if I find something -- will send out. At moment
> your patch should be more than enough ;)
Hi, Peter, sorry for delay,
after looking some more I think ht bit might be dropped from
the format, it's used internally by the kernel in attmept to
eliminate redundant msr poking if new event runs on the same
thread as previous one, and it's always cleared before real
write to msr happens, which means user-space might set or
clear it, but it never be considered by the kernel.
(still my earlier reviewed-by is valid because this ht bit
is harmless ;)
Cyrill
next prev parent reply other threads:[~2012-03-27 22:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 14:50 [PATCH] perf, p4: Add format attributes Peter Zijlstra
2012-03-27 14:57 ` Cyrill Gorcunov
2012-03-27 15:05 ` Cyrill Gorcunov
2012-03-27 15:05 ` Peter Zijlstra
2012-03-27 15:07 ` Peter Zijlstra
2012-03-27 15:12 ` Cyrill Gorcunov
2012-03-27 22:03 ` Cyrill Gorcunov [this message]
2012-03-27 22:05 ` Peter Zijlstra
2012-03-27 22:11 ` Cyrill Gorcunov
2012-04-03 8:11 ` [tip:perf/urgent] perf/x86/p4: " tip-bot for 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=20120327220343.GG16537@moon \
--to=gorcunov@openvz.org \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox