From: Zhang Rui <rui.zhang@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Lin, Ming M" <ming.m.lin@intel.com>, Ingo Molnar <mingo@elte.hu>,
Matt Fleming <matt@console-pimps.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
lkml <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [RFC PATCH 2/2] perf stat: Use event group to simulate PMI on PMI-less hardware counter
Date: Fri, 12 Nov 2010 08:32:44 +0800 [thread overview]
Message-ID: <1289521964.8148.1388.camel@rui> (raw)
In-Reply-To: <1289479601.2084.76.camel@laptop>
On Thu, 2010-11-11 at 20:46 +0800, Peter Zijlstra wrote:
> On Thu, 2010-11-11 at 10:00 +0800, Zhang Rui wrote:
> > Well, the RAPL package energy perf event may need this piece of code.
> >
> > "MSR_PKG_ENERGY_STATUS is a read-only MSR. It reports the actual energy
> > use for the package domain. This MSR is updated every ~1msec. It has a
> > wraparound time of around 60 secs when power consumption is high, and
> > may be longer otherwise."
> >
> > As it's an energy counter, we should show it in "perf stat", right?
> > As it doesn't have interrupt, I want to schedule a timer interrupt every
> > 30s to update the event counter.
>
> So use a timer inside the RAPL pmu driver. No need to change the
> interface or add generic code.
Okay.
I was wondering if this can be done with the current perf framework.
If not, surely I'm okay with using a timer inside RAPL driver. :)
thanks,
rui
prev parent reply other threads:[~2010-11-12 0:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 6:15 [RFC PATCH 2/2] perf stat: Use event group to simulate PMI on PMI-less hardware counter Lin Ming
2010-11-10 12:21 ` Peter Zijlstra
2010-11-10 14:45 ` Lin Ming
2010-11-10 14:53 ` Peter Zijlstra
2010-11-10 15:06 ` Lin Ming
2010-11-10 15:08 ` Peter Zijlstra
2010-11-10 15:17 ` Matt Fleming
2010-11-11 2:00 ` Zhang Rui
2010-11-11 12:46 ` Peter Zijlstra
2010-11-12 0:32 ` Zhang Rui [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=1289521964.8148.1388.camel@rui \
--to=rui.zhang@intel.com \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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