From: Peter Zijlstra <peterz@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: mingo@kernel.org, linux-kernel <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Arnaldo Carvalho de Melo <acme@infradead.org>
Subject: Re: [RFC][PATCH] perf, intel: Expose SMI_COUNT as a fixed counter
Date: Fri, 14 Sep 2012 15:43:00 +0200 [thread overview]
Message-ID: <1347630180.7172.34.camel@twins> (raw)
In-Reply-To: <1347449261.15764.9.camel@twins>
On Wed, 2012-09-12 at 13:27 +0200, Peter Zijlstra wrote:
> Subject: perf, intel: Expose SMI_COUNT as a fixed counter
> From: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Date: Wed Sep 12 13:10:53 CEST 2012
>
> The Intel SMI_COUNT sadly isn't a proper PMU event but a free-running
> MSR, expose it by creating another fake fixed PMC and another pseudo
> event.
OK, so it looks like this MSR has the same content on all CPUs.. is this
inherent to SMIs or is that just my box being funny?
prev parent reply other threads:[~2012-09-14 13:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 11:27 [RFC][PATCH] perf, intel: Expose SMI_COUNT as a fixed counter Peter Zijlstra
2012-09-14 13:43 ` 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=1347630180.7172.34.camel@twins \
--to=peterz@infradead.org \
--cc=acme@infradead.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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