From: Lin Ming <ming.m.lin@intel.com>
To: Matt Fleming <matt@console-pimps.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
"Zhang, Rui" <rui.zhang@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
"mingo@elte.hu" <mingo@elte.hu>,
"robert.richter@amd.com" <robert.richter@amd.com>,
"acme@redhat.com" <acme@redhat.com>,
"paulus@samba.org" <paulus@samba.org>,
"dzickus@redhat.com" <dzickus@redhat.com>,
"gorcunov@gmail.com" <gorcunov@gmail.com>,
"fweisbec@gmail.com" <fweisbec@gmail.com>,
"Brown, Len" <lenb@kernel.org>,
Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: [RFC PATCH 0/3] perf: show package power consumption in perf
Date: Thu, 19 Aug 2010 11:28:17 +0800 [thread overview]
Message-ID: <1282188497.11858.94.camel@minggr.sh.intel.com> (raw)
In-Reply-To: <20100818124116.GA17957@console-pimps.org>
On Wed, 2010-08-18 at 20:41 +0800, Matt Fleming wrote:
> On Wed, Aug 18, 2010 at 02:25:29PM +0200, Peter Zijlstra wrote:
> > On Wed, 2010-08-18 at 15:59 +0800, Zhang Rui wrote:
> > > Hi, all,
> > >
> > > RAPL(running average power limit) is a new feature which provides
> > > mechanisms to enforce power consumption limit, on some new processors.
> > >
> > > Generally speaking, by using RAPL, OS can set a power budget in a
> > > certain time window, and let Hardware to throttle the processor
> > > P/T-state to meet this energy limitation.
> > >
> > > RAPL also provides a new MSR, i.e. MSR_PKG_ENERGY_STATUS, which reports
> > > the total amount of energy consumed by the package.
> > >
> > > I'm not sure if to support RAPL or not, but anyway, it sounds like a
> > > good idea to export the energy status in perf.
> > >
> > > So a new perf pmu and event to show the package energy consumed is
> > > introduced in this patch.
> > >
> > > Here is what I get after applying the three patches,
> > >
> > > #./perf stat -e energy test
> > > Performance counter stats for 'test':
> > >
> > > 202 Joules cost by package
> > > 7.926001238 seconds time elapsed
> > >
> > >
> > > Note that this patch set is made based on Peter's perf-pmu branch,
> > > git://git.kernel.org/pub/scm/linux/kernel/git/peterz/linux-2.6-perf.git
> > > which provides better interfaces to register/unregister a new pmu.
> > >
> > > any comment are welcome. :)
> >
> >
> > Nice,.. however:
> >
> > - if it is a pure read-only counter without sampling support,
> > expose it as such, don't fudge in the hrtimer stuff. Simply
> > fail to create a sampling event.
> >
> > SH has the same problem for its 'normal' PMU, the solution is
> > to use event groups, Matt was looking at adding support to
> > perf-record for that, if creating a sampling event fails, fall
> > back to {hrtimer, $event} groups.
>
> I had a quick look over the patches and Peter is right - the group
> events stuff would probably fit quite well here. Unfortunately, due to
> holidays and things, I haven't been able to get them finished
> yet. I'll get on that ASAP.
Hi, Matt
What's the "group events stuff"?
Is there some discussion on LKML or elsewhere I can have a look at?
Thanks,
Lin Ming
next prev parent reply other threads:[~2010-08-19 3:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 7:59 Zhang Rui
2010-08-18 12:25 ` Peter Zijlstra
2010-08-18 12:41 ` Matt Fleming
2010-08-19 3:28 ` Lin Ming [this message]
2010-08-19 7:54 ` Matt Fleming
2010-08-19 8:15 ` Lin Ming
2010-08-19 8:31 ` Zhang Rui
2010-08-19 8:32 ` Matt Fleming
2010-08-19 9:44 ` Peter Zijlstra
2010-08-21 1:18 ` Frederic Weisbecker
2010-08-21 9:30 ` Ingo Molnar
2010-08-23 9:31 ` Peter Zijlstra
2010-08-19 9:02 ` Peter Zijlstra
2010-08-20 1:44 ` Zhang Rui
2010-08-20 9:34 ` Peter Zijlstra
2010-08-20 12:31 ` Ingo Molnar
2010-08-20 21:34 ` acme
2010-08-19 2:43 ` Lin Ming
2010-08-19 8:54 ` Peter Zijlstra
2010-08-20 0:21 ` Lin Ming
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=1282188497.11858.94.camel@minggr.sh.intel.com \
--to=ming.m.lin@intel.com \
--cc=acme@redhat.com \
--cc=dzickus@redhat.com \
--cc=fweisbec@gmail.com \
--cc=gorcunov@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=mingo@elte.hu \
--cc=mjg59@srcf.ucam.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=robert.richter@amd.com \
--cc=rui.zhang@intel.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
Powered by JetHome