From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: lirongqing <lirongqing@baidu.com>
Cc: "Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Kristen Carlson Accardi" <kristen.c.accardi@intel.com>,
"Srinivas Pandruvada" <srinivas.pandruvada@linux.intel.com>,
"Tero Kristo" <tero.kristo@linux.intel.com>,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] platform/x86: TPMI: clean up CPU mappings on offline
Date: Wed, 4 Nov 2026 17:39:24 +0200 [thread overview]
Message-ID: <autRrIIDU3hlwtU9@ashevche-desk.local> (raw)
In-Reply-To: <20261104032724.1824-1-lirongqing@baidu.com>
On Wed, Nov 04, 2026 at 11:27:24AM +0800, lirongqing wrote:
>
> The TPMI power domain driver adds each online CPU to a hash table and
> its power domain mask, but does not remove either entry when the CPU
> goes offline. Bringing a CPU back online can therefore insert the same
> hlist node again and leave stale CPU mask state.
>
> Register an offline callback that removes the hash entry and clears the
> CPU from its power domain mask.
...
> +static int tpmi_cpu_offline(unsigned int cpu)
> +{
> + struct tpmi_cpu_info *info = &per_cpu(tpmi_cpu_info, cpu);
> + int index;
> +
> + if (hlist_unhashed(&info->hnode) || !tpmi_domain_is_valid(info))
> + return 0;
> +
> + index = info->pkg_id * MAX_POWER_DOMAINS + info->punit_domain_id;
> +
> + guard(mutex)(&tpmi_lock);
+ Blank line, so we can see at glance the lock usage.
No need to resend just for this, unless Ilpo asks for it.
> + cpumask_clear_cpu(cpu, &tpmi_power_domain_mask[index]);
> + hash_del(&info->hnode);
> +
> + return 0;
> +}
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-11-04 15:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 3:27 [PATCH] platform/x86: TPMI: clean up CPU mappings on offline lirongqing
2026-11-04 15:30 ` Srinivas Pandruvada
2026-11-05 3:09 ` 答复: [外部邮件] " Li,Rongqing
2026-11-05 16:00 ` srinivas pandruvada
2026-11-04 15:39 ` Andy Shevchenko [this message]
2026-11-12 23:49 ` 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=autRrIIDU3hlwtU9@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kristen.c.accardi@intel.com \
--cc=lirongqing@baidu.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tero.kristo@linux.intel.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.