mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Guixiong Wei <weiguixiong@bytedance.com>,
	hansg@kernel.org,  ilpo.jarvinen@linux.intel.com,
	platform-driver-x86@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] platform/x86/intel-uncore-freq: Fix current_freq_khz after CPU hotplug
Date: Tue, 02 Jun 2026 09:13:02 -0700	[thread overview]
Message-ID: <db99c3312d96656d90788444ee8cf0105ac988cb.camel@linux.intel.com> (raw)
In-Reply-To: <20260602020752.3126-1-weiguixiong@bytedance.com>

On Tue, 2026-06-02 at 10:07 +0800, Guixiong Wei wrote:
> When the last CPU of a legacy uncore die goes offline,
> uncore_freq_remove_die_entry() clears control_cpu. During CPU hotplug
> re-add, uncore_freq_add_entry() still populates sysfs attributes
> before
> assigning the new control CPU. As a result, the current frequency
> read
> returns -ENXIO and current_freq_khz is omitted from the recreated
> sysfs
> group.
> 
> Assign control_cpu before the initial read paths and before
> create_attr_group() so sysfs recreation uses the new online CPU. If
> sysfs creation fails, restore control_cpu to -1 to keep the error
> path
> state consistent.
> 
> Fixes: 4d73c6772ab7 ("platform/x86: intel-uncore-freq: Conditionally
> create attribute for read frequency")
> Cc: stable@vger.kernel.org
> Signed-off-by: Guixiong Wei <weiguixiong@bytedance.com>

Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>


> ---
>  .../x86/intel/uncore-frequency/uncore-frequency-common.c   | 7
> ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/platform/x86/intel/uncore-frequency/uncore-
> frequency-common.c b/drivers/platform/x86/intel/uncore-
> frequency/uncore-frequency-common.c
> index 7070c94324e0..f8137ee92e47 100644
> --- a/drivers/platform/x86/intel/uncore-frequency/uncore-frequency-
> common.c
> +++ b/drivers/platform/x86/intel/uncore-frequency/uncore-frequency-
> common.c
> @@ -275,15 +275,20 @@ int uncore_freq_add_entry(struct uncore_data
> *data, int cpu)
>  			  data->package_id, data->die_id);
>  	}
>  
> +	/*
> +	 * Set the control CPU before any read path so entry
> recreation after CPU
> +	 * hotplug can populate read-only attributes from the new
> online CPU.
> +	 */
> +	data->control_cpu = cpu;
>  	uncore_read(data, &data->initial_min_freq_khz,
> UNCORE_INDEX_MIN_FREQ);
>  	uncore_read(data, &data->initial_max_freq_khz,
> UNCORE_INDEX_MAX_FREQ);
>  
>  	ret = create_attr_group(data, data->name);
>  	if (ret) {
> +		data->control_cpu = -1;
>  		if (data->domain_id != UNCORE_DOMAIN_ID_INVALID)
>  			ida_free(&intel_uncore_ida, data-
> >instance_id);
>  	} else {
> -		data->control_cpu = cpu;
>  		data->valid = true;
>  	}
>  

  reply	other threads:[~2026-06-02 16:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02  2:07 Guixiong Wei
2026-06-02 16:13 ` srinivas pandruvada [this message]
2026-06-10 13:29 ` Ilpo Järvinen

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=db99c3312d96656d90788444ee8cf0105ac988cb.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=stable@vger.kernel.org \
    --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®