From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
"H. Peter Anvin" <hpa@zytor.com>,
Stephane Eranian <eranian@google.com>,
Paul Mackerras <paulus@samba.org>,
Andi Kleen <andi.kleen@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [PATCH v3] perf/rapl: support per domain energy unit
Date: Mon, 15 Jun 2015 13:07:44 -0700 [thread overview]
Message-ID: <20150615130744.338995e0@icelake> (raw)
In-Reply-To: <alpine.DEB.2.20.1506151328290.8520@vincent-weaver-1.umelst.maine.edu>
On Mon, 15 Jun 2015 13:32:01 -0400 (EDT)
Vince Weaver <vincent.weaver@maine.edu> wrote:
> On Thu, 26 Mar 2015, Jacob Pan wrote:
>
> > RAPL energy hardware unit can vary within a single CPU package, e.g.
> > HSW server DRAM has a fixed energy unit of 15.3 uJ (2^-16) whereas
> > the unit on other domains can be enumerated from power unit MSR.
> > There might be other variations in the future, this patch adds
> > per cpu model quirk to allow special handling of certain cpus.
>
> So I have a Desktop Haswell machine (model 60) that is instrumented
> to measure actual DRAM power at the DIMM (with a sense resistor).
>
> We are consistently getting RAPL results roughly a factor of 2
> smaller than the actual, measured results.
>
> Does desktop Haswell have a similar units issue to Haswell-EP?
>
Not that I know of. perhaps has to do with the difference of what
and where we are measuring. Let me find a instrumented system to verify
and get back to you.
> I wasted a bunch of time trying to decode the
> DRAM_ENERGY_SCALEFACTOR_MCHBAR values described in the
> Desktop 4th Generation Intel Core Processor Family
> datasheet but possibly that value in the MCHBAR is unrelated to the
> one exported by the RAPL interface.
>
This scale factor is not directly related to the energy counter. The
MMIO DRAM RAPL energy status uses the same unit as the MSR interface,
the resolution is ~61uJ.
> Vince
[Jacob Pan]
next prev parent reply other threads:[~2015-06-15 20:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 17:32 [PATCH v3] perf/rapl: support per domain energy unit Vince Weaver
2015-06-15 20:07 ` Jacob Pan [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-26 21:28 Jacob Pan
2015-04-06 15:21 ` Jacob Pan
2015-04-06 17:30 ` Stephane Eranian
2015-04-15 15:08 ` Jacob Pan
2015-04-15 15:40 ` Peter Zijlstra
2015-04-15 16:19 ` Jacob Pan
2015-04-15 16:36 ` 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=20150615130744.338995e0@icelake \
--to=jacob.jun.pan@linux.intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=andi.kleen@intel.com \
--cc=eranian@google.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
--cc=vincent.weaver@maine.edu \
/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