From: Jason Baron <jbaron@akamai.com>
To: Jacob Pan <jacob.jun.pan@linux.intel.com>
Cc: "rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
"durgadoss.r@intel.com" <durgadoss.r@intel.com>,
"srivatsa.bhat@linux.vnet.ibm.com"
<srivatsa.bhat@linux.vnet.ibm.com>,
"srinivas.pandruvada@linux.intel.com"
<srinivas.pandruvada@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] powercap/rapl: add support for cpu model 0x3f
Date: Thu, 14 Aug 2014 10:21:22 -0400 [thread overview]
Message-ID: <53ECC5E2.5080903@akamai.com> (raw)
In-Reply-To: <20140813155035.2af00ef5@ultegra>
On 08/13/2014 06:50 PM, Jacob Pan wrote:
> On Wed, 13 Aug 2014 20:33:26 +0000 (GMT)
> Jason Baron <jbaron@akamai.com> wrote:
>
>> I've confirmed that monitoring the package power usage as well
>> as setting power limits appear to be working as expected. However,
>> I do see in the logs:
>>
>> [ 5.082632] intel_rapl: RAPL domain core detection failed
>> [ 5.088370] intel_rapl: RAPL domain uncore detection failed
>>
>> So I'm not sure if the h/w simply doesn't support that, or if the
>> driver could be improved here. In any case, adding the 0x3f makes
>> the driver useful for me. Tested aginst cpu:
>>
>> Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz
>>
> I don't have this CPU model to test. Most server processors don't
> have uncore domain so detection failed is normal. Looks like you just
> have package and dram domain?
Yes.
> Thanks for testing it out, looks good to me. can you send it to
> linux-pm list and cc rafael?
>
Ok.
Thanks,
-Jason
next prev parent reply other threads:[~2014-08-14 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 20:33 [PATCH] powercap/rapl: add support for cpu model 0x3f Jason Baron
2014-08-13 22:50 ` Jacob Pan
2014-08-14 14:21 ` Jason Baron [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-14 14:26 Jason Baron
2014-09-01 23:49 ` Rafael J. Wysocki
2014-09-02 14:31 ` Jason Baron
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=53ECC5E2.5080903@akamai.com \
--to=jbaron@akamai.com \
--cc=durgadoss.r@intel.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=srivatsa.bhat@linux.vnet.ibm.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.