From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: kazutomo <kazutomo.yoshii@gmail.com>
Cc: Linux PM <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Rafael Wysocki <rafael.j.wysocki@intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Len Brown <len.brown@intel.com>
Subject: Re: [PATCH] powercap/rapl: handle domain energy unit
Date: Fri, 13 Mar 2015 03:53:17 -0700 [thread overview]
Message-ID: <20150313035317.712e271d@ultegra> (raw)
In-Reply-To: <5502182C.90304@gmail.com>
On Thu, 12 Mar 2015 17:50:20 -0500
kazutomo <kazutomo.yoshii@gmail.com> wrote:
> On 03/12/2015 05:05 PM, Jacob Pan wrote:
> > On Thu, 12 Mar 2015 16:59:43 -0500
> > kazutomo <kazutomo.yoshii@gmail.com> wrote:
> >
> >>> according to the document, future DRAM energy unit will always be
> >>> hardcoded to 15.3uJ, no enumeration since there is no domain
> >>> specific MSR for energy unit.
> >> Which document are you referring to?
> > Intel DocID:330784-001 Sept 2014
> > Intel Xeon Processor E5-1600 and E5-2600 V2 of 2.
>
> I think V2 is Ivy Bridge. Is this typo?
>
v2 is volume 2, glad you found the doc.
BTW, i just sent out v2 of the patch to address the issues, changes are
1. use pJ for driver energy unit
2. fix max_energy_range_uj, makes it per domain
3. add reference doc info to commit message
Thanks,
Jacob
> By googling, I found a datasheet titled:
> "Intel Xeon Processor E5-1600 and E5-2600 v3 Product Families, Volume
> 2 of 2. Datasheet, September 2014, Reference Number: 330784-001 "
>
> It clearly says "ENERGY_UNIT for DRAM domain is 15.3uJ."
>
> - kaz
>
--
Jacob Pan
next prev parent reply other threads:[~2015-03-13 10:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 12:55 [PATCH] powercap/rapl: handle domain energy unit Jacob Pan
2015-03-11 21:25 ` kazutomo
2015-03-12 21:24 ` Jacob Pan
2015-03-12 21:59 ` kazutomo
2015-03-12 22:05 ` Jacob Pan
2015-03-12 22:50 ` kazutomo
2015-03-13 10:53 ` Jacob Pan [this message]
2015-03-11 22:01 ` Rafael J. Wysocki
2015-03-12 20:17 ` Jacob Pan
2015-03-12 22:24 ` Rafael J. Wysocki
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=20150313035317.712e271d@ultegra \
--to=jacob.jun.pan@linux.intel.com \
--cc=kazutomo.yoshii@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=srinivas.pandruvada@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.