From: Jason Baron <jbaron@akamai.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"jacob.jun.pan@linux.intel.com" <jacob.jun.pan@linux.intel.com>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
"durgadoss.r@intel.com" <durgadoss.r@intel.com>,
"srinivas.pandruvada@linux.intel.com"
<srinivas.pandruvada@linux.intel.com>
Subject: Re: [PATCH] powercap/rapl: add support for cpu model 0x3f
Date: Tue, 02 Sep 2014 10:31:53 -0400 [thread overview]
Message-ID: <5405D4D9.7050103@akamai.com> (raw)
In-Reply-To: <2447035.ZSkeOUhJMy@vostro.rjw.lan>
Hi Rafael,
I think Jacob is ok with it:
https://lkml.org/lkml/2014/8/13/702
but he didn't give it a formal ack.
Thanks,
-Jason
On 09/01/2014 07:49 PM, Rafael J. Wysocki wrote:
> On Thursday, August 14, 2014 02:26:08 PM Jason Baron wrote:
>> I've confirmed that monitoring the package power usage as well as setting power
>> limits appear to be working as expected. Supports the package and dram domains.
>>
>> Tested aginst cpu:
>>
>> Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz
>>
>> Signed-off-by: Jason Baron <jbaron@akamai.com>
>
> Has this been ACKed by Jacob?
>
>> ---
>> drivers/powercap/intel_rapl.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/powercap/intel_rapl.c b/drivers/powercap/intel_rapl.c
>> index b1cda6f..a362dcc 100644
>> --- a/drivers/powercap/intel_rapl.c
>> +++ b/drivers/powercap/intel_rapl.c
>> @@ -953,6 +953,7 @@ static const struct x86_cpu_id rapl_ids[] = {
>> { X86_VENDOR_INTEL, 6, 0x3a},/* Ivy Bridge */
>> { X86_VENDOR_INTEL, 6, 0x3c},/* Haswell */
>> { X86_VENDOR_INTEL, 6, 0x3d},/* Broadwell */
>> + { X86_VENDOR_INTEL, 6, 0x3f},/* Haswell */
>> { X86_VENDOR_INTEL, 6, 0x45},/* Haswell ULT */
>> /* TODO: Add more CPU IDs after testing */
>> {}
>>
>
next prev parent reply other threads:[~2014-09-02 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 14:26 [PATCH] powercap/rapl: add support for cpu model 0x3f Jason Baron
2014-09-01 23:49 ` Rafael J. Wysocki
2014-09-02 14:31 ` Jason Baron [this message]
2014-09-02 17:41 ` Jacob Pan
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=5405D4D9.7050103@akamai.com \
--to=jbaron@akamai.com \
--cc=durgadoss.r@intel.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--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 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).