All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>
To: "Zhang, Rui" <rui.zhang@intel.com>,
	"Wiles, Amy L" <amy.l.wiles@intel.com>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Cc: "jacob.jun.pan@linux.intel.com" <jacob.jun.pan@linux.intel.com>
Subject: Re: [PATCH] The x86 cpu RAPL id was added in to support BXT core
Date: Tue, 13 Oct 2015 23:07:21 +0000	[thread overview]
Message-ID: <1444777614.10629.6.camel@intel.com> (raw)
In-Reply-To: <1444751963-23743-1-git-send-email-amy.l.wiles@intel.com>

On Tue, 2015-10-13 at 08:59 -0700, amy.l.wiles@intel.com wrote:
> From: Amy Wiles <amy.l.wiles@intel.com>
> 
> BUG=None
> TEST=Navigate to /sys/class/powercap and check that the directory 
> intel-rapl:0 is present
Remove above lines and just say "Enabled Broxton RAPL support".
Copied to Jacob.

Thanks,
Srinivas


> Signed-off-by: Amy Wiles <amy.l.wiles@intel.com>
> ---
>  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 5efacd0..cc97f08 100644
> --- a/drivers/powercap/intel_rapl.c
> +++ b/drivers/powercap/intel_rapl.c
> @@ -1102,6 +1102,7 @@ static const struct x86_cpu_id rapl_ids[]
> __initconst = {
>  	RAPL_CPU(0x4A, rapl_defaults_tng),/* Tangier */
>  	RAPL_CPU(0x56, rapl_defaults_core),/* Future Xeon */
>  	RAPL_CPU(0x5A, rapl_defaults_ann),/* Annidale */
> +	RAPL_CPU(0X5C, rapl_defaults_core),/* Broxton */
>  	RAPL_CPU(0x5E, rapl_defaults_core),/* Skylake-H/S */
>  	RAPL_CPU(0x57, rapl_defaults_hsw_server),/* Knights Landing
> */
>  	{}

  reply	other threads:[~2015-10-13 23:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13 15:59 [PATCH] The x86 cpu RAPL id was added in to support BXT core amy.l.wiles
2015-10-13 23:07 ` Pandruvada, Srinivas [this message]
2015-10-14  4:53   ` Jacob Pan
  -- strict thread matches above, loose matches on Subject: below --
2015-10-13 16:13 amy.l.wiles

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=1444777614.10629.6.camel@intel.com \
    --to=srinivas.pandruvada@intel.com \
    --cc=amy.l.wiles@intel.com \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=rui.zhang@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.