From: Laszlo Ersek <lersek@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>, qemu-devel@nongnu.org
Cc: boris.ostrovsky@oracle.com, liran.alon@oracle.com
Subject: Re: [RFC 0/3] x86: fix cpu hotplug with secure boot
Date: Tue, 14 Jul 2020 12:10:45 +0200 [thread overview]
Message-ID: <ac0d7032-108e-1f82-f6cb-b2f3fecd3cf8@redhat.com> (raw)
In-Reply-To: <b0a2e023-9669-027e-7234-2e9ca53b8a1f@redhat.com>
On 07/14/20 11:58, Laszlo Ersek wrote:
> On 07/10/20 18:17, Igor Mammedov wrote:
>> CPU hotplug with Secure Boot was not really supported and firmware wasn't aware
>> of hotplugged CPUs (which might lead to guest crashes). During 4.2 we introduced
>> locked SMI handler RAM arrea to make sure that guest OS wasn't able to inject
>> its own SMI handler and OVMF added initial CPU hotplug support.
>>
>> This series is QEMU part of that support [1] which lets QMVF tell QEMU that
>> CPU hotplug with SMI broadcast enabled is supported so that QEMU would be able
>> to prevent hotplug in case it's not supported and trigger SMI on hotplug when
>> it's necessary.
>>
>> 1) CPU hotplug negotiation part was introduced later so it might not be
>> in upstream OVMF yet or I might have missed the patch on edk2-devel
>> (Laszlo will point out to it/post formal patch)
>
> I'll post it later, after testing it with this patch series.
(For the time being I had only attached it to
<https://bugzilla.redhat.com/show_bug.cgi?id=1849177#c1>.)
>
> Thanks!
> Laszlo
>
>>
>> Igor Mammedov (3):
>> x86: lpc9: let firmware negotiate CPU hotplug SMI feature
>> x86: cphp: prevent guest crash on CPU hotplug when broadcast SMI is in
>> use
>> x68: acpi: trigger SMI before scanning for hotplugged CPUs
>>
>> include/hw/acpi/cpu.h | 1 +
>> include/hw/i386/ich9.h | 1 +
>> hw/acpi/cpu.c | 6 ++++++
>> hw/acpi/ich9.c | 12 +++++++++++-
>> hw/i386/acpi-build.c | 33 ++++++++++++++++++++++++++++++++-
>> hw/i386/pc.c | 15 ++++++++++++++-
>> hw/isa/lpc_ich9.c | 10 ++++++++++
>> 7 files changed, 75 insertions(+), 3 deletions(-)
>>
>
next prev parent reply other threads:[~2020-07-14 10:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 16:17 [RFC 0/3] x86: fix cpu hotplug with secure boot Igor Mammedov
2020-07-10 16:17 ` [RFC 1/3] x86: lpc9: let firmware negotiate CPU hotplug SMI feature Igor Mammedov
2020-07-14 10:19 ` Laszlo Ersek
2020-07-10 16:17 ` [RFC 2/3] x86: cphp: prevent guest crash on CPU hotplug when broadcast SMI is in use Igor Mammedov
2020-07-14 10:56 ` Laszlo Ersek
2020-07-17 12:57 ` Igor Mammedov
2020-07-20 17:29 ` Laszlo Ersek
2020-07-10 16:17 ` [RFC 3/3] x68: acpi: trigger SMI before scanning for hotplugged CPUs Igor Mammedov
2020-07-14 12:28 ` Laszlo Ersek
2020-07-14 12:41 ` Laszlo Ersek
2020-07-14 15:19 ` Igor Mammedov
2020-07-15 12:38 ` Laszlo Ersek
2020-07-15 13:43 ` Igor Mammedov
2020-07-16 12:36 ` Laszlo Ersek
2020-07-17 13:13 ` Igor Mammedov
2020-07-20 19:12 ` Laszlo Ersek
2020-07-14 9:58 ` [RFC 0/3] x86: fix cpu hotplug with secure boot Laszlo Ersek
2020-07-14 10:10 ` Laszlo Ersek [this message]
2020-07-14 18:26 ` 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-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=ac0d7032-108e-1f82-f6cb-b2f3fecd3cf8@redhat.com \
--to=lersek@redhat.com \
--cc=boris.ostrovsky@oracle.com \
--cc=imammedo@redhat.com \
--cc=liran.alon@oracle.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).