From: Zhang Rui <rui.zhang@intel.com>
To: peterz@infradead.org
Cc: LKML <linux-kernel@vger.kernel.org>,
mingo@elte.hu, robert.richter@amd.com, acme@redhat.com,
paulus@samba.org, dzickus@redhat.com, gorcunov@gmail.com,
fweisbec@gmail.com, Lin Ming <ming.m.lin@intel.com>,
"Brown, Len" <lenb@kernel.org>,
Matthew Garrett <mjg59@srcf.ucam.org>,
"Zhang, Rui" <rui.zhang@intel.com>
Subject: [RFC PATCH 0/3] perf: show package power consumption in perf
Date: Wed, 18 Aug 2010 15:59:10 +0800 [thread overview]
Message-ID: <1282118350.5181.115.camel@rui> (raw)
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. :)
thanks,
rui
next reply other threads:[~2010-08-18 7:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 7:59 Zhang Rui [this message]
2010-08-18 12:25 ` [RFC PATCH 0/3] perf: show package power consumption in perf Peter Zijlstra
2010-08-18 12:41 ` Matt Fleming
2010-08-19 3:28 ` Lin Ming
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=1282118350.5181.115.camel@rui \
--to=rui.zhang@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=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
--cc=mjg59@srcf.ucam.org \
--cc=paulus@samba.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).