From: sashiko-bot@kernel.org
To: "Mete Durlu" <meted@linux.ibm.com>
Cc: "Alexander Gordeev" <agordeev@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>,
"Heiko Carstens" <hca@linux.ibm.com>,
linux-s390@vger.kernel.org
Subject: Re: [PATCH RFC 2/2] s390/topology: Enable SCHED_IDLE_SMT_PRIO
Date: Thu, 08 Oct 2026 08:40:21 +0000 [thread overview]
Message-ID: <sashiko-outbox-163846@kernel.org> (raw)
In-Reply-To: <20261008-hiperdispatchfix-v1-2-73fe41081070@linux.ibm.com>
> On s390, vertical polarization configuration assigns CPUs different
> polarization values and capacities. These capacities represent the
> virtual runtime being assigned to the shared CPUs by the underlying
> hypervisor. Consequently running load on high capacity cores, even if
> the SMT sibling (SMT=2 on s390) of a given core is busy is more
> favorable compared to a fully idle low capacity CPU.
>
> Implement arch_needs_idle_smt_prio() to enable the sched_idle_smt_prio
> static branch when the machine has hardware backed topology.
>
> Signed-off-by: Mete Durlu <meted@linux.ibm.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261008-hiperdispatchfix-v1-0-73fe41081070@linux.ibm.com?part=2
next prev parent reply other threads:[~2026-10-08 8:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 8:30 [PATCH RFC 0/2] sched: Introduce idle SMT priority for asymmetric capacity systems Mete Durlu
2026-10-08 8:30 ` [PATCH RFC 1/2] kernel/sched: Introduce idle SMT priority Mete Durlu
2026-10-08 8:45 ` sashiko-bot
2026-10-08 8:30 ` [PATCH RFC 2/2] s390/topology: Enable SCHED_IDLE_SMT_PRIO Mete Durlu
2026-10-08 8:40 ` sashiko-bot [this message]
2026-10-08 12:10 ` [PATCH RFC 0/2] sched: Introduce idle SMT priority for asymmetric capacity systems Andrea Righi
2026-10-08 14:58 ` Shrikanth Hegde
2026-10-08 15:24 ` Mete Durlu
2026-10-08 15:44 ` Shrikanth Hegde
2026-10-09 15:12 ` Andrea Righi
2026-10-09 15:35 ` Shrikanth Hegde
2026-10-12 12:32 ` Mete Durlu
2026-10-12 13:49 ` Shrikanth Hegde
2026-10-13 10:24 ` Mete Durlu
2026-10-09 15:32 ` Vincent Guittot
2026-10-12 11:04 ` Mete Durlu
2026-10-12 14:49 ` Vincent Guittot
2026-10-13 10:50 ` Mete Durlu
2026-10-13 11:19 ` Shrikanth Hegde
2026-10-13 12:40 ` Mete Durlu
2026-10-08 21:52 ` Tim Chen
2026-10-08 21:29 ` Tim Chen
2026-10-12 10:41 ` 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=sashiko-outbox-163846@kernel.org \
--to=sashiko-bot@kernel.org \
--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=sashiko-reviews@lists.linux.dev \
/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.