From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: Xiaolong Wang <xiaolong.wang@linux.intel.com>
Cc: linux-pm@vger.kernel.org, rjw@rjwysocki.net,
jacob.jun.pan@linux.intel.com
Subject: Re: [PATCH] powercap/intel_rapl: Add support for Ivy Bridge server
Date: Thu, 23 Jun 2016 06:34:35 -0700 [thread overview]
Message-ID: <20160623063435.2d1d963a@yairi> (raw)
In-Reply-To: <1466667204-26340-1-git-send-email-xiaolong.wang@linux.intel.com>
On Thu, 23 Jun 2016 15:33:24 +0800
Xiaolong Wang <xiaolong.wang@linux.intel.com> wrote:
> It's confirmed that RAPL works as expected on Ivy Bridge servers.
> Tested against processor: Intel(R) Xeon(R) CPU E5-2697 v2 @2.70GHz
>
> Signed-off-by: Xiaolong Wang <xiaolong.wang@linux.intel.com>
looks good to me but please always send to lkml as well.
> ---
> 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 06d21e6..fbab29d 100644
> --- a/drivers/powercap/intel_rapl.c
> +++ b/drivers/powercap/intel_rapl.c
> @@ -1134,6 +1134,7 @@ static const struct x86_cpu_id rapl_ids[]
> __initconst = { RAPL_CPU(INTEL_FAM6_SANDYBRIDGE_X,
> rapl_defaults_core),
> RAPL_CPU(INTEL_FAM6_IVYBRIDGE,
> rapl_defaults_core),
> + RAPL_CPU(INTEL_FAM6_IVYBRIDGE_X, rapl_defaults_core),
>
> RAPL_CPU(INTEL_FAM6_HASWELL_CORE, rapl_defaults_core),
> RAPL_CPU(INTEL_FAM6_HASWELL_ULT, rapl_defaults_core),
next prev parent reply other threads:[~2016-06-23 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 7:33 [PATCH] powercap/intel_rapl: Add support for Ivy Bridge server Xiaolong Wang
2016-06-23 13:34 ` Jacob Pan [this message]
2016-07-04 13:04 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2016-06-24 3:28 Xiaolong Wang
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=20160623063435.2d1d963a@yairi \
--to=jacob.jun.pan@linux.intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=xiaolong.wang@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