From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Thomas Gleixner <tglx@linutronix.de>,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: intel_pstate_get_hwp_cap on wrong CPU
Date: Fri, 31 May 2024 13:02:00 +0200 [thread overview]
Message-ID: <20240531110200.CtBSN_p4@linutronix.de> (raw)
In-Reply-To: <ca47b6f812175ea60f6ad615274223aa7fee295d.camel@linux.intel.com>
On 2024-05-29 16:08:19 [-0700], srinivas pandruvada wrote:
> Hi Sebastian,
Hi,
> On Wed, 2024-05-29 at 17:57 +0200, Sebastian Andrzej Siewior wrote:
> > Hi,
> >
> > this just popped up:
> > > [ 6538.614568] unchecked MSR access error: RDMSR from 0x771 at rIP:
>
> Please check if the attached change fixes?
it should based on the callchain. Let me test it in a few…
Would you mind letting
/sys/devices/system/cpu/intel_pstate/num_pstates
reporting something sane? Not 4294967285 but 0 for instance? Would that
make sense?
But
…
> From f85a83508ef029bceaf9192cb648d66f32b61d02 Mon Sep 17 00:00:00 2001
> From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> Date: Wed, 29 May 2024 15:30:49 -0700
> Subject: [PATCH] cpufreq: intel_pstate: Fix unchecked HWP MSR access
>
> HWP MSR 0x771 can be only read on a CPU which supports HWP and enabled.
> Hence intel_pstate_get_hwp_cap() can only be called when hwp_active is
> true.
>
> Reported-by: Sebastian Reichel <sebastian.reichel@collabora.com>
Did Sebastian _Reichel_ report it, too?
> Closes: https://lore.kernel.org/linux-pm/20240529155740.Hq2Hw7be@linutronix.de/
Because this my report ;)
> Fixes: e8217b4bece3 ("cpufreq: intel_pstate: Update the maximum CPU frequency consistently")
> Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Sebastian
next prev parent reply other threads:[~2024-05-31 11:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 15:57 intel_pstate_get_hwp_cap on wrong CPU Sebastian Andrzej Siewior
2024-05-29 23:08 ` srinivas pandruvada
2024-05-31 11:02 ` Sebastian Andrzej Siewior [this message]
2024-05-31 11:56 ` srinivas pandruvada
2024-05-31 14:01 ` Sebastian Andrzej Siewior
2024-05-31 22:27 ` srinivas pandruvada
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=20240531110200.CtBSN_p4@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=lenb@kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.org \
/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