From: Jan Beulich <jbeulich@suse.com>
To: Mykyta Poturai <Mykyta_Poturai@epam.com>
Cc: "Stefano Stabellini" <sstabellini@kernel.org>,
"Julien Grall" <julien@xen.org>,
"Bertrand Marquis" <bertrand.marquis@arm.com>,
"Michal Orzel" <michal.orzel@amd.com>,
"Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Timothy Pearson" <tpearson@raptorengineering.com>,
"Alistair Francis" <alistair.francis@wdc.com>,
"Connor Davis" <connojdavis@gmail.com>,
"Oleksii Kurochko" <oleksii.kurochko@gmail.com>,
"Daniel P. Smith" <dpsmith@apertussolutions.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v7 4/6] arm/sysctl: Implement cpu hotplug ops
Date: Thu, 9 Apr 2026 17:34:15 +0200 [thread overview]
Message-ID: <467df79c-e583-495a-bbe6-4d4b7dc8f0a3@suse.com> (raw)
In-Reply-To: <b320e53c-f794-43fc-8095-d5b4b92d7362@epam.com>
On 09.04.2026 16:34, Mykyta Poturai wrote:
> On 3/30/26 15:28, Jan Beulich wrote:
>> On 30.03.2026 13:59, Mykyta Poturai wrote:
>>> --- a/xen/common/Kconfig
>>> +++ b/xen/common/Kconfig
>>> @@ -638,9 +638,9 @@ config SYSTEM_SUSPEND
>>> If unsure, say N.
>>>
>>> config CPU_HOTPLUG
>>> - bool "CPU online/offline support"
>>> - depends on X86
>>> - default y
>>> + bool "CPU online/offline support" if EXPERT || X86
>>
>> Why not just EXPERT?
>
> Should it be marked as EXPERT on x86? I considered that if the option
> was non configurable (always enabled), it should stay enabled by default
> and always visible.
As you say, it wasn't configurable before. Imo that's a good sign that, at
least for starters, we should limit its disabling to experts.
Jan
next prev parent reply other threads:[~2026-04-09 15:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 11:59 [PATCH v7 0/6] Implement CPU hotplug on Arm Mykyta Poturai
2026-03-30 11:59 ` [PATCH v7 1/6] arm/irq: Keep track of irq affinities Mykyta Poturai
2026-03-30 11:59 ` [PATCH v7 2/6] arm/irq: Migrate IRQs during CPU up/down operations Mykyta Poturai
2026-04-10 9:36 ` Oleksandr Tyshchenko
2026-03-30 11:59 ` [PATCH v7 4/6] arm/sysctl: Implement cpu hotplug ops Mykyta Poturai
2026-03-30 12:28 ` Jan Beulich
2026-04-09 14:34 ` Mykyta Poturai
2026-04-09 15:34 ` Jan Beulich [this message]
2026-03-30 11:59 ` [PATCH v7 3/6] Kconfig: Make cpu hotplug configurable Mykyta Poturai
2026-03-30 12:19 ` Jan Beulich
2026-04-08 12:21 ` Mykyta Poturai
2026-04-08 12:27 ` Jan Beulich
2026-04-09 17:35 ` Oleksandr Tyshchenko
2026-03-30 11:59 ` [PATCH v7 5/6] tools: Allow building xen-hptool without CONFIG_MIGRATE Mykyta Poturai
2026-03-30 12:32 ` Jan Beulich
2026-04-15 14:51 ` Mykyta Poturai
2026-04-16 6:49 ` Jan Beulich
2026-04-16 8:22 ` Mykyta Poturai
2026-04-16 8:27 ` Jan Beulich
2026-04-29 14:33 ` Anthony PERARD
2026-05-06 8:52 ` Mykyta Poturai
2026-05-13 14:00 ` Anthony PERARD
2026-03-30 11:59 ` [PATCH v7 6/6] docs: Document CPU hotplug Mykyta Poturai
2026-03-30 12:37 ` Jan Beulich
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=467df79c-e583-495a-bbe6-4d4b7dc8f0a3@suse.com \
--to=jbeulich@suse.com \
--cc=Mykyta_Poturai@epam.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=alistair.francis@wdc.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=bertrand.marquis@arm.com \
--cc=connojdavis@gmail.com \
--cc=dpsmith@apertussolutions.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=oleksii.kurochko@gmail.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tpearson@raptorengineering.com \
--cc=xen-devel@lists.xenproject.org \
/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.