From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Guixiong Wei <weiguixiong@bytedance.com>
Cc: hansg@kernel.org, ilpo.jarvinen@linux.intel.com,
rafael.j.wysocki@intel.com, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, wangyijia.yeah@bytedance.com,
stable@vger.kernel.org
Subject: Re: [PATCH] platform/x86/intel-uncore-freq: Continue restoring limits on resume
Date: Wed, 30 Sep 2026 13:28:20 -0700 [thread overview]
Message-ID: <f3f665ca76f9d914bf4b91cf03358223596d922d.camel@linux.intel.com> (raw)
In-Reply-To: <20260929163133.14326-2-weiguixiong@bytedance.com>
On Wed, 2026-09-30 at 00:31 +0800, Guixiong Wei wrote:
> The PM notifier iterates over every uncore frequency instance to
> restore
> user-configured MSR_UNCORE_RATIO_LIMIT values after resume. Entries
> that
> have never been configured legitimately have stored_uncore_data set
> to
> zero.
>
> The refactoring that split common and enumeration code changed the
> iteration from active control CPUs to all allocated instances. It
> also
> changed the skip for an invalid or unconfigured entry from continue
> to
> return, causing that entry to terminate the entire restore operation.
>
> On a multi-package or multi-die system, configuring only a later
> instance
> therefore leaves its limit unrestored after suspend, hibernation, or
> restore if an earlier entry is invalid or unconfigured.
>
> Use continue to skip only the current entry and restore all remaining
> configured instances.
>
> Fixes: dbce412a7733 ("platform/x86/intel-uncore-freq: Split common
> and enumeration part")
> Cc: stable@vger.kernel.org
> Tested-by: Yijia Wang <wangyijia.yeah@bytedance.com>
> Signed-off-by: Guixiong Wei <weiguixiong@bytedance.com>
Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> ---
> drivers/platform/x86/intel/uncore-frequency/uncore-frequency.c | 2
> +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/platform/x86/intel/uncore-frequency/uncore-
> frequency.c b/drivers/platform/x86/intel/uncore-frequency/uncore-
> frequency.c
> index 667f2c8b9594a..c44e7e38cae25 100644
> --- a/drivers/platform/x86/intel/uncore-frequency/uncore-frequency.c
> +++ b/drivers/platform/x86/intel/uncore-frequency/uncore-frequency.c
> @@ -211,7 +211,7 @@ static int uncore_pm_notify(struct notifier_block
> *nb, unsigned long mode,
> struct uncore_data *data =
> &uncore_instances[i];
>
> if (!data || !data->valid || !data-
> >stored_uncore_data)
> - return 0;
> + continue;
>
> wrmsrq_on_cpu(data->control_cpu,
> MSR_UNCORE_RATIO_LIMIT,
> data->stored_uncore_data);
prev parent reply other threads:[~2026-09-30 20:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 16:31 Guixiong Wei
2026-09-30 20:28 ` srinivas pandruvada [this message]
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=f3f665ca76f9d914bf4b91cf03358223596d922d.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=stable@vger.kernel.org \
--cc=wangyijia.yeah@bytedance.com \
--cc=weiguixiong@bytedance.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
all inboxes | Powered by JetHome®