From: Jan Beulich <jbeulich@suse.com>
To: Mykyta Poturai <Mykyta_Poturai@epam.com>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Teddy Astie" <teddy.astie@vates.tech>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Julien Grall" <julien@xen.org>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v8 3/6] Kconfig: Make cpu hotplug configurable
Date: Fri, 15 May 2026 14:21:37 +0200 [thread overview]
Message-ID: <ff29493d-e855-40b7-9a0d-d2e43dbe7aff@suse.com> (raw)
In-Reply-To: <c32ac85498cd4dd4c1654e81b8880ce3c5149c01.1778845596.git.mykyta_poturai@epam.com>
On 15.05.2026 13:54, Mykyta Poturai wrote:
> --- a/xen/common/Kconfig
> +++ b/xen/common/Kconfig
> @@ -636,6 +636,14 @@ config SYSTEM_SUSPEND
>
> If unsure, say N.
>
> +config CPU_ONLINE_OFFLINE
> + bool "CPU online/offline support"
The "if EXPERT" that the next patch adds wants to move here. Then:
Acked-by: Jan Beulich <jbeulich@suse.com>
Jan
next prev parent reply other threads:[~2026-05-15 12:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 11:54 [PATCH v8 0/6] Implement CPU hotplug on Arm Mykyta Poturai
2026-05-15 11:54 ` [PATCH v8 1/6] arm/irq: Keep track of irq affinities Mykyta Poturai
2026-05-15 11:54 ` [PATCH v8 2/6] arm/irq: Migrate IRQs during CPU up/down operations Mykyta Poturai
2026-05-15 11:54 ` [PATCH v8 4/6] arm/sysctl: Implement cpu hotplug ops Mykyta Poturai
2026-05-15 12:18 ` Jan Beulich
2026-05-15 11:54 ` [PATCH v8 3/6] Kconfig: Make cpu hotplug configurable Mykyta Poturai
2026-05-15 12:21 ` Jan Beulich [this message]
2026-05-15 11:54 ` [PATCH v8 5/6] tools: Allow building xen-hptool without CONFIG_MIGRATE Mykyta Poturai
2026-05-15 12:29 ` Jan Beulich
2026-05-15 11:55 ` [PATCH v8 6/6] docs: Document CPU hotplug Mykyta Poturai
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=ff29493d-e855-40b7-9a0d-d2e43dbe7aff@suse.com \
--to=jbeulich@suse.com \
--cc=Mykyta_Poturai@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=teddy.astie@vates.tech \
--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.