From: Jan Beulich <jbeulich@suse.com>
To: Mykyta Poturai <Mykyta_Poturai@epam.com>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v7 6/6] docs: Document CPU hotplug
Date: Mon, 30 Mar 2026 14:37:00 +0200 [thread overview]
Message-ID: <c5cef874-b47c-4b18-a069-e6656fed6080@suse.com> (raw)
In-Reply-To: <97ad7b68c5e42fc396b155ef1d0a69a738b28881.1774871881.git.mykyta_poturai@epam.com>
On 30.03.2026 13:59, Mykyta Poturai wrote:
> --- a/SUPPORT.md
> +++ b/SUPPORT.md
> @@ -52,6 +52,7 @@ For the Cortex A77 r0p0 - r1p0, see Errata 1508412.
> ### ACPI CPU Hotplug
>
> Status, x86: Experimental
> + Status, Arm64: Experimental
Are you sure? I didn't spot an ACPI connection in the patches (in particular
in patch 4).
Jan
next prev parent reply other threads:[~2026-03-30 12:37 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 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 1/6] arm/irq: Keep track of irq affinities Mykyta Poturai
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
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 6/6] docs: Document CPU hotplug Mykyta Poturai
2026-03-30 12:37 ` Jan Beulich [this message]
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
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=c5cef874-b47c-4b18-a069-e6656fed6080@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=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.