From: Dirk Brandewie <dirk.brandewie@gmail.com>
To: Nell Hardcastle <nell@spicious.com>
Cc: cpufreq@vger.kernel.org, dirk.j.brandewie@intel.com
Subject: Re: [PATCH] intel_pstate: Add Haswell CPU models
Date: Tue, 09 Jul 2013 07:54:04 -0700 [thread overview]
Message-ID: <51DC240C.3090404@intel.com> (raw)
In-Reply-To: <51CD8087.7030303@spicious.com>
On 06/28/2013 05:24 AM, Nell Hardcastle wrote:
> Enable the intel_pstate driver for Haswell CPUs and one Ivy Bridge model not already included (0x3E). I've been testing this change on the Core i5-4200u (model 0x45) and I referenced the list of models in tools/power/x86/turbostat/turbostat.c:has_nehalem_turbo_ratio_limit to determine the others.
>
> Fixes https://bugzilla.kernel.org/show_bug.cgi?id=60211
>
> Signed-off-by: Nell Hardcastle <nell@spicious.com>
> ---
> drivers/cpufreq/intel_pstate.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c
> index 07f2840..dbd1032 100644
> --- a/drivers/cpufreq/intel_pstate.c
> +++ b/drivers/cpufreq/intel_pstate.c
> @@ -522,6 +522,11 @@ static const struct x86_cpu_id intel_pstate_cpu_ids[] = {
> ICPU(0x2a, default_policy),
> ICPU(0x2d, default_policy),
> ICPU(0x3a, default_policy),
> + ICPU(0x3c, default_policy),
> + ICPU(0x3e, default_policy),
> + ICPU(0x3f, default_policy),
> + ICPU(0x45, default_policy),
> + ICPU(0x46, default_policy),
Nak for now.
We have not completed our testing on these CPUs. I would like to
get my testing done before I start seeing issues from the field come
in.
If this patch were to hangout in testing for a while it would not
hurt my feelings there it could only hurt those that knew what
they were getting into :-)
--Dirk
> {}
> };
> MODULE_DEVICE_TABLE(x86cpu, intel_pstate_cpu_ids);
>
next prev parent reply other threads:[~2013-07-09 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 12:24 [PATCH] intel_pstate: Add Haswell CPU models Nell Hardcastle
2013-06-30 15:20 ` Viresh Kumar
2013-07-09 14:54 ` Dirk Brandewie [this message]
2013-08-17 19:43 ` Ilari Stenroth
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=51DC240C.3090404@intel.com \
--to=dirk.brandewie@gmail.com \
--cc=cpufreq@vger.kernel.org \
--cc=dirk.j.brandewie@intel.com \
--cc=nell@spicious.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.