From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
dirk.brandewie@gmail.com,
Dirk Brandewie <dirk.j.brandewie@intel.com>
Subject: Re: [Update][PATCH] intel_pstate: Fix type mismatch warning
Date: Wed, 16 Oct 2013 10:24:46 -0700 [thread overview]
Message-ID: <525ECBDE.5000801@linux.intel.com> (raw)
In-Reply-To: <2582369.lNhAMrrx8s@vostro.rjw.lan>
On 10/16/2013 05:53 AM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> The expression in line 398 of intel_pstate.c causes the following
> warning to be emitted:
>
> drivers/cpufreq/intel_pstate.c:398:3: warning: left shift count >= width of type
>
> which happens because unsigned long is 32-bit on some architectures.
> Fix that by using a helper u64 variable and simplify the code
> slightly.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> ---
> drivers/cpufreq/intel_pstate.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> Index: linux-pm/drivers/cpufreq/intel_pstate.c
> ===================================================================
> --- linux-pm.orig/drivers/cpufreq/intel_pstate.c
> +++ linux-pm/drivers/cpufreq/intel_pstate.c
> @@ -383,6 +383,7 @@ static void intel_pstate_get_min_max(str
> static void intel_pstate_set_pstate(struct cpudata *cpu, int pstate)
> {
> int max_perf, min_perf;
> + u64 val;
>
> intel_pstate_get_min_max(cpu, &min_perf, &max_perf);
>
> @@ -394,11 +395,11 @@ static void intel_pstate_set_pstate(stru
> trace_cpu_frequency(pstate * 100000, cpu->cpu);
>
> cpu->pstate.current_pstate = pstate;
> + val = pstate << 8;
> if (limits.no_turbo)
> - wrmsrl(MSR_IA32_PERF_CTL, BIT(32) | (pstate << 8));
> - else
> - wrmsrl(MSR_IA32_PERF_CTL, pstate << 8);
> + val |= (u64)1 << 32;
>
> + wrmsrl(MSR_IA32_PERF_CTL, val);
> }
>
> static inline void intel_pstate_pstate_increase(struct cpudata *cpu, int steps)
>
>
Tested with this change.
Thanks,
Srinivas
next prev parent reply other threads:[~2013-10-16 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 23:09 [PATCH] intel_pstate: Fix type mismatch warning Rafael J. Wysocki
2013-10-16 12:53 ` [Update][PATCH] " Rafael J. Wysocki
2013-10-16 17:24 ` Srinivas Pandruvada [this message]
2013-10-16 20:52 ` Rafael J. Wysocki
2013-10-16 21:05 ` [Resend][PATCH] " 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=525ECBDE.5000801@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=dirk.brandewie@gmail.com \
--cc=dirk.j.brandewie@intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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).