From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Jacob Pan <jacob.jun.pan@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Rafael Wysocki <rafael.j.wysocki@intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: Re: [PATCH] powercap/intel_rapl: Add support for Kabylake
Date: Mon, 25 Apr 2016 16:20:17 +0200 [thread overview]
Message-ID: <CAJZ5v0imwM3RCPM8QTWSWwEOfyCUZUTECMEa1hQOhyCLW06K_g@mail.gmail.com> (raw)
In-Reply-To: <1461345439-21215-1-git-send-email-jacob.jun.pan@linux.intel.com>
On Fri, Apr 22, 2016 at 7:17 PM, Jacob Pan
<jacob.jun.pan@linux.intel.com> wrote:
> Kabylake is similar to Skylake in terms of RAPL.
>
> Signed-off-by: Jacob Pan <jacob.jun.pan@linux.intel.com>
How urgent is this?
Can we live without it in 4.6 in particular?
> ---
> drivers/powercap/intel_rapl.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/powercap/intel_rapl.c b/drivers/powercap/intel_rapl.c
> index 8fad0a7..470bb62 100644
> --- a/drivers/powercap/intel_rapl.c
> +++ b/drivers/powercap/intel_rapl.c
> @@ -1101,6 +1101,8 @@ static const struct x86_cpu_id rapl_ids[] __initconst = {
> 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 */
> + RAPL_CPU(0x8E, rapl_defaults_core),/* Kabylake */
> + RAPL_CPU(0x9E, rapl_defaults_core),/* Kabylake */
> {}
> };
> MODULE_DEVICE_TABLE(x86cpu, rapl_ids);
> --
> 1.9.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-04-25 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 17:17 [PATCH] powercap/intel_rapl: Add support for Kabylake Jacob Pan
2016-04-25 14:20 ` Rafael J. Wysocki [this message]
2016-04-25 15:36 ` Jacob Pan
2016-04-27 21:34 ` 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=CAJZ5v0imwM3RCPM8QTWSWwEOfyCUZUTECMEa1hQOhyCLW06K_g@mail.gmail.com \
--to=rafael@kernel.org \
--cc=jacob.jun.pan@linux.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 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).