From: Vasily Gorbik <gor@linux.ibm.com>
To: Mete Durlu <meted@linux.ibm.com>
Cc: Heiko Carstens <hca@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Ilya Leoshkevich <iii@linux.ibm.com>,
linux-s390@vger.kernel.org
Subject: Re: [PATCH] s390/smp: Reflect (de)configured CPUs to cpu_enabled_mask
Date: Wed, 29 Jul 2026 15:01:48 +0200 [thread overview]
Message-ID: <ttixtj0@ub.hpns> (raw)
In-Reply-To: <20260723-enabled_cpus-v1-1-3a2cbdc374b0@linux.ibm.com>
On Thu, Jul 23, 2026 at 03:36:43PM +0200, Mete Durlu wrote:
> On s390, CPUs can be in a state where it is not possible to hotplug
> them online before certain prequisite steps. For example the CPUs which
> get introduced during runtime of a system can posses a "deconfigured"
> state which prevents them from being hotplugged online before they get
> configured. Another case is when users set the configured state of CPUs
> themselves via "chcpu" or sysfs attributes.
>
> On s390 available CPUs are being registered as new devices via
> smp_add_core() either during boot or after a CPU rescan (for newly added
> CPUs during runtime). Registered CPUs are marked as enabled without
> considering the configure states. Add necessary checks to smp_add_core()
> and userspace configure attribute handler. Reflect the configured CPUs
> to cpu_enabled_mask to correctly represent which CPUs can be hotplugged
> online.
>
> Signed-off-by: Mete Durlu <meted@linux.ibm.com>
> ---
> 4e1a7df45480 ("cpumask: Add enabled cpumask for present CPUs that can
> be brought online") introduces a new cpumask to signify which CPUs can
> be hotplugged online at a given time.
>
> Originally the concept is introduced to reflect CPUs which are being
> kept offline by firmware decisions. For s390 the configure state of the
> CPUs matches this concept. CPUs can assume configured or deconfigured
> state. When a CPU is in deconfigured state, it cannot be brought online
> util it is back in configured state.
>
> On s390 available CPUs are being registered as new devices via
> smp_add_core() either during boot or after a CPU rescan (for newly added
> CPUs during runtime). Registered CPUs are marked as enabled without
> considering the configure states. Add necessary checks to smp_add_core()
> and userspace configure attribute handler. Reflect the configured CPUs
> to cpu_enabled_mask to correctly represent which CPUs can be hotplugged
> online.
> ---
> arch/s390/kernel/smp.c | 5 +++++
> 1 file changed, 5 insertions(+)
Applied, thank you!
prev parent reply other threads:[~2026-07-29 13:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260723-enabled_cpus-v1-1-3a2cbdc374b0@linux.ibm.com>
2026-07-23 13:56 ` [PATCH] s390/smp: Reflect (de)configured CPUs to cpu_enabled_mask sashiko-bot
2026-07-23 14:03 ` Heiko Carstens
2026-07-29 13:01 ` Vasily Gorbik [this message]
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=ttixtj0@ub.hpns \
--to=gor@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=iii@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox