From: "Laszlo Ersek" <lersek@redhat.com>
To: Ankur Arora <ankur.a.arora@oracle.com>, devel@edk2.groups.io
Cc: imammedo@redhat.com, boris.ostrovsky@oracle.com
Subject: Re: [RFC PATCH 0/5] support CPU hot-unplug
Date: Thu, 10 Dec 2020 10:21:54 +0100 [thread overview]
Message-ID: <58d0ab9c-d50e-125f-d439-70a409bf95f0@redhat.com> (raw)
In-Reply-To: <20201208053432.2690694-1-ankur.a.arora@oracle.com>
Hi Ankur,
On 12/08/20 06:34, Ankur Arora wrote:
> [ Resending to the correct edk2 alias this time. ]
>
> Hi,
>
> This series adds support for CPU hot-unplug with OVMF.
>
> Please see this in conjunction with the QEMU v2 series posted here:
> https://lore.kernel.org/qemu-devel/20201207140739.3829993-1-imammedo@redhat.com/
>
> In particular, would be glad for comments on Patch 4, specifically
> where we should be ejecting the CPU.
>
> Right now the ejection happens in UnplugCpus() (called from
> CpuHotplugMmi()):
> + QemuCpuhpWriteCpuSelector (mMmCpuIo, RemoveApicId);
> + QemuCpuhpWriteCpuStatus (mMmCpuIo, QEMU_CPUHP_STAT_EJECTED);
>
> That is way too early -- given that the actual unplug will happen
> in SmmCpuUpdate() and given that the BSPHandler() would have waited
> for the APs multiple times before then.
>
> Another possibility is that the actual ejection be deferred to the
> _EJ0 method after the return from the SMI. But, that seems like a
> hack. Additionally, Igor points out here that this approach has problems:
> https://lore.kernel.org/qemu-devel/20201204170939.1815522-1-imammedo@redhat.com/
>
> Please review.
thanks for the patches; I'm confirming I've got them.
I'll need a non-trivial amount of time before I come to these patches
(and to the QEMU patches posted by Igor).
I'm working very busily on
<https://bugzilla.tianocore.org/show_bug.cgi?id=3097> and my brain is
full of other stuff.
We had the reverse situation earlier this year, I think, when -- in
relation to hotplug -- Igor was occupied with a more pressing QEMU
development (NUMA I think?), for a significant amount of time.
What's important is that I want to do both Igor's patches and your
patches *justice*, with my review, and at this time I just cannot sit
down with them alone for a day. These patches deserve a deep looking-at,
rather than a skim, and I cannot afford the former at the moment. I
prefer doing a (hopefully) thorough review, later, to rushing a review now.
I hope that's tolerable.
Thank you,
Laszlo
next prev parent reply other threads:[~2020-12-10 9:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 5:34 [RFC PATCH 0/5] support CPU hot-unplug ankur.a.arora
2020-12-08 5:34 ` [RFC PATCH 1/5] OvmfPkg/CpuHotplugSmm: move CPU Hotplug into PlugCpus() Ankur Arora
2020-12-08 5:34 ` [RFC PATCH 2/5] OvmfPkg/CpuHotplugSmm: handle fw_remove Ankur Arora
2020-12-08 5:34 ` [RFC PATCH 3/5] OvmfPkg/CpuHotplugSmm: add CpuStatus helper function Ankur Arora
2020-12-08 5:34 ` [RFC PATCH 4/5] OvmfPkg/CpuHotplugSmm: handle CPU hot-unplug Ankur Arora
2020-12-08 5:34 ` [RFC PATCH 5/5] OvmfPkg/SmmControl2Dxe: negotiate ICH9_LPC_SMI_F_CPU_HOT_UNPLUG Ankur Arora
2020-12-10 9:21 ` Laszlo Ersek [this message]
2020-12-10 20:08 ` [RFC PATCH 0/5] support CPU hot-unplug Ankur Arora
2020-12-11 16:21 ` [edk2-devel] " Igor Mammedov
2020-12-21 14:44 ` Laszlo Ersek
2020-12-21 15:03 ` Laszlo Ersek
2020-12-21 15:46 ` Igor Mammedov
2020-12-21 19:57 ` Laszlo Ersek
2020-12-21 19:09 ` Ankur Arora
2020-12-21 19:58 ` Laszlo Ersek
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-list 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=58d0ab9c-d50e-125f-d439-70a409bf95f0@redhat.com \
--to=devel@edk2.groups.io \
/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