From: Euan Bourke <euan@linux.ibm.com>
To: hca@linux.ibm.com, gor@linux.ibm.com, agordeev@linux.ibm.com,
borntraeger@linux.ibm.com, svens@linux.ibm.com
Cc: meted@linux.ibm.com, linux-s390@vger.kernel.org, euan@linux.ibm.com
Subject: [PATCH v2] s390/hiperdispatch: use system_dfl_wq to reschedule hd_capacity_work
Date: Fri, 11 Sep 2026 11:13:09 +0200 [thread overview]
Message-ID: <20260911091309.1238604-1-euan@linux.ibm.com> (raw)
In hd_enable_hiperdispatch(), hd_capacity_work is scheduled on
system_dfl_wq, however the work function reschedules itself with
schedule_delayed_work(), which uses system_percpu_wq.
Hiperdispatch does not benefit from using the percpu workqueue. Use
queue_delayed_work() with system_dfl_wq for consistency.
Changing the workqueue from system_percpu_wq to system_dfl_wq causes no
functional changes.
Signed-off-by: Euan Bourke <euan@linux.ibm.com>
---
v2:
- use queue_delayed_work() instead of mod_delayed_work()
arch/s390/kernel/hiperdispatch.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/s390/kernel/hiperdispatch.c b/arch/s390/kernel/hiperdispatch.c
index 217206522266..8494823559b1 100644
--- a/arch/s390/kernel/hiperdispatch.c
+++ b/arch/s390/kernel/hiperdispatch.c
@@ -265,7 +265,7 @@ static void hd_capacity_work_fn(struct work_struct *work)
}
trace_s390_hd_work_fn(steal_percentage, hd_entitled_cores, hd_high_capacity_cores);
mutex_unlock(&smp_cpu_state_mutex);
- schedule_delayed_work(&hd_capacity_work, HD_DELAY_INTERVAL);
+ queue_delayed_work(system_dfl_wq, &hd_capacity_work, HD_DELAY_INTERVAL);
}
static int hiperdispatch_ctl_handler(const struct ctl_table *ctl, int write,
--
2.54.0
next reply other threads:[~2026-09-11 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 9:13 Euan Bourke [this message]
2026-09-11 9:20 ` [PATCH v2] s390/hiperdispatch: use system_dfl_wq to reschedule hd_capacity_work sashiko-bot
2026-09-11 9:47 ` Mete Durlu
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=20260911091309.1238604-1-euan@linux.ibm.com \
--to=euan@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=meted@linux.ibm.com \
--cc=svens@linux.ibm.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.