From: "Ankur Arora" <ankur.a.arora@oracle.com>
To: Laszlo Ersek <lersek@redhat.com>, devel@edk2.groups.io
Cc: imammedo@redhat.com, boris.ostrovsky@oracle.com
Subject: Re: [edk2-devel] [RFC PATCH 0/5] support CPU hot-unplug
Date: Mon, 21 Dec 2020 11:09:01 -0800 [thread overview]
Message-ID: <98d3701d-f51f-0909-fd79-9ed4338eb1d8@oracle.com> (raw)
In-Reply-To: <70e6bf5d-3d59-2e6f-4b5a-2e68cdda8108@redhat.com>
On 2020-12-21 6:44 a.m., Laszlo Ersek wrote:
> 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/
>
> I've filed:
>
> https://bugzilla.tianocore.org/show_bug.cgi?id=3132
>
> Can you please register an account in the TianoCore Bugzilla at
> <https://bugzilla.tianocore.org/>, and assign the above ticket to yourself?
>
> And then, the URL of the new BZ ticket should be included in every
> commit message, like this:
>
> Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=3132
>
> just above your S-o-b.
Sure. Will do.
> No need to repost just because of this; I'll review the RFC series later.
Actually could you hold off before reviewing the RFC series. I'll be sending
a v2 series shortly. That does the actual unplug via SmmCpuFeaturesRendezvousExit()
(I had described the approach elsewhere in this thread.)
Thanks
Ankur
> Thanks,
> Laszlo
>
>>
>> Please review.
>>
>> Thanks
>> Ankur
>>
>> Ankur Arora (5):
>> OvmfPkg/CpuHotplugSmm: move CPU Hotplug into PlugCpus()
>> OvmfPkg/CpuHotplugSmm: handle fw_remove
>> OvmfPkg/CpuHotplugSmm: add CpuStatus helper function
>> OvmfPkg/CpuHotplugSmm: handle CPU hot-unplug
>> OvmfPkg/SmmControl2Dxe: negotiate ICH9_LPC_SMI_F_CPU_HOT_UNPLUG
>>
>> OvmfPkg/CpuHotplugSmm/CpuHotplug.c | 293 ++++++++++++------
>> OvmfPkg/CpuHotplugSmm/QemuCpuhp.c | 58 +++-
>> OvmfPkg/CpuHotplugSmm/QemuCpuhp.h | 6 +
>> .../Include/IndustryStandard/QemuCpuHotplug.h | 2 +
>> OvmfPkg/SmmControl2Dxe/SmiFeatures.c | 21 +-
>> 5 files changed, 280 insertions(+), 100 deletions(-)
>>
>
next prev parent reply other threads:[~2020-12-21 19:09 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 ` [RFC PATCH 0/5] support CPU hot-unplug Laszlo Ersek
2020-12-10 20:08 ` 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 [this message]
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=98d3701d-f51f-0909-fd79-9ed4338eb1d8@oracle.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