From: Zhongqiu Han <zhongqiu.han@oss.qualcomm.com>
To: Huacai Chen <chenhuacai@loongson.cn>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Huacai Chen <chenhuacai@kernel.org>
Cc: loongarch@lists.linux.dev, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, Xuerui Wang <kernel@xen0n.name>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
stable@vger.kernel.org,
Hongliang Wang <wanghongliang@loongson.cn>,
zhongqiu.han@oss.qualcomm.com
Subject: Re: [PATCH 3/5] cpufreq: loongson3: Replace per-package mutex with per-node
Date: Thu, 20 Aug 2026 19:34:57 +0800 [thread overview]
Message-ID: <3f352680-7090-456a-ab08-2d3367641783@oss.qualcomm.com> (raw)
In-Reply-To: <20260818123921.3600606-4-chenhuacai@loongson.cn>
On 8/18/2026 8:39 PM, Huacai Chen wrote:
> Our server productions (e.g. Loongson-3D6000/3E6000) can have multiple
> nodes in one package and SMC mailboxes are also per-node. So replace the
> per-package mutex with per-node one.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Hongliang Wang <wanghongliang@loongson.cn>
> Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
> ---
> drivers/cpufreq/loongson3_cpufreq.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/cpufreq/loongson3_cpufreq.c b/drivers/cpufreq/loongson3_cpufreq.c
> index 630f679aa739..e3cd78a5ab18 100644
> --- a/drivers/cpufreq/loongson3_cpufreq.c
> +++ b/drivers/cpufreq/loongson3_cpufreq.c
> @@ -169,7 +169,7 @@ struct loongson3_freq_data {
> struct cpufreq_frequency_table table[];
> };
>
> -static struct mutex cpufreq_mutex[MAX_PACKAGES];
> +static struct mutex cpufreq_mutex[MAX_NUMNODES];
> static struct cpufreq_driver loongson3_cpufreq_driver;
> static DEFINE_PER_CPU(struct loongson3_freq_data *, freq_data);
>
> @@ -177,14 +177,14 @@ static inline int do_service_request(u32 id, u32 info, u32 cmd, u32 val, u32 ext
> {
> int retries;
> unsigned int cpu = raw_smp_processor_id();
> - unsigned int package = cpu_data[cpu].package;
> + unsigned int nid = cpu_to_node(cpu);
> union smc_message msg, last;
>
> - mutex_lock(&cpufreq_mutex[package]);
> + mutex_lock(&cpufreq_mutex[nid]);
>
> last.value = iocsr_read32(LOONGARCH_IOCSR_SMCMBX);
> if (!last.complete) {
> - mutex_unlock(&cpufreq_mutex[package]);
> + mutex_unlock(&cpufreq_mutex[nid]);
> return -EPERM;
> }
>
> @@ -208,11 +208,11 @@ static inline int do_service_request(u32 id, u32 info, u32 cmd, u32 val, u32 ext
> }
>
> if (!msg.complete || msg.cmd != CMD_OK) {
> - mutex_unlock(&cpufreq_mutex[package]);
> + mutex_unlock(&cpufreq_mutex[nid]);
> return -EPERM;
> }
>
> - mutex_unlock(&cpufreq_mutex[package]);
> + mutex_unlock(&cpufreq_mutex[nid]);
An optimization independent of this patch: considering to use
guard(mutex)(xxx.lock)
>
> return msg.val;
> }
> @@ -337,7 +337,7 @@ static int loongson3_cpufreq_probe(struct platform_device *pdev)
> {
> int i, ret;
>
> - for (i = 0; i < MAX_PACKAGES; i++) {
> + for (i = 0; i < MAX_NUMNODES; i++) {
> ret = devm_mutex_init(&pdev->dev, &cpufreq_mutex[i]);
> if (ret)
> return ret;
--
Thx and BRs,
Zhongqiu Han
next prev parent reply other threads:[~2026-08-20 11:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 12:39 [PATCH 0/5] cpufreq: loongson3: Fix wrong behaviors on multi-node servers Huacai Chen
2026-08-18 12:39 ` [PATCH 1/5] cpufreq: loongson3: Make this drvier depend on MACH_LOONGSON64 Huacai Chen
2026-08-20 9:23 ` Zhongqiu Han
2026-08-18 12:39 ` [PATCH 2/5] cpufreq: loongson3: Adjust the width of id and val in smc_message Huacai Chen
2026-08-20 10:03 ` Zhongqiu Han
2026-08-18 12:39 ` [PATCH 3/5] cpufreq: loongson3: Replace per-package mutex with per-node Huacai Chen
2026-08-20 11:34 ` Zhongqiu Han [this message]
2026-08-20 12:35 ` Zhongqiu Han
2026-08-21 4:54 ` Xi Ruoyao
2026-08-18 12:39 ` [PATCH 4/5] cpufreq: loongson3: Use global physical CPU ID in get/target callbacks Huacai Chen
2026-08-20 12:23 ` Zhongqiu Han
2026-08-18 12:39 ` [PATCH 5/5] cpufreq: loongson3: Replace IOCSR read/write with MMIO ones Huacai Chen
2026-08-20 12:57 ` Zhongqiu Han
2026-08-21 5:01 ` Xi Ruoyao
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=3f352680-7090-456a-ab08-2d3367641783@oss.qualcomm.com \
--to=zhongqiu.han@oss.qualcomm.com \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=rafael@kernel.org \
--cc=stable@vger.kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=wanghongliang@loongson.cn \
/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