x86: fix cpu hotplug with secure boot
v2 cover x86: fix cpu hotplug with secure boot
v2:
- AML: clean is_inserted flag only after SMI callback
- make x-smi-cpu-hotunplug false by default
- massage error hint on not supported unplug
v1:
- fix typos and some phrases (Laszlo)
- add unplug check (Laszlo)
- redo AML scan logic to avoid race when adding multiple CPUs
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 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.
Igor Mammedov (7):
x86: lpc9: let firmware negotiate 'CPU hotplug with SMI' features
x86: cphp: prevent guest crash on CPU hotplug when broadcast SMI is in
use
x86: cpuhp: refuse cpu hot-unplug request earlier if not supported
acpi: add aml_land() and aml_break() primitives
tests: acpi: mark to be changed tables in
bios-tables-test-allowed-diff
x68: acpi: trigger SMI before sending hotplug Notify event to OSPM
tests: acpi: update acpi blobs with new AML
include/hw/acpi/aml-build.h | 2 + include/hw/acpi/cpu.h | 1 + include/hw/i386/ich9.h | 4 ++ include/hw/i386/pc.h | 3 ++ hw/acpi/aml-build.c | 16 ++++++ hw/acpi/cpu.c | 80 ++++++++++++++++++++++++++++-- hw/acpi/ich9.c | 24 ++++++++- hw/i386/acpi-build.c | 35 ++++++++++++- hw/i386/pc.c | 17 ++++++- hw/i386/pc_piix.c | 1 + hw/i386/pc_q35.c | 1 + hw/isa/lpc_ich9.c | 16 ++++++ tests/data/acpi/pc/DSDT | Bin 4934 -> 5009 bytes tests/data/acpi/pc/DSDT.acpihmat | Bin 6258 -> 6334 bytes tests/data/acpi/pc/DSDT.bridge | Bin 6793 -> 6868 bytes tests/data/acpi/pc/DSDT.cphp | Bin 5397 -> 5473 bytes tests/data/acpi/pc/DSDT.dimmpxm | Bin 6587 -> 6663 bytes tests/data/acpi/pc/DSDT.ipmikcs | Bin 5006 -> 5081 bytes tests/data/acpi/pc/DSDT.memhp | Bin 6293 -> 6368 bytes tests/data/acpi/pc/DSDT.numamem | Bin 4940 -> 5015 bytes tests/data/acpi/q35/DSDT | Bin 7678 -> 7753 bytes tests/data/acpi/q35/DSDT.acpihmat | Bin 9002 -> 9078 bytes tests/data/acpi/q35/DSDT.bridge | Bin 7695 -> 7770 bytes tests/data/acpi/q35/DSDT.cphp | Bin 8141 -> 8217 bytes tests/data/acpi/q35/DSDT.dimmpxm | Bin 9331 -> 9407 bytes tests/data/acpi/q35/DSDT.ipmibt | Bin 7753 -> 7828 bytes tests/data/acpi/q35/DSDT.memhp | Bin 9037 -> 9112 bytes tests/data/acpi/q35/DSDT.mmio64 | Bin 8808 -> 8883 bytes tests/data/acpi/q35/DSDT.numamem | Bin 7684 -> 7759 bytes tests/data/acpi/q35/DSDT.tis | Bin 8283 -> 8358 bytes 30 files changed, 192 insertions(+), 8 deletions(-)
Signature · 1 line
2.26.2
PATCH v2 1/7 x86: lpc9: let firmware negotiate 'CPU hotplug with SMI' features
It will allow firmware to notify QEMU that firmware requires SMI being triggered on CPU hot[un]plug, so that it would be able to account for hotplugged CPU and relocate it to new SMM base and/or safely remove CPU on unplug.
Using negotiated features, follow up patches will insert SMI upcall into AML code, to make sure that firmware processes hotplug before guest OS would attempt to use new CPU.
---
v2:
- rebase on top of 5.1 (move compat values to 5.1 machine)
- make "x-smi-cpu-hotunplug" false by default (Laszlo Ersek <[email protected]>)
--- include/hw/i386/ich9.h | 2 ++ include/hw/i386/pc.h | 3 +++ hw/i386/pc.c | 6 +++++- hw/i386/pc_piix.c | 1 + hw/i386/pc_q35.c | 1 + hw/isa/lpc_ich9.c | 13 +++++++++++++ 6 files changed, 25 insertions(+), 1 deletion(-)
include/hw/i386/ich9.h +2 -0
@@ -247,5 +247,7 @@ typedef struct ICH9LPCState {/* bit positions used in fw_cfg SMI feature negotiation */ #define ICH9_LPC_SMI_F_BROADCAST_BIT 0 +#define ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT 1 +#define ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT 2#endif /* HW_ICH9_H */
include/hw/i386/pc.h +3 -0
@@ -193,6 +193,9 @@ void pc_system_firmware_init(PCMachineState *pcms, MemoryRegion *rom_memory);void pc_madt_cpu_entry (AcpiDeviceIf *adev,int uid,const CPUArchIdList *apic_ids,GArray *entry); +extern GlobalProperty pc_compat_5_1[]; +extern const size_t pc_compat_5_1_len; +extern GlobalProperty pc_compat_5_0[];extern const size_t pc_compat_5_0_len;
hw/i386/pc.c +5 -1
@@ -97,8 +97,12 @@#include "fw_cfg.h" #include "trace.h" -GlobalProperty pc_compat_5_0[] = { +GlobalProperty pc_compat_5_1[] = { + {"ICH9-LPC" ,"x-smi-cpu-hotplug" ,"off" }, }; +const size_t pc_compat_5_1_len =G_N_ELEMENTS (pc_compat_5_1); + +GlobalProperty pc_compat_5_0[] = { };const size_t pc_compat_5_0_len =G_N_ELEMENTS (pc_compat_5_0);GlobalProperty pc_compat_4_2[] = {
hw/i386/pc_piix.c +1 -0
@@ -433,6 +433,7 @@ static void pc_i440fx_5_1_machine_options(MachineClass *m) m->alias ="pc" ; m->is_default = true; pcmc->default_cpu_version =1 ; +compat_props_add (m->compat_props, pc_compat_5_1, pc_compat_5_1_len); } DEFINE_I440FX_MACHINE(v5_1, "pc-i440fx-5.1", NULL,
hw/i386/pc_q35.c +1 -0
@@ -359,6 +359,7 @@ static void pc_q35_5_1_machine_options(MachineClass *m)pc_q35_machine_options (m); m->alias ="q35" ; pcmc->default_cpu_version =1 ; +compat_props_add (m->compat_props, pc_compat_5_1, pc_compat_5_1_len); } DEFINE_Q35_MACHINE(v5_1, "pc-q35-5.1", NULL,
hw/isa/lpc_ich9.c +13 -0
@@ -373,6 +373,15 @@ static void smi_features_ok_callback(void *opaque)/* guest requests invalid features, leave @features_ok at zero */ return ; } +if (!(guest_features &BIT_ULL (ICH9_LPC_SMI_F_BROADCAST_BIT )) && + guest_features & (BIT_ULL (ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT ) | +BIT_ULL (ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT ))) { +/* +* cpu hot-[un]plug with SMI requires SMI broadcast, +* leave @features_ok at zero +*/ +return ; + }/* valid feature subset requested, lock it down, report success */ lpc->smi_negotiated_features = guest_features;
@@ -747,6 +756,10 @@ static Property ich9_lpc_properties[] = {DEFINE_PROP_BOOL ("noreboot" , ICH9LPCState, pin_strap.spkr_hi, true),DEFINE_PROP_BIT64 ("x-smi-broadcast" , ICH9LPCState, smi_host_features,ICH9_LPC_SMI_F_BROADCAST_BIT , true), +DEFINE_PROP_BIT64 ("x-smi-cpu-hotplug" , ICH9LPCState, smi_host_features, +ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT , true), +DEFINE_PROP_BIT64 ("x-smi-cpu-hotunplug" , ICH9LPCState, smi_host_features, +ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT , false), DEFINE_PROP_END_OF_LIST(), };
Signature · 1 line
2.26.2
Re: [PATCH v2 1/7] x86: lpc9: let firmware negotiate 'CPU hotplug with SMI' features
Hi Igor,
(CC'ing Daniel, Cornelia, David, Peter)
Quoted 114 lines · Igor Mammedov
It will allow firmware to notify QEMU that firmware requires SMI being triggered on CPU hot[un]plug, so that it would be able to account for hotplugged CPU and relocate it to new SMM base and/or safely remove CPU on unplug.
Using negotiated features, follow up patches will insert SMI upcall into AML code, to make sure that firmware processes hotplug before guest OS would attempt to use new CPU.
Signed-off-by Igor Mammedov <[email protected]>Reviewed-by Laszlo Ersek <[email protected]>---
v2:
- rebase on top of 5.1 (move compat values to 5.1 machine)
- make "x-smi-cpu-hotunplug" false by default (Laszlo Ersek <[email protected]>)--- include/hw/i386/ich9.h | 2 ++ include/hw/i386/pc.h | 3 +++ hw/i386/pc.c | 6 +++++- hw/i386/pc_piix.c | 1 + hw/i386/pc_q35.c | 1 + hw/isa/lpc_ich9.c | 13 +++++++++++++ 6 files changed, 25 insertions(+), 1 deletion(-)include/hw/i386/ich9.h +2
-0@@ -247,5 +247,7 @@ typedef struct ICH9LPCState {/* bit positions used in fw_cfg SMI feature negotiation */ #define ICH9_LPC_SMI_F_BROADCAST_BIT 0 +#define ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT 1 +#define ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT 2#endif /* HW_ICH9_H */ include/hw/i386/pc.h +3
-0@@ -193,6 +193,9 @@ void pc_system_firmware_init(PCMachineState *pcms, MemoryRegion *rom_memory);void pc_madt_cpu_entry (AcpiDeviceIf *adev,int uid,const CPUArchIdList *apic_ids,GArray *entry); +extern GlobalProperty pc_compat_5_1[]; +extern const size_t pc_compat_5_1_len; +extern GlobalProperty pc_compat_5_0[];extern const size_t pc_compat_5_0_len;hw/i386/pc.c +5
-1@@ -97,8 +97,12 @@#include "fw_cfg.h" #include "trace.h" -GlobalProperty pc_compat_5_0[] = { +GlobalProperty pc_compat_5_1[] = { + {"ICH9-LPC" ,"x-smi-cpu-hotplug" ,"off" }, }; +const size_t pc_compat_5_1_len =G_N_ELEMENTS (pc_compat_5_1); + +GlobalProperty pc_compat_5_0[] = { };const size_t pc_compat_5_0_len =G_N_ELEMENTS (pc_compat_5_0);GlobalProperty pc_compat_4_2[] = {hw/i386/pc_piix.c +1
-0@@ -433,6 +433,7 @@ static void pc_i440fx_5_1_machine_options(MachineClass *m) m->alias ="pc" ; m->is_default = true; pcmc->default_cpu_version =1 ; +compat_props_add (m->compat_props, pc_compat_5_1, pc_compat_5_1_len); } DEFINE_I440FX_MACHINE(v5_1, "pc-i440fx-5.1", NULL,hw/i386/pc_q35.c +1
-0@@ -359,6 +359,7 @@ static void pc_q35_5_1_machine_options(MachineClass *m)pc_q35_machine_options (m); m->alias ="q35" ; pcmc->default_cpu_version =1 ; +compat_props_add (m->compat_props, pc_compat_5_1, pc_compat_5_1_len); } DEFINE_Q35_MACHINE(v5_1, "pc-q35-5.1", NULL,hw/isa/lpc_ich9.c +9
-0@@ -373,6 +373,15 @@ static void smi_features_ok_callback(void *opaque)/* guest requests invalid features, leave @features_ok at zero */ return ; } +if (!(guest_features &BIT_ULL (ICH9_LPC_SMI_F_BROADCAST_BIT )) && + guest_features & (BIT_ULL (ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT ) | +BIT_ULL (ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT ))) { +/* +* cpu hot-[un]plug with SMI requires SMI broadcast, +* leave @features_ok at zero +*/ +return ; + }/* valid feature subset requested, lock it down, report success */ lpc->smi_negotiated_features = guest_features;
hw/isa/lpc_ich9.c static Property ich9_lpc_properties[] = { · line 765
Quoted 10 lines
hw/isa/lpc_ich9.c +4
-0@@ -747,6 +756,10 @@ static Property ich9_lpc_properties[] = {DEFINE_PROP_BOOL ("noreboot" , ICH9LPCState, pin_strap.spkr_hi, true),DEFINE_PROP_BIT64 ("x-smi-broadcast" , ICH9LPCState, smi_host_features,ICH9_LPC_SMI_F_BROADCAST_BIT , true), +DEFINE_PROP_BIT64 ("x-smi-cpu-hotplug" , ICH9LPCState, smi_host_features, +ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT , true), +DEFINE_PROP_BIT64 ("x-smi-cpu-hotunplug" , ICH9LPCState, smi_host_features, +ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT , false), DEFINE_PROP_END_OF_LIST(), };
this patch does the right thing for the 5.1 PC machine types, but it does not introduce any 5.2 machine types, so I can't enable the hotplug feature bit without messing with the x-smi-cpu-hotplug property manually.
Now... looking at the mailing list, I can see the following patch pending review (posted by Daniel ~5 days ago):
[PATCH 01/10] hw: add compat machines for 5.2
http://mid.mail-archive.com/[email protected]
That patch introduces the 5.2 PC machine types.
However, I can't just apply your series on top of that one patch, because they conflict at least on the "pc_compat_5_1" array.
Given that Daniel's patch was posted before yours, and also that Daniel's patch introduces 5.2 machine types for arm, ppc and s390x too (and the "hw_compat_5_1" array in addition to the "pc_compat_5_1" array), I'd like to request:
- that we please review and/or merge Daniel's patch in isolation (just the first patch in the containing series, not the entire series!),
- and that you please rebase your series on top of Daniel's patch.
If Daniel's patch is approved as-is on the list, then I'm OK applying it locally in isolation from the rest of the containing series, as a basis for locally applying your v3.
(I could resolve the conflicts myself at once I guess, and proceed with the review / testing -- but that's not really useful if I want to give a formal Tested-by. I wouldn't be testing the patches as they were posted.)
Thanks!
Laszlo
Re: [PATCH v2 1/7] x86: lpc9: let firmware negotiate 'CPU hotplug with SMI' features
correcting myself a bit, with Drew and Thomas CC'd as well:
Quoted 156 lines · Laszlo Ersek
Hi Igor,
(CC'ing Daniel, Cornelia, David, Peter)
Quoted 114 lines · Igor Mammedov
It will allow firmware to notify QEMU that firmware requires SMI being triggered on CPU hot[un]plug, so that it would be able to account for hotplugged CPU and relocate it to new SMM base and/or safely remove CPU on unplug.
Using negotiated features, follow up patches will insert SMI upcall into AML code, to make sure that firmware processes hotplug before guest OS would attempt to use new CPU.
Signed-off-by Igor Mammedov <[email protected]>Reviewed-by Laszlo Ersek <[email protected]>---
v2:
- rebase on top of 5.1 (move compat values to 5.1 machine)
- make "x-smi-cpu-hotunplug" false by default (Laszlo Ersek <[email protected]>)--- include/hw/i386/ich9.h | 2 ++ include/hw/i386/pc.h | 3 +++ hw/i386/pc.c | 6 +++++- hw/i386/pc_piix.c | 1 + hw/i386/pc_q35.c | 1 + hw/isa/lpc_ich9.c | 13 +++++++++++++ 6 files changed, 25 insertions(+), 1 deletion(-)include/hw/i386/ich9.h +2
-0@@ -247,5 +247,7 @@ typedef struct ICH9LPCState {/* bit positions used in fw_cfg SMI feature negotiation */ #define ICH9_LPC_SMI_F_BROADCAST_BIT 0 +#define ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT 1 +#define ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT 2#endif /* HW_ICH9_H */ include/hw/i386/pc.h +3
-0@@ -193,6 +193,9 @@ void pc_system_firmware_init(PCMachineState *pcms, MemoryRegion *rom_memory);void pc_madt_cpu_entry (AcpiDeviceIf *adev,int uid,const CPUArchIdList *apic_ids,GArray *entry); +extern GlobalProperty pc_compat_5_1[]; +extern const size_t pc_compat_5_1_len; +extern GlobalProperty pc_compat_5_0[];extern const size_t pc_compat_5_0_len;hw/i386/pc.c +5
-1@@ -97,8 +97,12 @@#include "fw_cfg.h" #include "trace.h" -GlobalProperty pc_compat_5_0[] = { +GlobalProperty pc_compat_5_1[] = { + {"ICH9-LPC" ,"x-smi-cpu-hotplug" ,"off" }, }; +const size_t pc_compat_5_1_len =G_N_ELEMENTS (pc_compat_5_1); + +GlobalProperty pc_compat_5_0[] = { };const size_t pc_compat_5_0_len =G_N_ELEMENTS (pc_compat_5_0);GlobalProperty pc_compat_4_2[] = {hw/i386/pc_piix.c +1
-0@@ -433,6 +433,7 @@ static void pc_i440fx_5_1_machine_options(MachineClass *m) m->alias ="pc" ; m->is_default = true; pcmc->default_cpu_version =1 ; +compat_props_add (m->compat_props, pc_compat_5_1, pc_compat_5_1_len); } DEFINE_I440FX_MACHINE(v5_1, "pc-i440fx-5.1", NULL,hw/i386/pc_q35.c +1
-0@@ -359,6 +359,7 @@ static void pc_q35_5_1_machine_options(MachineClass *m)pc_q35_machine_options (m); m->alias ="q35" ; pcmc->default_cpu_version =1 ; +compat_props_add (m->compat_props, pc_compat_5_1, pc_compat_5_1_len); } DEFINE_Q35_MACHINE(v5_1, "pc-q35-5.1", NULL,hw/isa/lpc_ich9.c +9
-0@@ -373,6 +373,15 @@ static void smi_features_ok_callback(void *opaque)/* guest requests invalid features, leave @features_ok at zero */ return ; } +if (!(guest_features &BIT_ULL (ICH9_LPC_SMI_F_BROADCAST_BIT )) && + guest_features & (BIT_ULL (ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT ) | +BIT_ULL (ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT ))) { +/* +* cpu hot-[un]plug with SMI requires SMI broadcast, +* leave @features_ok at zero +*/ +return ; + }/* valid feature subset requested, lock it down, report success */ lpc->smi_negotiated_features = guest_features;hw/isa/lpc_ich9.c static Property ich9_lpc_properties[] = { · line 765
Quoted 10 lines
hw/isa/lpc_ich9.c +4
-0@@ -747,6 +756,10 @@ static Property ich9_lpc_properties[] = {DEFINE_PROP_BOOL ("noreboot" , ICH9LPCState, pin_strap.spkr_hi, true),DEFINE_PROP_BIT64 ("x-smi-broadcast" , ICH9LPCState, smi_host_features,ICH9_LPC_SMI_F_BROADCAST_BIT , true), +DEFINE_PROP_BIT64 ("x-smi-cpu-hotplug" , ICH9LPCState, smi_host_features, +ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT , true), +DEFINE_PROP_BIT64 ("x-smi-cpu-hotunplug" , ICH9LPCState, smi_host_features, +ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT , false), DEFINE_PROP_END_OF_LIST(), };this patch does the right thing for the 5.1 PC machine types, but it does not introduce any 5.2 machine types, so I can't enable the hotplug feature bit without messing with the x-smi-cpu-hotplug property manually.
Now... looking at the mailing list, I can see the following patch pending review (posted by Daniel ~5 days ago):
[PATCH 01/10] hw: add compat machines for 5.2
http://mid.mail-archive.com/[email protected]That patch introduces the 5.2 PC machine types.
However, I can't just apply your series on top of that one patch, because they conflict at least on the "
pc_compat_5_1" array.Given that Daniel's patch was posted before yours, and also that Daniel's patch introduces 5.2 machine types for arm, ppc and s390x too (and the "
hw_compat_5_1" array in addition to the "pc_compat_5_1" array), I'd like to request:- that we please review and/or merge Daniel's patch in isolation (just the first patch in the containing series, not the entire series!),
- and that you please rebase your series on top of Daniel's patch.
Quoted 8 lines
If Daniel's patch is approved as-is on the list, then I'm OK applying it locally in isolation from the rest of the containing series, as a basis for locally applying your v3.
(I could resolve the conflicts myself at once I guess, and proceed with the review / testing -- but that's not really useful if I want to give a formal Tested-by. I wouldn't be testing the patches as they were posted.)
Sorry, I've just realized: the patch in question was originally written by Cornelia. And it's been on the list for a good time now -- it's been multiply reviewed, and also picked up in other series several times:
Original posting, with reviews:
http://mid.mail-archive.com/[email protected]
Picked into another series (different from Daniel's):
http://mid.mail-archive.com/[email protected]
Peter, would you please consider pushing that one patch directly? It seems to be a choke point.
Thanks!
Laszlo
Re: [PATCH v2 1/7] x86: lpc9: let firmware negotiate 'CPU hotplug with SMI' features
In reply to Laszlo ErsekQuoted 138 lines · On Wed, 19 Aug 2020 10:39:04 +0200 Laszlo Ersek <[email protected]> wrote:
Hi Igor,
(CC'ing Daniel, Cornelia, David, Peter)
Quoted 114 lines · Igor Mammedov
It will allow firmware to notify QEMU that firmware requires SMI being triggered on CPU hot[un]plug, so that it would be able to account for hotplugged CPU and relocate it to new SMM base and/or safely remove CPU on unplug.
Using negotiated features, follow up patches will insert SMI upcall into AML code, to make sure that firmware processes hotplug before guest OS would attempt to use new CPU.
Signed-off-by Igor Mammedov <[email protected]>Reviewed-by Laszlo Ersek <[email protected]>---
v2:
- rebase on top of 5.1 (move compat values to 5.1 machine)
- make "x-smi-cpu-hotunplug" false by default (Laszlo Ersek <[email protected]>)--- include/hw/i386/ich9.h | 2 ++ include/hw/i386/pc.h | 3 +++ hw/i386/pc.c | 6 +++++- hw/i386/pc_piix.c | 1 + hw/i386/pc_q35.c | 1 + hw/isa/lpc_ich9.c | 13 +++++++++++++ 6 files changed, 25 insertions(+), 1 deletion(-)include/hw/i386/ich9.h +2
-0@@ -247,5 +247,7 @@ typedef struct ICH9LPCState {/* bit positions used in fw_cfg SMI feature negotiation */ #define ICH9_LPC_SMI_F_BROADCAST_BIT 0 +#define ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT 1 +#define ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT 2#endif /* HW_ICH9_H */ include/hw/i386/pc.h +3
-0@@ -193,6 +193,9 @@ void pc_system_firmware_init(PCMachineState *pcms, MemoryRegion *rom_memory);void pc_madt_cpu_entry (AcpiDeviceIf *adev,int uid,const CPUArchIdList *apic_ids,GArray *entry); +extern GlobalProperty pc_compat_5_1[]; +extern const size_t pc_compat_5_1_len; +extern GlobalProperty pc_compat_5_0[];extern const size_t pc_compat_5_0_len;hw/i386/pc.c +5
-1@@ -97,8 +97,12 @@#include "fw_cfg.h" #include "trace.h" -GlobalProperty pc_compat_5_0[] = { +GlobalProperty pc_compat_5_1[] = { + {"ICH9-LPC" ,"x-smi-cpu-hotplug" ,"off" }, }; +const size_t pc_compat_5_1_len =G_N_ELEMENTS (pc_compat_5_1); + +GlobalProperty pc_compat_5_0[] = { };const size_t pc_compat_5_0_len =G_N_ELEMENTS (pc_compat_5_0);GlobalProperty pc_compat_4_2[] = {hw/i386/pc_piix.c +1
-0@@ -433,6 +433,7 @@ static void pc_i440fx_5_1_machine_options(MachineClass *m) m->alias ="pc" ; m->is_default = true; pcmc->default_cpu_version =1 ; +compat_props_add (m->compat_props, pc_compat_5_1, pc_compat_5_1_len); } DEFINE_I440FX_MACHINE(v5_1, "pc-i440fx-5.1", NULL,hw/i386/pc_q35.c +1
-0@@ -359,6 +359,7 @@ static void pc_q35_5_1_machine_options(MachineClass *m)pc_q35_machine_options (m); m->alias ="q35" ; pcmc->default_cpu_version =1 ; +compat_props_add (m->compat_props, pc_compat_5_1, pc_compat_5_1_len); } DEFINE_Q35_MACHINE(v5_1, "pc-q35-5.1", NULL,hw/isa/lpc_ich9.c +9
-0@@ -373,6 +373,15 @@ static void smi_features_ok_callback(void *opaque)/* guest requests invalid features, leave @features_ok at zero */ return ; } +if (!(guest_features &BIT_ULL (ICH9_LPC_SMI_F_BROADCAST_BIT )) && + guest_features & (BIT_ULL (ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT ) | +BIT_ULL (ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT ))) { +/* +* cpu hot-[un]plug with SMI requires SMI broadcast, +* leave @features_ok at zero +*/ +return ; + }/* valid feature subset requested, lock it down, report success */ lpc->smi_negotiated_features = guest_features;hw/isa/lpc_ich9.c static Property ich9_lpc_properties[] = { · line 765
Quoted 10 lines
hw/isa/lpc_ich9.c +4
-0@@ -747,6 +756,10 @@ static Property ich9_lpc_properties[] = {DEFINE_PROP_BOOL ("noreboot" , ICH9LPCState, pin_strap.spkr_hi, true),DEFINE_PROP_BIT64 ("x-smi-broadcast" , ICH9LPCState, smi_host_features,ICH9_LPC_SMI_F_BROADCAST_BIT , true), +DEFINE_PROP_BIT64 ("x-smi-cpu-hotplug" , ICH9LPCState, smi_host_features, +ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT , true), +DEFINE_PROP_BIT64 ("x-smi-cpu-hotunplug" , ICH9LPCState, smi_host_features, +ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT , false), DEFINE_PROP_END_OF_LIST(), };this patch does the right thing for the 5.1 PC machine types, but it does not introduce any 5.2 machine types, so I can't enable the hotplug feature bit without messing with the x-smi-cpu-hotplug property manually.
Now... looking at the mailing list, I can see the following patch pending review (posted by Daniel ~5 days ago):
Quoted 7 lines
[PATCH 01/10] hw: add compat machines for 5.2
http://mid.mail-archive.com/[email protected]That patch introduces the 5.2 PC machine types.
However, I can't just apply your series on top of that one patch, because they conflict at least on the "
pc_compat_5_1" array.
I consider any patch that adds compat options without adding all compat machines first to be buggy. We had that in the past, and it had been painful to sort it out again later. That's why I usually post a compat machines patch during hardfreeze, to be picked up by anyone who needs it.
(See
https://lore.kernel.org/qemu-devel/[email protected]/
-- this is the patch that Daniel re-posted.)
Quoted 10 lines
Given that Daniel's patch was posted before yours, and also that Daniel's patch introduces 5.2 machine types for arm, ppc and s390x too (and the "
hw_compat_5_1" array in addition to the "pc_compat_5_1" array), I'd like to request:- that we please review and/or merge Daniel's patch in isolation (just the first patch in the containing series, not the entire series!),
- and that you please rebase your series on top of Daniel's patch.
Ack. Any series introducing compat options should have the machines patch as the first patch; depending on merge order, it can then be dropped again. (Usually, one of the architecture pull requests merges it; we just don't have anything merged yet.)
Quoted 4 lines
If Daniel's patch is approved as-is on the list, then I'm OK applying it locally in isolation from the rest of the containing series, as a basis for locally applying your v3.
Just pick my original patch, it has a bunch of acks already.
Quoted 8 lines
(I could resolve the conflicts myself at once I guess, and proceed with the review / testing -- but that's not really useful if I want to give a formal Tested-by. I wouldn't be testing the patches as they were posted.)
Thanks!
Laszlo
Re: [PATCH v2 1/7] x86: lpc9: let firmware negotiate 'CPU hotplug with SMI' features
Quoted 9 lines · Cornelia Huck
I consider any patch that adds compat options without adding all compat machines first to be buggy. We had that in the past, and it had been painful to sort it out again later. That's why I usually post a compat machines patch during hardfreeze, to be picked up by anyone who needs it.
(See
https://lore.kernel.org/qemu-devel/[email protected]/
-- this is the patch that Daniel re-posted.)
Indeed, thank you -- in the end, I did notice that Daniel's patch started with "From: Cornelia" :) and then I checked my qemu-devel folders for more emails with the same subject.
Quoted 1 line
Just pick my original patch, it has a bunch of acks already.
True, but Igor's series wouldn't apply without manual conflict resolution, and I can't do that if I want to respond with a Tested-by.
(Of course, picking up your patch and including it in v3 is feasible for Igor.)
Thanks!
Laszlo
Re: [PATCH v2 1/7] x86: lpc9: let firmware negotiate 'CPU hotplug with SMI' features
Quoted 16 lines · On Wed, 19 Aug 2020 11:14:45 +0200 Laszlo Ersek <[email protected]> wrote:
Quoted 9 lines · Cornelia Huck
I consider any patch that adds compat options without adding all compat machines first to be buggy. We had that in the past, and it had been painful to sort it out again later. That's why I usually post a compat machines patch during hardfreeze, to be picked up by anyone who needs it.
(See
https://lore.kernel.org/qemu-devel/[email protected]/
-- this is the patch that Daniel re-posted.)Indeed, thank you -- in the end, I did notice that Daniel's patch started with "From: Cornelia" :) and then I checked my qemu-devel folders for more emails with the same subject.
Quoted 7 lines
Quoted 1 line
Just pick my original patch, it has a bunch of acks already.
True, but Igor's series wouldn't apply without manual conflict resolution, and I can't do that if I want to respond with a Tested-by.
(Of course, picking up your patch and including it in v3 is feasible for Igor.)
I'll rebase this path on top 5.2 machine patch and post it here.
Quoted 3 lines
Thanks!
Laszlo
PATCH v3 1/7 x86: lpc9: let firmware negotiate 'CPU hotplug with SMI' features
In reply to Igor MammedovIt will allow firmware to notify QEMU that firmware requires SMI being triggered on CPU hot[un]plug, so that it would be able to account for hotplugged CPU and relocate it to new SMM base and/or safely remove CPU on unplug.
Using negotiated features, follow up patches will insert SMI upcall into AML code, to make sure that firmware processes hotplug before guest OS would attempt to use new CPU.
---
v3:
- rebase on top of "[PATCH v2] hw: add compat machines for 5.2"
so apply that before this patch
v2:
- rebase on top of 5.1 (move compat values to 5.1 machine)
- make "x-smi-cpu-hotunplug" false by default (Laszlo Ersek <[email protected]>)
--- include/hw/i386/ich9.h | 2 ++ hw/i386/pc.c | 4 +++- hw/i386/pc_piix.c | 1 + hw/i386/pc_q35.c | 1 + hw/isa/lpc_ich9.c | 13 +++++++++++++ 5 files changed, 20 insertions(+), 1 deletion(-)
include/hw/i386/ich9.h +2 -0
@@ -247,5 +247,7 @@ typedef struct ICH9LPCState {/* bit positions used in fw_cfg SMI feature negotiation */ #define ICH9_LPC_SMI_F_BROADCAST_BIT 0 +#define ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT 1 +#define ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT 2#endif /* HW_ICH9_H */
hw/i386/pc.c +3 -1
@@ -97,7 +97,9 @@#include "fw_cfg.h" #include "trace.h" -GlobalProperty pc_compat_5_1[] = {}; +GlobalProperty pc_compat_5_1[] = { + {"ICH9-LPC" ,"x-smi-cpu-hotplug" ,"off" }, +};const size_t pc_compat_5_1_len =G_N_ELEMENTS (pc_compat_5_1);GlobalProperty pc_compat_5_0[] = {
hw/i386/pc_piix.c +1 -0
@@ -433,6 +433,7 @@ static void pc_i440fx_5_2_machine_options(MachineClass *m) m->alias ="pc" ; m->is_default = true; pcmc->default_cpu_version =1 ; +compat_props_add (m->compat_props, pc_compat_5_1, pc_compat_5_1_len); } DEFINE_I440FX_MACHINE(v5_2, "pc-i440fx-5.2", NULL,
hw/i386/pc_q35.c +1 -0
@@ -359,6 +359,7 @@ static void pc_q35_5_2_machine_options(MachineClass *m)pc_q35_machine_options (m); m->alias ="q35" ; pcmc->default_cpu_version =1 ; +compat_props_add (m->compat_props, pc_compat_5_1, pc_compat_5_1_len); } DEFINE_Q35_MACHINE(v5_2, "pc-q35-5.2", NULL,
hw/isa/lpc_ich9.c +13 -0
@@ -373,6 +373,15 @@ static void smi_features_ok_callback(void *opaque)/* guest requests invalid features, leave @features_ok at zero */ return ; } +if (!(guest_features &BIT_ULL (ICH9_LPC_SMI_F_BROADCAST_BIT )) && + guest_features & (BIT_ULL (ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT ) | +BIT_ULL (ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT ))) { +/* +* cpu hot-[un]plug with SMI requires SMI broadcast, +* leave @features_ok at zero +*/ +return ; + }/* valid feature subset requested, lock it down, report success */ lpc->smi_negotiated_features = guest_features;
@@ -747,6 +756,10 @@ static Property ich9_lpc_properties[] = {DEFINE_PROP_BOOL ("noreboot" , ICH9LPCState, pin_strap.spkr_hi, true),DEFINE_PROP_BIT64 ("x-smi-broadcast" , ICH9LPCState, smi_host_features,ICH9_LPC_SMI_F_BROADCAST_BIT , true), +DEFINE_PROP_BIT64 ("x-smi-cpu-hotplug" , ICH9LPCState, smi_host_features, +ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT , true), +DEFINE_PROP_BIT64 ("x-smi-cpu-hotunplug" , ICH9LPCState, smi_host_features, +ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT , false), DEFINE_PROP_END_OF_LIST(), };
Signature · 1 line
2.26.2
Re: [PATCH v3 1/7] x86: lpc9: let firmware negotiate 'CPU hotplug with SMI' features
Hi Igor,
Quoted 69 lines · Igor Mammedov
It will allow firmware to notify QEMU that firmware requires SMI being triggered on CPU hot[un]plug, so that it would be able to account for hotplugged CPU and relocate it to new SMM base and/or safely remove CPU on unplug.
Using negotiated features, follow up patches will insert SMI upcall into AML code, to make sure that firmware processes hotplug before guest OS would attempt to use new CPU.
Signed-off-by Igor Mammedov <[email protected]>---
v3:
- rebase on top of "[PATCH v2] hw: add compat machines for 5.2"
so apply that before this patch
v2:
- rebase on top of 5.1 (move compat values to 5.1 machine)
- make "x-smi-cpu-hotunplug" false by default (Laszlo Ersek <[email protected]>)--- include/hw/i386/ich9.h | 2 ++ hw/i386/pc.c | 4 +++- hw/i386/pc_piix.c | 1 + hw/i386/pc_q35.c | 1 + hw/isa/lpc_ich9.c | 13 +++++++++++++ 5 files changed, 20 insertions(+), 1 deletion(-)include/hw/i386/ich9.h +2
-0@@ -247,5 +247,7 @@ typedef struct ICH9LPCState {/* bit positions used in fw_cfg SMI feature negotiation */ #define ICH9_LPC_SMI_F_BROADCAST_BIT 0 +#define ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT 1 +#define ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT 2#endif /* HW_ICH9_H */ hw/i386/pc.c +3
-1@@ -97,7 +97,9 @@#include "fw_cfg.h" #include "trace.h" -GlobalProperty pc_compat_5_1[] = {}; +GlobalProperty pc_compat_5_1[] = { + {"ICH9-LPC" ,"x-smi-cpu-hotplug" ,"off" }, +};const size_t pc_compat_5_1_len =G_N_ELEMENTS (pc_compat_5_1);GlobalProperty pc_compat_5_0[] = {hw/i386/pc_piix.c +1
-0@@ -433,6 +433,7 @@ static void pc_i440fx_5_2_machine_options(MachineClass *m) m->alias ="pc" ; m->is_default = true; pcmc->default_cpu_version =1 ; +compat_props_add (m->compat_props, pc_compat_5_1, pc_compat_5_1_len); } DEFINE_I440FX_MACHINE(v5_2, "pc-i440fx-5.2", NULL,hw/i386/pc_q35.c +0
-0
hw/i386/pc_q35.c static void pc_q35_5_2_machine_options(MachineClass *m) · line 365
Quoted 7 lines
hw/i386/pc_q35.c +1
-0@@ -359,6 +359,7 @@ static void pc_q35_5_2_machine_options(MachineClass *m)pc_q35_machine_options (m); m->alias ="q35" ; pcmc->default_cpu_version =1 ; +compat_props_add (m->compat_props, pc_compat_5_1, pc_compat_5_1_len); } DEFINE_Q35_MACHINE(v5_2, "pc-q35-5.2", NULL,
Sorry about the late response, I was away yesterday (public holiday in my country).
The above two hunks should be dropped.
Cornelia's patch already handles both of:
- hw_compat_5_1,
- pc_compat_5_1.
in both of:
- pc_i440fx_5_1_machine_options(),
- pc_q35_5_1_machine_options().
So you don't need to modify those functions any longer.
Furthermore, the machine-options functions for 5.2 machine types should not be modified *at all*. The effect of the above two hunks is that the 5.2 machine types will inherit the 5.1 compat props (such as
ICH9-LPC.x-smi-cpu-hotplug=off
) and we do not want that.
So please drop the above two hunks.
If you could post a v4 of this patch today, that would be awesome; I would like to play with this series extensively still today. "tonight" is definitely an option, so if you can post the patch in the evening (CEST), that's still great from my POV!
Thanks!
Laszlo
Quoted 32 lines
hw/isa/lpc_ich9.c +13
-0@@ -373,6 +373,15 @@ static void smi_features_ok_callback(void *opaque)/* guest requests invalid features, leave @features_ok at zero */ return ; } +if (!(guest_features &BIT_ULL (ICH9_LPC_SMI_F_BROADCAST_BIT )) && + guest_features & (BIT_ULL (ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT ) | +BIT_ULL (ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT ))) { +/* +* cpu hot-[un]plug with SMI requires SMI broadcast, +* leave @features_ok at zero +*/ +return ; + }/* valid feature subset requested, lock it down, report success */ lpc->smi_negotiated_features = guest_features;@@ -747,6 +756,10 @@ static Property ich9_lpc_properties[] = {DEFINE_PROP_BOOL ("noreboot" , ICH9LPCState, pin_strap.spkr_hi, true),DEFINE_PROP_BIT64 ("x-smi-broadcast" , ICH9LPCState, smi_host_features,ICH9_LPC_SMI_F_BROADCAST_BIT , true), +DEFINE_PROP_BIT64 ("x-smi-cpu-hotplug" , ICH9LPCState, smi_host_features, +ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT , true), +DEFINE_PROP_BIT64 ("x-smi-cpu-hotunplug" , ICH9LPCState, smi_host_features, +ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT , false), DEFINE_PROP_END_OF_LIST(), };
PATCH v4 1/6 x86: lpc9: let firmware negotiate 'CPU hotplug with SMI' features
It will allow firmware to notify QEMU that firmware requires SMI being triggered on CPU hot[un]plug, so that it would be able to account for hotplugged CPU and relocate it to new SMM base and/or safely remove CPU on unplug.
Using negotiated features, follow up patches will insert SMI upcall into AML code, to make sure that firmware processes hotplug before guest OS would attempt to use new CPU.
---
v4:
- fix 5.2 machine types so they won't apply pc_compat_5_1
(Laszlo Ersek <[email protected]>)
v3:
- rebase on top of "[PATCH v2] hw: add compat machines for 5.2"
so apply that before this patch
v2:
- rebase on top of 5.1 (move compat values to 5.1 machine)
- make "x-smi-cpu-hotunplug" false by default (Laszlo Ersek <[email protected]>)
fixup
--- include/hw/i386/ich9.h | 2 ++ hw/i386/pc.c | 4 +++- hw/isa/lpc_ich9.c | 13 +++++++++++++ 3 files changed, 18 insertions(+), 1 deletion(-)
include/hw/i386/ich9.h +2 -0
@@ -247,5 +247,7 @@ typedef struct ICH9LPCState {/* bit positions used in fw_cfg SMI feature negotiation */ #define ICH9_LPC_SMI_F_BROADCAST_BIT 0 +#define ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT 1 +#define ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT 2#endif /* HW_ICH9_H */
hw/i386/pc.c +3 -1
@@ -97,7 +97,9 @@#include "fw_cfg.h" #include "trace.h" -GlobalProperty pc_compat_5_1[] = {}; +GlobalProperty pc_compat_5_1[] = { + {"ICH9-LPC" ,"x-smi-cpu-hotplug" ,"off" }, +};const size_t pc_compat_5_1_len =G_N_ELEMENTS (pc_compat_5_1);GlobalProperty pc_compat_5_0[] = {
hw/isa/lpc_ich9.c +13 -0
@@ -373,6 +373,15 @@ static void smi_features_ok_callback(void *opaque)/* guest requests invalid features, leave @features_ok at zero */ return ; } +if (!(guest_features &BIT_ULL (ICH9_LPC_SMI_F_BROADCAST_BIT )) && + guest_features & (BIT_ULL (ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT ) | +BIT_ULL (ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT ))) { +/* +* cpu hot-[un]plug with SMI requires SMI broadcast, +* leave @features_ok at zero +*/ +return ; + }/* valid feature subset requested, lock it down, report success */ lpc->smi_negotiated_features = guest_features;
@@ -747,6 +756,10 @@ static Property ich9_lpc_properties[] = {DEFINE_PROP_BOOL ("noreboot" , ICH9LPCState, pin_strap.spkr_hi, true),DEFINE_PROP_BIT64 ("x-smi-broadcast" , ICH9LPCState, smi_host_features,ICH9_LPC_SMI_F_BROADCAST_BIT , true), +DEFINE_PROP_BIT64 ("x-smi-cpu-hotplug" , ICH9LPCState, smi_host_features, +ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT , true), +DEFINE_PROP_BIT64 ("x-smi-cpu-hotunplug" , ICH9LPCState, smi_host_features, +ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT , false), DEFINE_PROP_END_OF_LIST(), };
Signature · 1 line
2.26.2
Re: [PATCH v4 1/6] x86: lpc9: let firmware negotiate 'CPU hotplug with SMI' features
Quoted 78 lines · Igor Mammedov
It will allow firmware to notify QEMU that firmware requires SMI being triggered on CPU hot[un]plug, so that it would be able to account for hotplugged CPU and relocate it to new SMM base and/or safely remove CPU on unplug.
Using negotiated features, follow up patches will insert SMI upcall into AML code, to make sure that firmware processes hotplug before guest OS would attempt to use new CPU.
Signed-off-by Igor Mammedov <[email protected]>Reviewed-by Laszlo Ersek <[email protected]>---
v4:
- fix 5.2 machine types so they won't applypc_compat_5_1
(Laszlo Ersek <[email protected]>)
v3:
- rebase on top of "[PATCH v2] hw: add compat machines for 5.2"
so apply that before this patch
v2:
- rebase on top of 5.1 (move compat values to 5.1 machine)
- make "x-smi-cpu-hotunplug" false by default (Laszlo Ersek <[email protected]>)fixup
--- include/hw/i386/ich9.h | 2 ++ hw/i386/pc.c | 4 +++- hw/isa/lpc_ich9.c | 13 +++++++++++++ 3 files changed, 18 insertions(+), 1 deletion(-)include/hw/i386/ich9.h +2
-0@@ -247,5 +247,7 @@ typedef struct ICH9LPCState {/* bit positions used in fw_cfg SMI feature negotiation */ #define ICH9_LPC_SMI_F_BROADCAST_BIT 0 +#define ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT 1 +#define ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT 2#endif /* HW_ICH9_H */ hw/i386/pc.c +3
-1@@ -97,7 +97,9 @@#include "fw_cfg.h" #include "trace.h" -GlobalProperty pc_compat_5_1[] = {}; +GlobalProperty pc_compat_5_1[] = { + {"ICH9-LPC" ,"x-smi-cpu-hotplug" ,"off" }, +};const size_t pc_compat_5_1_len =G_N_ELEMENTS (pc_compat_5_1);GlobalProperty pc_compat_5_0[] = {hw/isa/lpc_ich9.c +9
-0@@ -373,6 +373,15 @@ static void smi_features_ok_callback(void *opaque)/* guest requests invalid features, leave @features_ok at zero */ return ; } +if (!(guest_features &BIT_ULL (ICH9_LPC_SMI_F_BROADCAST_BIT )) && + guest_features & (BIT_ULL (ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT ) | +BIT_ULL (ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT ))) { +/* +* cpu hot-[un]plug with SMI requires SMI broadcast, +* leave @features_ok at zero +*/ +return ; + }/* valid feature subset requested, lock it down, report success */ lpc->smi_negotiated_features = guest_features;
hw/isa/lpc_ich9.c static Property ich9_lpc_properties[] = { · line 765
Quoted 10 lines
hw/isa/lpc_ich9.c +4
-0@@ -747,6 +756,10 @@ static Property ich9_lpc_properties[] = {DEFINE_PROP_BOOL ("noreboot" , ICH9LPCState, pin_strap.spkr_hi, true),DEFINE_PROP_BIT64 ("x-smi-broadcast" , ICH9LPCState, smi_host_features,ICH9_LPC_SMI_F_BROADCAST_BIT , true), +DEFINE_PROP_BIT64 ("x-smi-cpu-hotplug" , ICH9LPCState, smi_host_features, +ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT , true), +DEFINE_PROP_BIT64 ("x-smi-cpu-hotunplug" , ICH9LPCState, smi_host_features, +ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT , false), DEFINE_PROP_END_OF_LIST(), };
This patch doesn't apply with git-am, as of commit 44423107e7b5 ("Merge remote-tracking branch 'remotes/xtensa/tags/20200821-xtensa' into staging", 2020-08-24).
The reason is that commit 2becc36a3e53 ("meson: infrastructure for building emulators", 2020-08-21) introduced
#include CONFIG_DEVICES
to "hw/i386/pc.c", just above the (then) "pc_compat_5_0" array.
Then Cornelia's commit 3ff3c5d31740 ("hw: add compat machines for 5.2", 2020-08-19), which introduced "pc_compat_5_1" independently of the Meson conversion, needed explicit resolution against CONFIG_DEVICES for merging into master. That was covered in merge commit ca489cd037e4 ("Merge remote-tracking branch 'remotes/ehabkost/tags/machine-next-pull-request' into staging", 2020-08-22).
So the patch applies on top of 3ff3c5d31740, but not on the merge (ca489cd037e4) that brought 3ff3c5d31740 into master.
Not a problem though: I can apply the patch on 3ff3c5d31740, and then cleanly (automatically) rebase to current HEAD (44423107e7b5) from there. This is the range-diff across the rebase:
Quoted 11 lines
1:
9066fa4ccb49! 1:05188fffe6aax86: lpc9: let firmware negotiate 'CPU hotplug with SMI' features@@ -31,8 +31,8 @@ --- a/hw/i386/pc.c +++ b/hw/i386/pc.c @@ - #include "fw_cfg.h" #include "trace.h" + #include CONFIG_DEVICES -GlobalProperty pc_compat_5_1[] = {}; +GlobalProperty pc_compat_5_1[] = {
So it's indeed just a context update.
Having applied this series to QEMU, my test results are:
OVMF has 5ba203b54e59 machine type plug gate unplug gate gating result --------------------- ------------ --------- ----------- ------------- no pc-q35-5.1 reject reject pass no pc-q35-5.2 reject reject pass yes pc-q35-5.1 reject reject pass yes pc-q35-5.2 accept reject pass
The results are the same after S3 suspend/resume. (This is relevant because the features are re-negotiated during S3 resume.)
Thus, for this one patch, so far:
- (just to confirm:)
- also:
Thanks!
Laszlo
PATCH v2 2/7 x86: cphp: prevent guest crash on CPU hotplug when broadcast SMI is in use
In reply to Igor MammedovThere were reports of guest crash on CPU hotplug, when using q35 machine type and OVMF with SMM, due to hotplugged CPU trying to process SMI at default SMI handler location without it being relocated by firmware first.
Fix it by refusing hotplug if firmware hasn't negotiated CPU hotplug with SMI support while SMI broadcast is in use.
---
v1:
fix typos an use suggested wording in commit and error msg s/secure boot/smm/; s/hotplug SMI/hotplug with SMI/
(Laszlo Ersek <[email protected]>)
--- hw/acpi/ich9.c | 12 +++++++++++- hw/i386/pc.c | 11 +++++++++++ 2 files changed, 22 insertions(+), 1 deletion(-)
hw/acpi/ich9.c +11 -1
@@ -408,10 +408,20 @@ void ich9_pm_device_pre_plug_cb(HotplugHandler *hotplug_dev, DeviceState *dev,ICH9LPCState *lpc =ICH9_LPC_DEVICE (hotplug_dev);if (object_dynamic_cast (OBJECT (dev),TYPE_PC_DIMM ) && - !lpc->pm.acpi_memory_hotplug.is_enabled) + !lpc->pm.acpi_memory_hotplug.is_enabled) {error_setg (errp,"memory hotplug is not enabled: %s.memory-hotplug-support " "is not set" ,object_get_typename (OBJECT (lpc))); + }else if (object_dynamic_cast (OBJECT (dev),TYPE_CPU )) { +uint64_t negotiated = lpc->smi_negotiated_features; + +if (negotiated &BIT_ULL (ICH9_LPC_SMI_F_BROADCAST_BIT ) && + !(negotiated &BIT_ULL (ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT ))) { +error_setg (errp,"cpu hotplug with SMI wasn't enabled by firmware" ); +error_append_hint (errp,"update machine type to newer than 5.1 " +"and firmware that suppors CPU hotplug with SMM" ); + } + } } void ich9_pm_device_plug_cb(HotplugHandler *hotplug_dev, DeviceState *dev,
hw/i386/pc.c +11 -0
@@ -1499,6 +1499,17 @@ static void pc_cpu_pre_plug(HotplugHandler *hotplug_dev,return ; } +if (pcms->acpi_dev) { +Error *local_err =NULL ; + +hotplug_handler_pre_plug (HOTPLUG_HANDLER (pcms->acpi_dev), dev, + &local_err); +if (local_err) { +error_propagate (errp, local_err); +return ; + } + } +init_topo_info (&topo_info, x86ms); env->nr_dies = x86ms->smp_dies;
Signature · 1 line
2.26.2
PATCH v2 3/7 x86: cpuhp: refuse cpu hot-unplug request earlier if not supported
In reply to Igor MammedovCPU hot-unplug with SMM requires firmware participation to prevent guest crash (i.e. CPU can be removed only after OS _and_ firmware were prepared for the action).
Previous patches introduced ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT feature bit, which is advertised by firmware when it has support for CPU hot-unplug. Use it to check if guest is able to handle unplug and make device_del fail gracefully if hot-unplug feature hasn't been negotiated.
---
v2:
- fix typo in commit message
- drop 5.1 version from hint message (Laszlo)
--- hw/acpi/ich9.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)
hw/acpi/ich9.c +12 -0
@@ -460,6 +460,18 @@ void ich9_pm_device_unplug_request_cb(HotplugHandler *hotplug_dev, errp); }else if (object_dynamic_cast (OBJECT (dev),TYPE_CPU ) && !lpc->pm.cpu_hotplug_legacy) { +uint64_t negotiated = lpc->smi_negotiated_features; + +if (negotiated &BIT_ULL (ICH9_LPC_SMI_F_BROADCAST_BIT ) && + !(negotiated &BIT_ULL (ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT ))) { +error_setg (errp,"cpu hot-unplug with SMI wasn't enabled " +"by firmware" ); +error_append_hint (errp,"update machine type to a version having " +"x-smi-cpu-hotunplug=on and firmware that " +"supports CPU hot-unplug with SMM" ); +return ; + } +acpi_cpu_unplug_request_cb (hotplug_dev, &lpc->pm.cpuhp_state, dev, errp); }else {
Signature · 1 line
2.26.2
Re: [PATCH v2 3/7] x86: cpuhp: refuse cpu hot-unplug request earlier if not supported
Quoted 34 lines · Igor Mammedov
CPU hot-unplug with SMM requires firmware participation to prevent guest crash (i.e. CPU can be removed only after OS _and_ firmware were prepared for the action).
Previous patches introducedICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BITfeature bit, which is advertised by firmware when it has support for CPU hot-unplug. Use it to check if guest is able to handle unplug and makedevice_delfail gracefully if hot-unplug feature hasn't been negotiated.Signed-off-by Igor Mammedov <[email protected]>Tested-by Laszlo Ersek <[email protected]>Reviewed-by Laszlo Ersek <[email protected]>---
v2:
- fix typo in commit message
- drop 5.1 version from hint message (Laszlo)--- hw/acpi/ich9.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)hw/acpi/ich9.c +5
-0@@ -460,6 +460,18 @@ void ich9_pm_device_unplug_request_cb(HotplugHandler *hotplug_dev, errp); }else if (object_dynamic_cast (OBJECT (dev),TYPE_CPU ) && !lpc->pm.cpu_hotplug_legacy) { +uint64_t negotiated = lpc->smi_negotiated_features; + +if (negotiated &BIT_ULL (ICH9_LPC_SMI_F_BROADCAST_BIT ) && + !(negotiated &BIT_ULL (ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT ))) { + error_setg(errp, "cpu hot-unplug with SMI wasn't enabled "
hw/acpi/ich9.c void ich9_pm_device_unplug_request_cb(HotplugHandler *hotplug_dev, · line 477
Quoted 10 lines
hw/acpi/ich9.c +7
-0+ "by firmware"); +error_append_hint (errp,"update machine type to a version having " +"x-smi-cpu-hotunplug=on and firmware that " +"supports CPU hot-unplug with SMM" ); +return ; + } +acpi_cpu_unplug_request_cb (hotplug_dev, &lpc->pm.cpuhp_state, dev, errp); }else {
A trivial comment:
Patch#2 says "x86: cphp: " in the subject line, but patch#3 says "x86:
cpuhp: " (note the extra "u").
I'm fine with either "cphp" or "cpuhp", but the subjects should be consistent -- both patches should use the same word.
Preserve my T-b and R-b on both patches #2 and #3, after fixing up one of the subjects. (Up to you which one.)
Thanks!
Laszlo
PATCH v2 4/7 acpi: add aml_land() and aml_break() primitives
In reply to Igor Mammedov--- include/hw/acpi/aml-build.h | 2 ++ hw/acpi/aml-build.c | 16 ++++++++++++++++ 2 files changed, 18 insertions(+)
include/hw/acpi/aml-build.h +2 -0
@@ -291,6 +291,7 @@ Aml *aml_store(Aml *val, Aml *target);Aml *aml_and (Aml *arg1,Aml *arg2,Aml *dst);Aml *aml_or (Aml *arg1,Aml *arg2,Aml *dst);Aml *aml_lor (Aml *arg1,Aml *arg2); +Aml *aml_land (Aml *arg1,Aml *arg2);Aml *aml_shiftleft (Aml *arg1,Aml *count);Aml *aml_shiftright (Aml *arg1,Aml *count,Aml *dst);Aml *aml_lless (Aml *arg1,Aml *arg2);
@@ -300,6 +301,7 @@ Aml *aml_increment(Aml *arg);Aml *aml_decrement (Aml *arg);Aml *aml_index (Aml *arg1,Aml *idx);Aml *aml_notify (Aml *arg1,Aml *arg2); +Aml *aml_break (void );Aml *aml_call0 (const char *method);Aml *aml_call1 (const char *method,Aml *arg1);Aml *aml_call2 (const char *method,Aml *arg1,Aml *arg2);
hw/acpi/aml-build.c +16 -0
@@ -556,6 +556,15 @@ Aml *aml_or(Aml *arg1, Aml *arg2, Aml *dst)return build_opcode_2arg_dst (0x7D /* OrOp */ , arg1, arg2, dst); } +/* ACPI 1.0b: 16.2.5.4 Type 2 Opcodes Encoding: DefLAnd */ +Aml *aml_land (Aml *arg1,Aml *arg2) +{ +Aml *var =aml_opcode (0x90 /* LandOp */ ); +aml_append (var, arg1); +aml_append (var, arg2); +return var; +} +/* ACPI 1.0b: 16.2.5.4 Type 2 Opcodes Encoding: DefLOr */ Aml *aml_lor (Aml *arg1,Aml *arg2) {
@@ -629,6 +638,13 @@ Aml *aml_notify(Aml *arg1, Aml *arg2)return var; } +/* ACPI 1.0b: 16.2.5.3 Type 1 Opcodes Encoding: DefBreak */ +Aml *aml_break (void ) +{ +Aml *var =aml_opcode (0xa5 /* BreakOp */ ); +return var; +} +/* helper to call method without argument */ Aml *aml_call0 (const char *method) {
Signature · 1 line
2.26.2
Re: [PATCH v2 4/7] acpi: add aml_land() and aml_break() primitives
Quoted 1 line · Igor Mammedov
Signed-off-by Igor Mammedov <[email protected]>
Quoted 60 lines
--- include/hw/acpi/aml-build.h | 2 ++ hw/acpi/aml-build.c | 16 ++++++++++++++++ 2 files changed, 18 insertions(+)include/hw/acpi/aml-build.h +2
-0@@ -291,6 +291,7 @@ Aml *aml_store(Aml *val, Aml *target);Aml *aml_and (Aml *arg1,Aml *arg2,Aml *dst);Aml *aml_or (Aml *arg1,Aml *arg2,Aml *dst);Aml *aml_lor (Aml *arg1,Aml *arg2); +Aml *aml_land (Aml *arg1,Aml *arg2);Aml *aml_shiftleft (Aml *arg1,Aml *count);Aml *aml_shiftright (Aml *arg1,Aml *count,Aml *dst);Aml *aml_lless (Aml *arg1,Aml *arg2);@@ -300,6 +301,7 @@ Aml *aml_increment(Aml *arg);Aml *aml_decrement (Aml *arg);Aml *aml_index (Aml *arg1,Aml *idx);Aml *aml_notify (Aml *arg1,Aml *arg2); +Aml *aml_break (void );Aml *aml_call0 (const char *method);Aml *aml_call1 (const char *method,Aml *arg1);Aml *aml_call2 (const char *method,Aml *arg1,Aml *arg2);hw/acpi/aml-build.c +16
-0@@ -556,6 +556,15 @@ Aml *aml_or(Aml *arg1, Aml *arg2, Aml *dst)return build_opcode_2arg_dst (0x7D /* OrOp */ , arg1, arg2, dst); } +/* ACPI 1.0b: 16.2.5.4 Type 2 Opcodes Encoding: DefLAnd */ +Aml *aml_land (Aml *arg1,Aml *arg2) +{ +Aml *var =aml_opcode (0x90 /* LandOp */ ); +aml_append (var, arg1); +aml_append (var, arg2); +return var; +} +/* ACPI 1.0b: 16.2.5.4 Type 2 Opcodes Encoding: DefLOr */ Aml *aml_lor (Aml *arg1,Aml *arg2) {@@ -629,6 +638,13 @@ Aml *aml_notify(Aml *arg1, Aml *arg2)return var; } +/* ACPI 1.0b: 16.2.5.3 Type 1 Opcodes Encoding: DefBreak */ +Aml *aml_break (void ) +{ +Aml *var =aml_opcode (0xa5 /* BreakOp */ ); +return var; +} +/* helper to call method without argument */ Aml *aml_call0 (const char *method) {
Re: [PATCH v2 4/7] acpi: add aml_land() and aml_break() primitives
In reply to Igor MammedovQuoted 31 lines · Igor Mammedov
Signed-off-by Igor Mammedov <[email protected]>--- include/hw/acpi/aml-build.h | 2 ++ hw/acpi/aml-build.c | 16 ++++++++++++++++ 2 files changed, 18 insertions(+)include/hw/acpi/aml-build.h +2
-0@@ -291,6 +291,7 @@ Aml *aml_store(Aml *val, Aml *target);Aml *aml_and (Aml *arg1,Aml *arg2,Aml *dst);Aml *aml_or (Aml *arg1,Aml *arg2,Aml *dst);Aml *aml_lor (Aml *arg1,Aml *arg2); +Aml *aml_land (Aml *arg1,Aml *arg2);Aml *aml_shiftleft (Aml *arg1,Aml *count);Aml *aml_shiftright (Aml *arg1,Aml *count,Aml *dst);Aml *aml_lless (Aml *arg1,Aml *arg2);@@ -300,6 +301,7 @@ Aml *aml_increment(Aml *arg);Aml *aml_decrement (Aml *arg);Aml *aml_index (Aml *arg1,Aml *idx);Aml *aml_notify (Aml *arg1,Aml *arg2); +Aml *aml_break (void );Aml *aml_call0 (const char *method);Aml *aml_call1 (const char *method,Aml *arg1);Aml *aml_call2 (const char *method,Aml *arg1,Aml *arg2);hw/acpi/aml-build.c +0
-0
hw/acpi/aml-build.c Aml *aml_or(Aml *arg1, Aml *arg2, Aml *dst) · line 562
Quoted 7 lines
hw/acpi/aml-build.c +4
-0@@ -556,6 +556,15 @@ Aml *aml_or(Aml *arg1, Aml *arg2, Aml *dst)return build_opcode_2arg_dst (0x7D /* OrOp */ , arg1, arg2, dst); } +/* ACPI 1.0b: 16.2.5.4 Type 2 Opcodes Encoding: DefLAnd */ +Aml *aml_land (Aml *arg1,Aml *arg2) +{ +Aml *var =aml_opcode (0x90 /* LandOp */ );
(1) Small typo in the comment: in the spec, it is spelled "LAndOp", not "LandOp" (consistently with "LOrOp" just below -- although "LOrOp" is not visible in the context, in this email).
hw/acpi/aml-build.c Aml *aml_or(Aml *arg1, Aml *arg2, Aml *dst) · line 570
Quoted 8 lines
hw/acpi/aml-build.c +5
-0+aml_append (var, arg1); +aml_append (var, arg2); +return var; +} +/* ACPI 1.0b: 16.2.5.4 Type 2 Opcodes Encoding: DefLOr */ Aml *aml_lor (Aml *arg1,Aml *arg2) {
(2) In the header file, the declaration order is aml_lor(), then aml_land(). But in the C file, the definitions are in the opposite
order: aml_land(), aml_lor().
Not sure which one is right, but we should be consistent, if we can.
Quoted 5 lines
hw/acpi/aml-build.c +0
-0@@ -629,6 +638,13 @@ Aml *aml_notify(Aml *arg1, Aml *arg2)return var; }
hw/acpi/aml-build.c Aml *aml_notify(Aml *arg1, Aml *arg2) · line 650
Quoted 10 lines
hw/acpi/aml-build.c +7
-0+/* ACPI 1.0b: 16.2.5.3 Type 1 Opcodes Encoding: DefBreak */ +Aml *aml_break (void ) +{ +Aml *var =aml_opcode (0xa5 /* BreakOp */ ); +return var; +} +/* helper to call method without argument */ Aml *aml_call0 (const char *method) {
With my trivial comments (1) and (2) fixed:
Thanks,
Laszlo
PATCH v2 5/7 tests: acpi: mark to be changed tables in bios-tables-test-allowed-diff
In reply to Igor Mammedov... to let tests pass until binary blobs are updated with new AML
--- tests/qtest/bios-tables-test-allowed-diff.h | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+)
tests/qtest/bios-tables-test-allowed-diff.h +19 -0
@@ -1 +1,20 @@/* List of comma-separated changed AML files to ignore */ +"tests/data/acpi/pc/DSDT" , +"tests/data/acpi/q35/DSDT" , +"tests/data/acpi/q35/DSDT.tis" , +"tests/data/acpi/q35/DSDT.bridge" , +"tests/data/acpi/q35/DSDT.mmio64" , +"tests/data/acpi/q35/DSDT.ipmibt" , +"tests/data/acpi/q35/DSDT.cphp" , +"tests/data/acpi/q35/DSDT.memhp" , +"tests/data/acpi/q35/DSDT.numamem" , +"tests/data/acpi/q35/DSDT.dimmpxm" , +"tests/data/acpi/q35/DSDT.acpihmat" , +"tests/data/acpi/pc/DSDT.bridge" , +"tests/data/acpi/pc/DSDT.ipmikcs" , +"tests/data/acpi/pc/DSDT.cphp" , +"tests/data/acpi/pc/DSDT.memhp" , +"tests/data/acpi/pc/DSDT.numamem" , +"tests/data/acpi/pc/DSDT.dimmpxm" , +"tests/data/acpi/pc/DSDT.acpihmat" , +"tests/data/acpi/pc/DSDT.acpihmat",
Signature · 1 line
2.26.2
PATCH v2 6/7 x68: acpi: trigger SMI before sending hotplug Notify event to OSPM
In reply to Igor MammedovIn case firmware has negotiated CPU hotplug SMI feature, generate AML to describe SMI IO port region and send SMI to firmware on each CPU hotplug SCI in case new CPUs were hotplugged.
Since new CPUs can be hotplugged while CPU_SCAN_METHOD is running we can't send SMI before new CPUs are fetched from QEMU as it could cause sending Notify to a CPU that firmware hasn't seen yet. So fetch new CPUs into local cache first and then send SMI and after that sends Notify events to cached CPUs. This should ensure that Notify is sent only to CPUs which were processed by firmware first.
Any CPUs that were hotplugged after caching will be processed by the next CPU_SCAN_METHOD, when pending SCI is handled.
---
v2:
- clear insert event after firmware has returned
control from SMI. (Laszlo Ersek <[email protected]>)
v1:
- make sure that Notify is sent only to CPUs seen by FW
- (Laszlo Ersek <[email protected]>)
- use macro instead of x-smi-negotiated-features
- style fixes
- reserve whole SMI block (0xB2, 0xB3)
v0:
- s/aml_string/aml_eisaid/
/fixes Windows BSOD, on nonsense value/ (Laszlo Ersek <[email protected]>)
- put SMI device under PCI0 like the rest of hotplug IO port
- do not generate SMI AML if CPU hotplug SMI feature hasn't been negotiated
--- include/hw/acpi/cpu.h | 1 + include/hw/i386/ich9.h | 2 ++ hw/acpi/cpu.c | 80 +++++++++++++++++++++++++++++++++++++++--- hw/i386/acpi-build.c | 35 +++++++++++++++++- hw/isa/lpc_ich9.c | 3 ++ 5 files changed, 115 insertions(+), 6 deletions(-)
include/hw/acpi/cpu.h +1 -0
@@ -50,6 +50,7 @@ void cpu_hotplug_hw_init(MemoryRegion *as, Object *owner,typedef struct CPUHotplugFeatures {bool acpi_1_compatible;bool has_legacy_cphp; +const char *smi_path; }CPUHotplugFeatures ; void build_cpus_aml(Aml *table, MachineState *machine, CPUHotplugFeatures opts,
include/hw/i386/ich9.h +2 -0
@@ -245,6 +245,8 @@ typedef struct ICH9LPCState {#define ICH9_SMB_HST_D1 0x06#define ICH9_SMB_HOST_BLOCK_DB 0x07 +#define ICH9_LPC_SMI_NEGOTIATED_FEAT_PROP "x-smi-negotiated-features" +/* bit positions used in fw_cfg SMI feature negotiation */ #define ICH9_LPC_SMI_F_BROADCAST_BIT 0#define ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT 1
hw/acpi/cpu.c +75 -5
122 lines not on this page · raw message
hw/i386/acpi-build.c +34 -1
@@ -95,6 +95,7 @@ typedef struct AcpiPmInfo {bool s3_disabled;bool s4_disabled;bool pcihp_bridge_en; +bool smi_on_cpuhp;uint8_t s4_val;AcpiFadtData fadt;uint16_t cpu_hp_io_base;
@@ -194,6 +195,7 @@ static void acpi_get_pm_info(MachineState *machine, AcpiPmInfo *pm) pm->cpu_hp_io_base =0 ; pm->pcihp_io_base =0 ; pm->pcihp_io_len =0 ; + pm->smi_on_cpuhp = false;assert (obj);init_common_fadt_data (machine, obj, &pm->fadt);
@@ -207,12 +209,16 @@ static void acpi_get_pm_info(MachineState *machine, AcpiPmInfo *pm)object_property_get_uint (obj,ACPI_PCIHP_IO_LEN_PROP ,NULL ); }if (lpc) { +uint64_t smi_features =object_property_get_uint (lpc, +ICH9_LPC_SMI_NEGOTIATED_FEAT_PROP ,NULL );struct AcpiGenericAddress r = { .space_id =AML_AS_SYSTEM_IO , .bit_width =8 , .address =ICH9_RST_CNT_IOPORT }; pm->fadt.reset_reg = r; pm->fadt.reset_val =0xf ; pm->fadt.flags |=1 <<ACPI_FADT_F_RESET_REG_SUP ; pm->cpu_hp_io_base =ICH9_CPU_HOTPLUG_IO_BASE ; + pm->smi_on_cpuhp = + !!(smi_features &BIT_ULL (ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT )); }/* The above need not be conditional on machine type because the reset port
@@ -1515,6 +1521,32 @@ build_dsdt(GArray *table_data, BIOSLinker *linker,aml_append (dev,aml_name_decl ("_UID" ,aml_int (1 )));aml_append (dev,build_q35_osc_method ());aml_append (sb_scope, dev); + +if (pm->smi_on_cpuhp) { +/* reserve SMI block resources, IO ports 0xB2, 0xB3 */ + dev =aml_device ("PCI0.SMI0" ); +aml_append (dev,aml_name_decl ("_HID" ,aml_eisaid ("PNP0A06" ))); +aml_append (dev,aml_name_decl ("_UID" ,aml_string ("SMI resources" ))); + crs =aml_resource_template (); +aml_append (crs, +aml_io ( +AML_DECODE16 , +ACPI_PORT_SMI_CMD , +ACPI_PORT_SMI_CMD , +1 , +2 ) + ); +aml_append (dev,aml_name_decl ("_CRS" , crs)); +aml_append (dev,aml_operation_region ("SMIR" ,AML_SYSTEM_IO , +aml_int (ACPI_PORT_SMI_CMD ),2 )); + field =aml_field ("SMIR" ,AML_BYTE_ACC ,AML_NOLOCK , +AML_WRITE_AS_ZEROS ); +aml_append (field,aml_named_field ("SMIC" ,8 )); +aml_append (field,aml_reserved_field (8 )); +aml_append (dev, field); +aml_append (sb_scope, dev); + } +aml_append (dsdt, sb_scope);build_hpet_aml (dsdt);
@@ -1530,7 +1562,8 @@ build_dsdt(GArray *table_data, BIOSLinker *linker,build_legacy_cpu_hotplug_aml (dsdt, machine, pm->cpu_hp_io_base); }else {CPUHotplugFeatures opts = { - .acpi_1_compatible = true, .has_legacy_cphp = true + .acpi_1_compatible = true, .has_legacy_cphp = true, + .smi_path = pm->smi_on_cpuhp ?"\\_SB.PCI0.SMI0.SMIC" :NULL , };build_cpus_aml (dsdt, machine, opts, pm->cpu_hp_io_base,"\\_SB.PCI0" ,"\\_GPE._E02" );
hw/isa/lpc_ich9.c +3 -0
@@ -647,6 +647,9 @@ static void ich9_lpc_initfn(Object *obj) &acpi_enable_cmd, OBJ_PROP_FLAG_READ);object_property_add_uint8_ptr (OBJECT (lpc),ACPI_PM_PROP_ACPI_DISABLE_CMD , &acpi_disable_cmd,OBJ_PROP_FLAG_READ ); +object_property_add_uint64_ptr (obj,ICH9_LPC_SMI_NEGOTIATED_FEAT_PROP , + &lpc->smi_negotiated_features, +OBJ_PROP_FLAG_READ );ich9_pm_add_properties (obj, &lpc->pm); }
Signature · 1 line
2.26.2
Re: [PATCH v2 6/7] x68: acpi: trigger SMI before sending hotplug Notify event to OSPM
Quoted 31 lines · Igor Mammedov
In case firmware has negotiated CPU hotplug SMI feature, generate AML to describe SMI IO port region and send SMI to firmware on each CPU hotplug SCI in case new CPUs were hotplugged.
Since new CPUs can be hotplugged while
CPU_SCAN_METHODis running we can't send SMI before new CPUs are fetched from QEMU as it could cause sending Notify to a CPU that firmware hasn't seen yet. So fetch new CPUs into local cache first and then send SMI and after that sends Notify events to cached CPUs. This should ensure that Notify is sent only to CPUs which were processed by firmware first.
Any CPUs that were hotplugged after caching will be processed by the nextCPU_SCAN_METHOD, when pending SCI is handled.Signed-off-by Igor Mammedov <[email protected]>---
v2:
- clear insert event after firmware has returned
control from SMI. (Laszlo Ersek <[email protected]>)
v1:
- make sure that Notify is sent only to CPUs seen by FW
- (Laszlo Ersek <[email protected]>)
- use macro instead of x-smi-negotiated-features
- style fixes
- reserve whole SMI block (0xB2,0xB3)
v0:
- s/aml_string/aml_eisaid/
/fixes Windows BSOD, on nonsense value/ (Laszlo Ersek <[email protected]>)
- put SMI device under PCI0 like the rest of hotplug IO port
- do not generate SMI AML if CPU hotplug SMI feature hasn't been negotiated
Quoted 8 lines
Signed-off-by Igor Mammedov <[email protected]>--- include/hw/acpi/cpu.h | 1 + include/hw/i386/ich9.h | 2 ++ hw/acpi/cpu.c | 80 +++++++++++++++++++++++++++++++++++++++--- hw/i386/acpi-build.c | 35 +++++++++++++++++- hw/isa/lpc_ich9.c | 3 ++ 5 files changed, 115 insertions(+), 6 deletions(-)
For easing review, this patch could be split in several patches, I think. I'm not saying that's a "requirement", just that it would be possible, and could help review.
* Patch "a":
[subject:]
x86: ich9: expose "smi_negotiated_features" as a QOM property
[commit message:]
Expose the "smi_negotiated_features" field of ICH9LPCState as a QOM property.
[code extracted from current patch follows]
Quoted 19 lines
include/hw/i386/ich9.h +2
-0@@ -245,6 +245,8 @@ typedef struct ICH9LPCState {#define ICH9_SMB_HST_D1 0x06#define ICH9_SMB_HOST_BLOCK_DB 0x07 +#define ICH9_LPC_SMI_NEGOTIATED_FEAT_PROP "x-smi-negotiated-features" +/* bit positions used in fw_cfg SMI feature negotiation */ #define ICH9_LPC_SMI_F_BROADCAST_BIT 0#define ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT 1hw/isa/lpc_ich9.c +0
-0
hw/isa/lpc_ich9.c static void ich9_lpc_initfn(Object *obj) · line 655
Quoted 9 lines
hw/isa/lpc_ich9.c +3
-0@@ -647,6 +647,9 @@ static void ich9_lpc_initfn(Object *obj) &acpi_enable_cmd, OBJ_PROP_FLAG_READ);object_property_add_uint8_ptr (OBJECT (lpc),ACPI_PM_PROP_ACPI_DISABLE_CMD , &acpi_disable_cmd,OBJ_PROP_FLAG_READ ); +object_property_add_uint64_ptr (obj,ICH9_LPC_SMI_NEGOTIATED_FEAT_PROP , + &lpc->smi_negotiated_features, +OBJ_PROP_FLAG_READ );ich9_pm_add_properties (obj, &lpc->pm); }
For sub-patch "a":
* Patch "b":
[subject:]
x86: acpi: introduce "AcpiPmInfo.smi_on_cpuhp"
[commit message:]
Translate the "CPU hotplug with SMI" feature bit, from the property added in the last patch, to a dedicated boolean in AcpiPmInfo.
[code extracted from current patch follows]
Quoted 27 lines
hw/i386/acpi-build.c +4
-0@@ -95,6 +95,7 @@ typedef struct AcpiPmInfo {bool s3_disabled;bool s4_disabled;bool pcihp_bridge_en; +bool smi_on_cpuhp;uint8_t s4_val;AcpiFadtData fadt;uint16_t cpu_hp_io_base;@@ -194,6 +195,7 @@ static void acpi_get_pm_info(MachineState *machine, AcpiPmInfo *pm) pm->cpu_hp_io_base =0 ; pm->pcihp_io_base =0 ; pm->pcihp_io_len =0 ; + pm->smi_on_cpuhp = false;assert (obj);init_common_fadt_data (machine, obj, &pm->fadt);@@ -207,12 +209,16 @@ static void acpi_get_pm_info(MachineState *machine, AcpiPmInfo *pm)object_property_get_uint (obj,ACPI_PCIHP_IO_LEN_PROP ,NULL ); }if (lpc) { +uint64_t smi_features =object_property_get_uint (lpc, +ICH9_LPC_SMI_NEGOTIATED_FEAT_PROP ,NULL );struct AcpiGenericAddress r = { .space_id =AML_AS_SYSTEM_IO ,
hw/i386/acpi-build.c static void acpi_get_pm_info(MachineState *machine, AcpiPmInfo *pm) · line 224
Quoted 10 lines
hw/i386/acpi-build.c +2
-0.bit_width = 8, .address = ICH9_RST_CNT_IOPORT }; pm->fadt.reset_reg = r; pm->fadt.reset_val =0xf ; pm->fadt.flags |=1 <<ACPI_FADT_F_RESET_REG_SUP ; pm->cpu_hp_io_base =ICH9_CPU_HOTPLUG_IO_BASE ; + pm->smi_on_cpuhp = + !!(smi_features &BIT_ULL (ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT )); }/* The above need not be conditional on machine type because the reset port
For sub-patch "b":
* Patch "c":
[subject:]
x86: acpi: introduce the "PCI0.SMI0" ACPI device
[commit message:]
When CPU hotplug with SMI has been negotiated, describe the SMI register block in the DSDT. Pass the ACPI name of the SMI control register to build_cpus_aml(), so that CPU_SCAN_METHOD can access the register in the next patch.
[code extracted from current patch follows]
Quoted 50 lines
include/hw/acpi/cpu.h +1
-0@@ -50,6 +50,7 @@ void cpu_hotplug_hw_init(MemoryRegion *as, Object *owner,typedef struct CPUHotplugFeatures {bool acpi_1_compatible;bool has_legacy_cphp; +const char *smi_path; }CPUHotplugFeatures ; void build_cpus_aml(Aml *table, MachineState *machine, CPUHotplugFeatures opts,hw/i386/acpi-build.c +26
-0@@ -1515,6 +1521,32 @@ build_dsdt(GArray *table_data, BIOSLinker *linker,aml_append (dev,aml_name_decl ("_UID" ,aml_int (1 )));aml_append (dev,build_q35_osc_method ());aml_append (sb_scope, dev); + +if (pm->smi_on_cpuhp) { +/* reserve SMI block resources, IO ports 0xB2, 0xB3 */ + dev =aml_device ("PCI0.SMI0" ); +aml_append (dev,aml_name_decl ("_HID" ,aml_eisaid ("PNP0A06" ))); +aml_append (dev,aml_name_decl ("_UID" ,aml_string ("SMI resources" ))); + crs =aml_resource_template (); +aml_append (crs, +aml_io ( +AML_DECODE16 , +ACPI_PORT_SMI_CMD , +ACPI_PORT_SMI_CMD , +1 , +2 ) + ); +aml_append (dev,aml_name_decl ("_CRS" , crs)); +aml_append (dev,aml_operation_region ("SMIR" ,AML_SYSTEM_IO , +aml_int (ACPI_PORT_SMI_CMD ),2 )); + field =aml_field ("SMIR" ,AML_BYTE_ACC ,AML_NOLOCK , +AML_WRITE_AS_ZEROS ); +aml_append (field,aml_named_field ("SMIC" ,8 )); +aml_append (field,aml_reserved_field (8 )); +aml_append (dev, field); +aml_append (sb_scope, dev); + } +aml_append (dsdt, sb_scope);build_hpet_aml (dsdt);
hw/i386/acpi-build.c build_dsdt(GArray *table_data, BIOSLinker *linker, · line 1569
Quoted 9 lines
hw/i386/acpi-build.c +2
-1@@ -1530,7 +1562,8 @@ build_dsdt(GArray *table_data, BIOSLinker *linker,build_legacy_cpu_hotplug_aml (dsdt, machine, pm->cpu_hp_io_base); }else {CPUHotplugFeatures opts = { - .acpi_1_compatible = true, .has_legacy_cphp = true + .acpi_1_compatible = true, .has_legacy_cphp = true, + .smi_path = pm->smi_on_cpuhp ?"\\_SB.PCI0.SMI0.SMIC" :NULL , };build_cpus_aml (dsdt, machine, opts, pm->cpu_hp_io_base,"\\_SB.PCI0" ,"\\_GPE._E02" );
For sub-patch "c":
* Patch "d":
[subject: copy from current (large) patch]
[commit message: copy from current (large) patch]
[code extracted from current patch follows, with my comments]
Quoted 36 lines
hw/acpi/cpu.c +12
-0@@ -14,6 +14,8 @@#define ACPI_CPU_CMD_DATA_OFFSET_RW 8#define ACPI_CPU_CMD_DATA2_OFFSET_R 0 +#define OVMF_CPUHP_SMI_CMD 4 +enum {CPHP_GET_NEXT_CPU_WITH_EVENT_CMD =0 ,CPHP_OST_EVENT_CMD =1 ,@@ -321,6 +323,7 @@ const VMStateDescription vmstate_cpu_hotplug = {#define CPU_NOTIFY_METHOD "CTFY"#define CPU_EJECT_METHOD "CEJ0"#define CPU_OST_METHOD "COST" +#define CPU_ADDED_LIST "CNEW"#define CPU_ENABLED "CPEN"#define CPU_SELECTOR "CSEL"@@ -471,21 +474,61 @@ void build_cpus_aml(Aml *table, MachineState *machine, CPUHotplugFeatures opts,Aml *dev_chk =aml_int (1 );Aml *eject_req =aml_int (3 );Aml *next_cpu_cmd =aml_int (CPHP_GET_NEXT_CPU_WITH_EVENT_CMD ); +Aml *num_added_cpus =aml_local (1 ); +Aml *cpu_idx =aml_local (2 ); +Aml *uid =aml_local (3 ); +Aml *new_cpus =aml_name (CPU_ADDED_LIST );aml_append (method,aml_acquire (ctrl_lock,0xFFFF )); + +/* use named package as old Windows don't support it in local var */ +if (arch_ids->len <=256 ) { +/* +* For compatibility with Windows Server 2008 (max 256 cpus),
hw/acpi/cpu.c void build_cpus_aml(Aml *table, MachineState *machine, CPUHotplugFeatures opts, · line 497
Quoted 10 lines
hw/acpi/cpu.c +10
-0+* use ACPI1.0 PackageOp which can cache max 255 elements. +* Which is fine for 256 CPUs VM. Max 255 can be hotplugged, +* sice at least one CPU must be already present. +*/ +aml_append (method,aml_name_decl (CPU_ADDED_LIST , +aml_package (arch_ids->len))); + }else { +aml_append (method,aml_name_decl (CPU_ADDED_LIST , +aml_varpackage (arch_ids->len))); + }
(1) Both package sizes are off-by-one. We only need room for the CPUs that have events pending, and that excludes CPU#0.
In particular, in the compatibility case, when "arch_ids->len" is exactly 256, then we pass 256 to aml_package(). However, aml_package() -- correctly! -- takes:
uint8_t num_elements
So with 256 VCPUs, we'd pass a zero "num_elements".
The comparison (<= 256) is correct, we just need to pass
arch_ids->len - 1
to both aml_package() and aml_varpackage().
Quoted 53 lines
hw/acpi/cpu.c +27
-5+ +aml_append (method,aml_store (zero, num_added_cpus));aml_append (method,aml_store (one, has_event)); - while_ctx =aml_while (aml_equal (has_event, one)); +/* start scan from the 1st CPU */ +aml_append (method,aml_store (zero, uid)); + while_ctx =aml_while (aml_land (aml_equal (has_event, one), +aml_lless (uid,aml_int (arch_ids->len)))); {/* clear loop exit condition, ins_evt/rm_evt checks * will set it to 1 while next_cpu_cmd returns a CPU * with events */ aml_append (while_ctx,aml_store (zero, has_event)); + +aml_append (while_ctx,aml_store (uid, cpu_selector));aml_append (while_ctx,aml_store (next_cpu_cmd, cpu_cmd)); + +/* +* wrap around case, scan is complete, exit loop. +* It happens since events are not cleared in scan loop, +* so next_cpu_cmd continues to find already processed CPUs. +*/ + ifctx =aml_if (aml_lless (cpu_data, uid)); + { +aml_append (ifctx,aml_break ()); + } +aml_append (while_ctx, ifctx); + +aml_append (while_ctx,aml_store (cpu_data, uid)); ifctx =aml_if (aml_equal (ins_evt, one)); { -aml_append (ifctx, -aml_call2 (CPU_NOTIFY_METHOD , cpu_data, dev_chk)); -aml_append (ifctx,aml_store (one, ins_evt)); +/* cache added CPUs to Notify/Wakeup later */ +aml_append (ifctx,aml_store (uid, +aml_index (new_cpus, num_added_cpus))); +aml_append (ifctx,aml_increment (num_added_cpus));aml_append (ifctx,aml_store (one, has_event)); }aml_append (while_ctx, ifctx);@@ -493,14 +536,41 @@ void build_cpus_aml(Aml *table, MachineState *machine, CPUHotplugFeatures opts, ifctx =aml_if (aml_equal (rm_evt, one)); {aml_append (ifctx, -aml_call2 (CPU_NOTIFY_METHOD , cpu_data, eject_req)); +aml_call2 (CPU_NOTIFY_METHOD , uid, eject_req));aml_append (ifctx,aml_store (one, rm_evt));aml_append (ifctx,aml_store (one, has_event)); }aml_append (else_ctx, ifctx);aml_append (while_ctx, else_ctx); +aml_append (while_ctx,aml_increment (uid));
hw/acpi/cpu.c void build_cpus_aml(Aml *table, MachineState *machine, CPUHotplugFeatures opts, · line 555
Quoted 10 lines
hw/acpi/cpu.c +10
-0+ } +aml_append (method, while_ctx); + +/* +* in case FW negotiated ICH9_LPC_SMI_F_CPU_HOTPLUG_BIT, +* make upcall to FW, so it can pull in new CPUs before +* OS is notified and wakes them up +*/ +if (opts.smi_path) { + ifctx =aml_if (aml_lnot (aml_equal (num_added_cpus, zero)));
(2) The composed "aml_lnot(aml_equal())" is not wrong, but I think aml_lgreater() would be simpler (for the QEMU source code anyway).
Feel free to ignore.
Quoted 4 lines
hw/acpi/cpu.c +4
-0+ { +aml_append (ifctx,aml_store (aml_int (OVMF_CPUHP_SMI_CMD ), +aml_name ("%s" , opts.smi_path))); + }
hw/acpi/cpu.c void build_cpus_aml(Aml *table, MachineState *machine, CPUHotplugFeatures opts, · line 569
Quoted 10 lines
hw/acpi/cpu.c +10
-0+aml_append (method, ifctx); + } + +/* Notify OSPM about new CPUs and clear insert events */ +aml_append (method,aml_store (zero, cpu_idx)); + while_ctx =aml_while (aml_lless (cpu_idx, num_added_cpus)); + { +aml_append (while_ctx,aml_call2 (CPU_NOTIFY_METHOD , +aml_derefof (aml_index (new_cpus, cpu_idx)), dev_chk)); +aml_append (while_ctx,aml_store (one, ins_evt));
(3) Before writing 1 to CINS, you need to set CSEL as well.
This bug is masked if the loop finds *at most* one added CPU. To see why, here's the decompiled method, with a possible CPUs count of 4, and the local variable names substituted:
1 Method (CSCN, 0, Serialized)
2 {
3 Acquire (\_SB.PCI0.PRES.CPLK, 0xFFFF)
4 Name (CNEW, Package (0x04){})
5
6 Local_NumAddedCpus = Zero
7 Local_HasEvent = One
8 Local_Uid = Zero
9
10 While (((Local_HasEvent == One) && (Local_Uid < 0x04)))
11 {
12 Local_HasEvent = Zero
13 \_SB.PCI0.PRES.CSEL = Local_Uid
14 \_SB.PCI0.PRES.CCMD = Zero
15 If ((\_SB.PCI0.PRES.CDAT < Local_Uid))
16 {
17 Break
18 }
19
20 Local_Uid = \_SB.PCI0.PRES.CDAT
21 If ((\_SB.PCI0.PRES.CINS == One))
22 {
23 CNEW [Local_NumAddedCpus] = Local_Uid
24 Local_NumAddedCpus++
25 Local_HasEvent = One
26 }
27 ElseIf ((\_SB.PCI0.PRES.CRMV == One))
28 {
29 CTFY (Local_Uid, 0x03)
30 \_SB.PCI0.PRES.CRMV = One
31 Local_HasEvent = One
32 }
33
34 Local_Uid++
35 }
36
37 If ((Local_NumAddedCpus != Zero))
38 {
39 \_SB.PCI0.SMI0.SMIC = 0x04
40 }
41
42 Local_CpuIdx = Zero
43 While ((Local_CpuIdx < Local_NumAddedCpus))
44 {
45 CTFY (DerefOf (CNEW [Local_CpuIdx]), One)
46 \_SB.PCI0.PRES.CINS = One
47 Local_CpuIdx++
48 }
49
50 Release (\_SB.PCI0.PRES.CPLK)
51 }If the loop has found exactly one VCPU with a pending event, then we must have exited the loop in one of two ways:
- The UID of the VCPU with the pending event was maximal, and so the Local_Uid limit in the While fired on the next iteration (line 10).
- Otherwise, the search wrapped on the next iteration (line 17).
In either case, the loop leaves the "right" CPU selector in place:
- In the first case, when we exit on line 10, we never write to CSEL again (line 13).
- In the second case, we wrap back to the *one and only* VCPU with pending events, on line 14, before we exit on line 17.
And so when we reach the *one and only* write to CINS on line 46, the CPU selector happens to be correct.
Because of this, I happened to test this patch successfully with e.g.
virsh setvcpu DOMAIN 3 --enable --live
(note: "setvcpu", singular).
However, the bug can be triggered when plugging multiple VCPUs in quick succession, with e.g.
virsh setvcpus DOMAIN 8 --live
(note "setvcpus", plural).
So I would suggest fetching the CNEW array element back into "uid" first, then using "uid" for both the NOTIFY call, and the (currently missing) restoration of CSEL. Then we can write 1 to CINS.
Expressed as a patch on top of yours:
Quoted 8 lines
hw/acpi/cpu.c +0
-0@@ -564,8 +564,11 @@ void build_cpus_aml(Aml *table, MachineState *machine, CPUHotplugFeatures opts,aml_append (method,aml_store (zero, cpu_idx)); while_ctx =aml_while (aml_lless (cpu_idx, num_added_cpus)); {
hw/acpi/cpu.c void build_cpus_aml(Aml *table, MachineState *machine, CPUHotplugFeatures opts, · line 574
Quoted 10 lines
hw/acpi/cpu.c +5
-2-aml_append (while_ctx,aml_call2 (CPU_NOTIFY_METHOD , -aml_derefof (aml_index (new_cpus, cpu_idx)), dev_chk)); +aml_append (while_ctx, +aml_store (aml_derefof (aml_index (new_cpus, cpu_idx)), uid)); +aml_append (while_ctx, +aml_call2 (CPU_NOTIFY_METHOD , uid, dev_chk)); +aml_append (while_ctx,aml_store (uid, cpu_selector));aml_append (while_ctx,aml_store (one, ins_evt));aml_append (while_ctx,aml_increment (cpu_idx)); }
This effects the following change, in the decompiled method:
Quoted 9 lines
hw/acpi/cpu.c +0
-0@@ -37,15 +37,17 @@If ((Local_NumAddedCpus != Zero)) { \_SB.PCI0.SMI0.SMIC = 0x04 } Local_CpuIdx = Zero While ((Local_CpuIdx < Local_NumAddedCpus)) {
hw/acpi/cpu.c line 53
Quoted 10 lines
hw/acpi/cpu.c +3
-1-CTFY (DerefOf (CNEW [Local_CpuIdx]), One) + Local_Uid =DerefOf (CNEW [Local_CpuIdx]) + CTFY (Local_Uid, One) + \_SB.PCI0.PRES.CSEL = Local_Uid \_SB.PCI0.PRES.CINS = One Local_CpuIdx++ } Release (\_SB.PCI0.PRES.CPLK) }
With this change, the
virsh setvcpus DOMAIN 8 --live
command works for me. The topology in my test domain has CPU#0 and CPU#2 cold-plugged, so the command adds 6 VCPUs. Viewed from the firmware side, the 6 "device_add" commands, issued in close succession by libvirtd, coalesce into 4 "batches". (And of course the firmware sees the 4 batches back-to-back.)
Note the "PluggedCount" message, which reports the size of each batch:
- Batch#1 adds CPU#1:
Quoted 5 lines
QemuCpuhpCollectApicIds: CurrentSelector=1: insert
QemuCpuhpCollectApicIds: ApicId=0x00000001
QemuCpuhpCollectApicIds: CurrentSelector=2 PendingSelector=1: wrap-around
QemuCpuhpCollectApicIds: PluggedCount=1 ToUnplugCount=0
CpuHotplugMmi: hot-added APIC ID0x00000001, SMBASE0x7FF7A000,EFI_SMM_CPU_SERVICE_PROTOCOLassigned number 2
- Batch#2 adds CPU#3:
Quoted 5 lines
QemuCpuhpCollectApicIds: CurrentSelector=3: insert
QemuCpuhpCollectApicIds: ApicId=0x00000003
QemuCpuhpCollectApicIds: CurrentSelector=4 PendingSelector=3: wrap-around
QemuCpuhpCollectApicIds: PluggedCount=1 ToUnplugCount=0
CpuHotplugMmi: hot-added APIC ID0x00000003, SMBASE0x7FF7C000,EFI_SMM_CPU_SERVICE_PROTOCOLassigned number 3
- Batch#3 adds CPU#4, CPU#5, CPU#6:
Quoted 11 lines
QemuCpuhpCollectApicIds: CurrentSelector=4: insert
QemuCpuhpCollectApicIds: ApicId=0x00000004
QemuCpuhpCollectApicIds: CurrentSelector=5: insert
QemuCpuhpCollectApicIds: ApicId=0x00000005
QemuCpuhpCollectApicIds: CurrentSelector=6: insert
QemuCpuhpCollectApicIds: ApicId=0x00000006
QemuCpuhpCollectApicIds: CurrentSelector=7 PendingSelector=4: wrap-around
QemuCpuhpCollectApicIds: PluggedCount=3 ToUnplugCount=0
CpuHotplugMmi: hot-added APIC ID0x00000004, SMBASE0x7FF7E000,EFI_SMM_CPU_SERVICE_PROTOCOLassigned number 4
CpuHotplugMmi: hot-added APIC ID0x00000005, SMBASE0x7FF80000,EFI_SMM_CPU_SERVICE_PROTOCOLassigned number 5
CpuHotplugMmi: hot-added APIC ID0x00000006, SMBASE0x7FF82000,EFI_SMM_CPU_SERVICE_PROTOCOLassigned number 6
- Batch#4 adds CPU#7:
Quoted 4 lines
QemuCpuhpCollectApicIds: CurrentSelector=7: insert
QemuCpuhpCollectApicIds: ApicId=0x00000007
QemuCpuhpCollectApicIds: PluggedCount=1 ToUnplugCount=0
CpuHotplugMmi: hot-added APIC ID0x00000007, SMBASE0x7FF84000,EFI_SMM_CPU_SERVICE_PROTOCOLassigned number 7
Thanks,
Laszlo
Quoted 7 lines · Igor Mammedov
hw/acpi/cpu.c +2
-0+aml_append (while_ctx,aml_increment (cpu_idx)); }aml_append (method, while_ctx); +aml_append (method,aml_release (ctrl_lock)); }aml_append (cpus_dev, method);
Re: [PATCH v2 6/7] x68: acpi: trigger SMI before sending hotplug Notify event to OSPM
Quoted 15 lines · On Tue, 25 Aug 2020 19:25:48 +0200 Laszlo Ersek <[email protected]> wrote:
Quoted 14 lines · Igor Mammedov
In case firmware has negotiated CPU hotplug SMI feature, generate AML to describe SMI IO port region and send SMI to firmware on each CPU hotplug SCI in case new CPUs were hotplugged.
Since new CPUs can be hotplugged while
CPU_SCAN_METHODis running we can't send SMI before new CPUs are fetched from QEMU as it could cause sending Notify to a CPU that firmware hasn't seen yet. So fetch new CPUs into local cache first and then send SMI and after that sends Notify events to cached CPUs. This should ensure that Notify is sent only to CPUs which were processed by firmware first.
Any CPUs that were hotplugged after caching will be processed by the nextCPU_SCAN_METHOD, when pending SCI is handled.
Quoted 5 lines
Quoted 5 lines
Signed-off-by Igor Mammedov <[email protected]>---
v2:
- clear insert event after firmware has returned control from SMI. (Laszlo Ersek <[email protected]>)
Laszlo,
Thanks a lot for such detailed review
I'll respin series with your feed back incorporated.
[...]
Re: [PATCH v2 6/7] x68: acpi: trigger SMI before sending hotplug Notify event to OSPM
In reply to Laszlo ErsekHi Igor,
Quoted 49 lines · Laszlo Ersek
So I would suggest fetching the CNEW array element back into "uid" first, then using "uid" for both the NOTIFY call, and the (currently missing) restoration of CSEL. Then we can write 1 to CINS.
Expressed as a patch on top of yours:
Quoted 8 lines
hw/acpi/cpu.c +0
-0@@ -564,8 +564,11 @@ void build_cpus_aml(Aml *table, MachineState *machine, CPUHotplugFeatures opts,aml_append (method,aml_store (zero, cpu_idx)); while_ctx =aml_while (aml_lless (cpu_idx, num_added_cpus)); {hw/acpi/cpu.c void build_cpus_aml(Aml *table, MachineState *machine, CPUHotplugFeatures opts, · line 574
Quoted 10 lines
hw/acpi/cpu.c +5
-2-aml_append (while_ctx,aml_call2 (CPU_NOTIFY_METHOD , -aml_derefof (aml_index (new_cpus, cpu_idx)), dev_chk)); +aml_append (while_ctx, +aml_store (aml_derefof (aml_index (new_cpus, cpu_idx)), uid)); +aml_append (while_ctx, +aml_call2 (CPU_NOTIFY_METHOD , uid, dev_chk)); +aml_append (while_ctx,aml_store (uid, cpu_selector));aml_append (while_ctx,aml_store (one, ins_evt));aml_append (while_ctx,aml_increment (cpu_idx)); }This effects the following change, in the decompiled method:
Quoted 9 lines
hw/acpi/cpu.c +0
-0@@ -37,15 +37,17 @@If ((Local_NumAddedCpus != Zero)) { \_SB.PCI0.SMI0.SMIC = 0x04 } Local_CpuIdx = Zero While ((Local_CpuIdx < Local_NumAddedCpus)) {hw/acpi/cpu.c line 53
Quoted 10 lines
hw/acpi/cpu.c +3
-1-CTFY (DerefOf (CNEW [Local_CpuIdx]), One) + Local_Uid =DerefOf (CNEW [Local_CpuIdx]) + CTFY (Local_Uid, One) + \_SB.PCI0.PRES.CSEL = Local_Uid \_SB.PCI0.PRES.CINS = One Local_CpuIdx++ } Release (\_SB.PCI0.PRES.CPLK) }With this change, the
Quoted 7 lines
virsh setvcpus DOMAIN 8 --livecommand works for me. The topology in my test domain has CPU#0 and CPU#2 cold-plugged, so the command adds 6 VCPUs. Viewed from the firmware side, the 6 "
device_add" commands, issued in close succession by libvirtd, coalesce into 4 "batches". (And of course the firmware sees the 4 batches back-to-back.)
unfortunately, with more testing, I have run into two more races:
(1) When a "device_add" occurs after the ACPI loop collects the CPUS from the register block, but before the SMI.
Here, the "stray CPU" is processed fine by the firmware. However, the CTFY loop in ACPI does not know about the CPU, so it doesn't clear the pending insert event for it. And when the firmware is entered with an SMI for the *next* time, the firmware sees the same CPU *again* as pending, and tries to relocate it again. Bad things happen.
(2) When a "device_add" occurs after the SMI, but before the firmware collects the pending CPUs from the register block.
Here, the firmware collects the "stray CPU". However, the "broadcast SMI", with which we entered the firmware, did *not* cover the stray CPU -- the CPU_FOREACH() loop in ich9_apm_ctrl_changed() could not make the SMI pending for the new CPU, because at that time, the CPU had not been added yet. As a result, when the firmware sends an INIT-SIPI-SIPI to the new CPU, expecting it to boot right into SMM, the new CPU instead boots straight into the post-RSM (normal mode) "pen", skipping its initial SMI handler. Meaning that the CPU halts nicely, but its SMBASE is never relocated, and the SMRAM message exchange with the BSP falls apart.
Possible mitigations I can think of:
For problem (1):
(1a) Change the firmware so it notices that it has relocated the
"stray" CPU before -- such CPUs should be simply skipped in the firmware. The next time the CTFY loop runs in ACPI, it will clear the pending event.
(1b) Alternatively, stop consuming the hotplug register block in the
firmware altogether, and work out general message passing, from ACPI to firmware. See the outline here:
http://mid.mail-archive.com/[email protected]
For problem (2):
(2a) Change the firmware so that it sends a directed SMI as well to
each CPU, just before sending an INIT-SIPI-SIPI. This should be idempotent -- if the broadcast SMI *has* covered the the CPU, then sending a directed SMI should make no difference.
(2b) Alternatively, change the "device_add" command in QEMU so that,
if "CPU hotplug with SMI" has been negotiated, the new CPU is added with the SMI made pending for it at once. (That is, no hot-plugged CPU would exist with the directed SMI *not* pending for it.)
(2c) Alternatively, approach (1b) would fix problem (2) as well -- the
firmware would only relocate such CPUs that ACPI collected before injecting the SMI. So all those CPUs would have the SMI pending.
I can experiment with (1a) and (2a), but note that for unplug, we're likely going to need the array passing method (1b) anyway. I'm concerned that (1a) and (2a) together may not fix all possible races (i.e. we might see more kinds).
What's important is that, *IF* we need to change anything in the firmware for fixing these races, then we either need to do so urgently, *or* I have to revert OVMF commit 5ba203b54e59 ("OvmfPkg/SmmControl2Dxe:
negotiate ICH9_LPC_SMI_F_CPU_HOTPLUG", 2020-08-24).
That's because we're in feature freeze for edk2-stable202008
and we shouldn't make a release with ICH9_LPC_SMI_F_CPU_HOTPLUG negotiated, knowing that there are races.
Please advise!
Thanks,
Laszlo
Re: [PATCH v2 6/7] x68: acpi: trigger SMI before sending hotplug Notify event to OSPM
Quoted 100 lines · On Wed, 26 Aug 2020 11:24:14 +0200 Laszlo Ersek <[email protected]> wrote:
Hi Igor,
Quoted 49 lines · Laszlo Ersek
So I would suggest fetching the CNEW array element back into "uid" first, then using "uid" for both the NOTIFY call, and the (currently missing) restoration of CSEL. Then we can write 1 to CINS.
Expressed as a patch on top of yours:
Quoted 8 lines
hw/acpi/cpu.c +0
-0@@ -564,8 +564,11 @@ void build_cpus_aml(Aml *table, MachineState *machine, CPUHotplugFeatures opts,aml_append (method,aml_store (zero, cpu_idx)); while_ctx =aml_while (aml_lless (cpu_idx, num_added_cpus)); {hw/acpi/cpu.c void build_cpus_aml(Aml *table, MachineState *machine, CPUHotplugFeatures opts, · line 574
Quoted 10 lines
hw/acpi/cpu.c +5
-2-aml_append (while_ctx,aml_call2 (CPU_NOTIFY_METHOD , -aml_derefof (aml_index (new_cpus, cpu_idx)), dev_chk)); +aml_append (while_ctx, +aml_store (aml_derefof (aml_index (new_cpus, cpu_idx)), uid)); +aml_append (while_ctx, +aml_call2 (CPU_NOTIFY_METHOD , uid, dev_chk)); +aml_append (while_ctx,aml_store (uid, cpu_selector));aml_append (while_ctx,aml_store (one, ins_evt));aml_append (while_ctx,aml_increment (cpu_idx)); }This effects the following change, in the decompiled method:
Quoted 9 lines
hw/acpi/cpu.c +0
-0@@ -37,15 +37,17 @@If ((Local_NumAddedCpus != Zero)) { \_SB.PCI0.SMI0.SMIC = 0x04 } Local_CpuIdx = Zero While ((Local_CpuIdx < Local_NumAddedCpus)) {hw/acpi/cpu.c line 53
Quoted 10 lines
hw/acpi/cpu.c +3
-1-CTFY (DerefOf (CNEW [Local_CpuIdx]), One) + Local_Uid =DerefOf (CNEW [Local_CpuIdx]) + CTFY (Local_Uid, One) + \_SB.PCI0.PRES.CSEL = Local_Uid \_SB.PCI0.PRES.CINS = One Local_CpuIdx++ } Release (\_SB.PCI0.PRES.CPLK) }With this change, the
Quoted 7 lines
virsh setvcpus DOMAIN 8 --livecommand works for me. The topology in my test domain has CPU#0 and CPU#2 cold-plugged, so the command adds 6 VCPUs. Viewed from the firmware side, the 6 "
device_add" commands, issued in close succession by libvirtd, coalesce into 4 "batches". (And of course the firmware sees the 4 batches back-to-back.)unfortunately, with more testing, I have run into two more races:
(1) When a "
device_add" occurs after the ACPI loop collects the CPUS from the register block, but before the SMI.Here, the "stray CPU" is processed fine by the firmware. However, the CTFY loop in ACPI does not know about the CPU, so it doesn't clear the pending insert event for it. And when the firmware is entered with an SMI for the *next* time, the firmware sees the same CPU *again* as pending, and tries to relocate it again. Bad things happen.
(2) When a "
device_add" occurs after the SMI, but before the firmware collects the pending CPUs from the register block.Here, the firmware collects the "stray CPU". However, the "broadcast SMI", with which we entered the firmware, did *not* cover the stray CPU -- the
CPU_FOREACH()loop inich9_apm_ctrl_changed()could not make the SMI pending for the new CPU, because at that time, the CPU had not been added yet. As a result, when the firmware sends an INIT-SIPI-SIPI to the new CPU, expecting it to boot right into SMM, the new CPU instead boots straight into the post-RSM (normal mode) "pen", skipping its initial SMI handler. Meaning that the CPU halts nicely, but its SMBASE is never relocated, and the SMRAM message exchange with the BSP falls apart.Possible mitigations I can think of:
For problem (1):
(1a) Change the firmware so it notices that it has relocated the
"stray" CPU before -- such CPUs should be simply skipped in the firmware. The next time the CTFY loop runs in ACPI, it will clear the pending event.(1b) Alternatively, stop consuming the hotplug register block in the
firmware altogether, and work out general message passing, from ACPI to firmware. See the outline here:
Quoted 8 lines
http://mid.mail-archive.com/[email protected]
For problem (2):
(2a) Change the firmware so that it sends a directed SMI as well to
each CPU, just before sending an INIT-SIPI-SIPI. This should be idempotent -- if the broadcast SMI *has* covered the the CPU, then sending a directed SMI should make no difference.
may be still racy, as new cpus can arrive diring/after direct broadcast. better would be ignore stray CPUs that didn't pass through SMM relocation.
Quoted 12 lines
(2b) Alternatively, change the "
device_add" command in QEMU so that,
if "CPU hotplug with SMI" has been negotiated, the new CPU is added with the SMI made pending for it at once. (That is, no hot-plugged CPU would exist with the directed SMI *not* pending for it.)(2c) Alternatively, approach (1b) would fix problem (2) as well -- the
firmware would only relocate such CPUs that ACPI collected before injecting the SMI. So all those CPUs would have the SMI pending.
Quoted 4 lines
I can experiment with (1a) and (2a), but note that for unplug, we're likely going to need the array passing method (1b) anyway. I'm concerned that (1a) and (2a) together may not fix all possible races (i.e. we might see more kinds).
Given async nature of device_add, (1a) and (2a) are expected (I've thought it were already handled by fw),
so I'd prefer to continue with current approach if possible. (if fw is not able to deal with 2a without QEMU help, maybe we could add an extra flag in register block to help, though my preference is to avoid it if it's possible)
(2b) if twisting CPU state in QEMU were acceptable we would have had a lot of helping quirks that would put CPU in some desired for a a particular guest code state, and why stop there just discard firmware and configure all devices right from QEMU to and start executing OS code strait away. (it would be faster than going through what real hw does) (I'm afraid it's not going to fly).
(1c) it's still very unclear what direction to take there,
* one as you mentioned, would be introducing new protocol for message passing between acpi and fw.
(so far I've was thinking that payload should be UID of CPU)
* another approach, I was considering was adding an additional flag to register block. So CPU._EJ0 would mark CPU as pending for removal and do SMI upcall to fw to act on it.
Quoted 17 lines
What's important is that, *IF* we need to change anything in the firmware for fixing these races, then we either need to do so urgently, *or* I have to revert OVMF commit
5ba203b54e59("OvmfPkg/SmmControl2Dxe:
negotiateICH9_LPC_SMI_F_CPU_HOTPLUG", 2020-08-24).That's because we're in feature freeze for edk2-stable202008
and we shouldn't make a release with
ICH9_LPC_SMI_F_CPU_HOTPLUGnegotiated, knowing that there are races.Please advise!
Thanks,
Laszlo
Re: [PATCH v2 6/7] x68: acpi: trigger SMI before sending hotplug Notify event to OSPM
Quoted 8 lines · Igor Mammedov
Quoted 4 lines · On Wed, 26 Aug 2020 11:24:14 +0200 Laszlo Ersek <[email protected]> wrote:
(2a) Change the firmware so that it sends a directed SMI as well to
each CPU, just before sending an INIT-SIPI-SIPI. This should be idempotent -- if the broadcast SMI *has* covered the the CPU, then sending a directed SMI should make no difference.may be still racy, as new cpus can arrive diring/after direct broadcast.
(I think you meant "direct SMI")
That's not a problem -- the point is that we must never send INIT-SIPI-SIPI to a hot-added CPU without making an SMI pending for it.
The above condition can be satisfied by not sending INIT-SIPI-SIPI to a VCPU at all.
The firmware collects pending CPUs into an array, and then does the directed SMI + INIT-SIPI-SIPI dance for each, in a separate loop.
So if a new VCPU is hot-added while we are sending the interrupts to the already collected ones, that's fine -- we're not going to send *either* SMI *or* INIT-SIPI-SIPI to that VCPU, until the next time we collect VCPUS.
It's basically the same idea as in your ACPI patch for QEMU.
I'll send the OVMF patches soon.
Thanks!
Laszlo
Re: [PATCH v2 6/7] x68: acpi: trigger SMI before sending hotplug Notify event to OSPM
In reply to Laszlo ErsekQuoted 115 lines · Laszlo Ersek
Hi Igor,
Quoted 49 lines · Laszlo Ersek
So I would suggest fetching the CNEW array element back into "uid" first, then using "uid" for both the NOTIFY call, and the (currently missing) restoration of CSEL. Then we can write 1 to CINS.
Expressed as a patch on top of yours:
Quoted 8 lines
hw/acpi/cpu.c +0
-0@@ -564,8 +564,11 @@ void build_cpus_aml(Aml *table, MachineState *machine, CPUHotplugFeatures opts,aml_append (method,aml_store (zero, cpu_idx)); while_ctx =aml_while (aml_lless (cpu_idx, num_added_cpus)); {hw/acpi/cpu.c void build_cpus_aml(Aml *table, MachineState *machine, CPUHotplugFeatures opts, · line 574
Quoted 10 lines
hw/acpi/cpu.c +5
-2-aml_append (while_ctx,aml_call2 (CPU_NOTIFY_METHOD , -aml_derefof (aml_index (new_cpus, cpu_idx)), dev_chk)); +aml_append (while_ctx, +aml_store (aml_derefof (aml_index (new_cpus, cpu_idx)), uid)); +aml_append (while_ctx, +aml_call2 (CPU_NOTIFY_METHOD , uid, dev_chk)); +aml_append (while_ctx,aml_store (uid, cpu_selector));aml_append (while_ctx,aml_store (one, ins_evt));aml_append (while_ctx,aml_increment (cpu_idx)); }This effects the following change, in the decompiled method:
Quoted 9 lines
hw/acpi/cpu.c +0
-0@@ -37,15 +37,17 @@If ((Local_NumAddedCpus != Zero)) { \_SB.PCI0.SMI0.SMIC = 0x04 } Local_CpuIdx = Zero While ((Local_CpuIdx < Local_NumAddedCpus)) {hw/acpi/cpu.c line 53
Quoted 10 lines
hw/acpi/cpu.c +3
-1-CTFY (DerefOf (CNEW [Local_CpuIdx]), One) + Local_Uid =DerefOf (CNEW [Local_CpuIdx]) + CTFY (Local_Uid, One) + \_SB.PCI0.PRES.CSEL = Local_Uid \_SB.PCI0.PRES.CINS = One Local_CpuIdx++ } Release (\_SB.PCI0.PRES.CPLK) }With this change, the
Quoted 7 lines
virsh setvcpus DOMAIN 8 --livecommand works for me. The topology in my test domain has CPU#0 and CPU#2 cold-plugged, so the command adds 6 VCPUs. Viewed from the firmware side, the 6 "
device_add" commands, issued in close succession by libvirtd, coalesce into 4 "batches". (And of course the firmware sees the 4 batches back-to-back.)unfortunately, with more testing, I have run into two more races:
(1) When a "
device_add" occurs after the ACPI loop collects the CPUS from the register block, but before the SMI.Here, the "stray CPU" is processed fine by the firmware. However, the CTFY loop in ACPI does not know about the CPU, so it doesn't clear the pending insert event for it. And when the firmware is entered with an SMI for the *next* time, the firmware sees the same CPU *again* as pending, and tries to relocate it again. Bad things happen.
(2) When a "
device_add" occurs after the SMI, but before the firmware collects the pending CPUs from the register block.Here, the firmware collects the "stray CPU". However, the "broadcast SMI", with which we entered the firmware, did *not* cover the stray CPU -- the
CPU_FOREACH()loop inich9_apm_ctrl_changed()could not make the SMI pending for the new CPU, because at that time, the CPU had not been added yet. As a result, when the firmware sends an INIT-SIPI-SIPI to the new CPU, expecting it to boot right into SMM, the new CPU instead boots straight into the post-RSM (normal mode) "pen", skipping its initial SMI handler. Meaning that the CPU halts nicely, but its SMBASE is never relocated, and the SMRAM message exchange with the BSP falls apart.Possible mitigations I can think of:
For problem (1):
(1a) Change the firmware so it notices that it has relocated the
"stray" CPU before -- such CPUs should be simply skipped in the firmware. The next time the CTFY loop runs in ACPI, it will clear the pending event.(1b) Alternatively, stop consuming the hotplug register block in the
firmware altogether, and work out general message passing, from ACPI to firmware. See the outline here:http://mid.mail-archive.com/[email protected]
For problem (2):
(2a) Change the firmware so that it sends a directed SMI as well to
each CPU, just before sending an INIT-SIPI-SIPI. This should be idempotent -- if the broadcast SMI *has* covered the the CPU, then sending a directed SMI should make no difference.(2b) Alternatively, change the "
device_add" command in QEMU so that,
if "CPU hotplug with SMI" has been negotiated, the new CPU is added with the SMI made pending for it at once. (That is, no hot-plugged CPU would exist with the directed SMI *not* pending for it.)
Quoted 6 lines
(2c) Alternatively, approach (1b) would fix problem (2) as well -- the
firmware would only relocate such CPUs that ACPI collected before injecting the SMI. So all those CPUs would have the SMI pending.I can experiment with (1a) and (2a),
My patches for (1a) and (1b) seem to work -- my workstation has 10 PCPUs, and I'm using a guest with 20 possible VCPUs and 2 cold-plugged VCPUs on it, for testing. The patches survive the hot-plugging of 18 VCPUs in one go, or two batches like 9+9. I can see the fixes being exercised.
Unless you strongly disagree (or I find issues in further testing), I propose that I post these fixes to edk2-devel (they should still be in scope for the upcoming release), and that we stick with your current patch series for QEMU (v3 -- upcoming, or maybe already posted).
Thanks!
Laszlo
Re: [PATCH v2 6/7] x68: acpi: trigger SMI before sending hotplug Notify event to OSPM
Quoted 116 lines · Laszlo Ersek
Quoted 115 lines · Laszlo Ersek
Hi Igor,
Quoted 49 lines · Laszlo Ersek
So I would suggest fetching the CNEW array element back into "uid" first, then using "uid" for both the NOTIFY call, and the (currently missing) restoration of CSEL. Then we can write 1 to CINS.
Expressed as a patch on top of yours:
Quoted 8 lines
hw/acpi/cpu.c +0
-0@@ -564,8 +564,11 @@ void build_cpus_aml(Aml *table, MachineState *machine, CPUHotplugFeatures opts,aml_append (method,aml_store (zero, cpu_idx)); while_ctx =aml_while (aml_lless (cpu_idx, num_added_cpus)); {hw/acpi/cpu.c void build_cpus_aml(Aml *table, MachineState *machine, CPUHotplugFeatures opts, · line 574
Quoted 10 lines
hw/acpi/cpu.c +5
-2-aml_append (while_ctx,aml_call2 (CPU_NOTIFY_METHOD , -aml_derefof (aml_index (new_cpus, cpu_idx)), dev_chk)); +aml_append (while_ctx, +aml_store (aml_derefof (aml_index (new_cpus, cpu_idx)), uid)); +aml_append (while_ctx, +aml_call2 (CPU_NOTIFY_METHOD , uid, dev_chk)); +aml_append (while_ctx,aml_store (uid, cpu_selector));aml_append (while_ctx,aml_store (one, ins_evt));aml_append (while_ctx,aml_increment (cpu_idx)); }This effects the following change, in the decompiled method:
Quoted 9 lines
hw/acpi/cpu.c +0
-0@@ -37,15 +37,17 @@If ((Local_NumAddedCpus != Zero)) { \_SB.PCI0.SMI0.SMIC = 0x04 } Local_CpuIdx = Zero While ((Local_CpuIdx < Local_NumAddedCpus)) {hw/acpi/cpu.c line 53
Quoted 10 lines
hw/acpi/cpu.c +3
-1-CTFY (DerefOf (CNEW [Local_CpuIdx]), One) + Local_Uid =DerefOf (CNEW [Local_CpuIdx]) + CTFY (Local_Uid, One) + \_SB.PCI0.PRES.CSEL = Local_Uid \_SB.PCI0.PRES.CINS = One Local_CpuIdx++ } Release (\_SB.PCI0.PRES.CPLK) }With this change, the
Quoted 7 lines
virsh setvcpus DOMAIN 8 --livecommand works for me. The topology in my test domain has CPU#0 and CPU#2 cold-plugged, so the command adds 6 VCPUs. Viewed from the firmware side, the 6 "
device_add" commands, issued in close succession by libvirtd, coalesce into 4 "batches". (And of course the firmware sees the 4 batches back-to-back.)unfortunately, with more testing, I have run into two more races:
(1) When a "
device_add" occurs after the ACPI loop collects the CPUS from the register block, but before the SMI.Here, the "stray CPU" is processed fine by the firmware. However, the CTFY loop in ACPI does not know about the CPU, so it doesn't clear the pending insert event for it. And when the firmware is entered with an SMI for the *next* time, the firmware sees the same CPU *again* as pending, and tries to relocate it again. Bad things happen.
(2) When a "
device_add" occurs after the SMI, but before the firmware collects the pending CPUs from the register block.Here, the firmware collects the "stray CPU". However, the "broadcast SMI", with which we entered the firmware, did *not* cover the stray CPU -- the
CPU_FOREACH()loop inich9_apm_ctrl_changed()could not make the SMI pending for the new CPU, because at that time, the CPU had not been added yet. As a result, when the firmware sends an INIT-SIPI-SIPI to the new CPU, expecting it to boot right into SMM, the new CPU instead boots straight into the post-RSM (normal mode) "pen", skipping its initial SMI handler. Meaning that the CPU halts nicely, but its SMBASE is never relocated, and the SMRAM message exchange with the BSP falls apart.Possible mitigations I can think of:
For problem (1):
(1a) Change the firmware so it notices that it has relocated the
"stray" CPU before -- such CPUs should be simply skipped in the firmware. The next time the CTFY loop runs in ACPI, it will clear the pending event.(1b) Alternatively, stop consuming the hotplug register block in the
firmware altogether, and work out general message passing, from ACPI to firmware. See the outline here:http://mid.mail-archive.com/[email protected]
For problem (2):
(2a) Change the firmware so that it sends a directed SMI as well to
each CPU, just before sending an INIT-SIPI-SIPI. This should be idempotent -- if the broadcast SMI *has* covered the the CPU, then sending a directed SMI should make no difference.(2b) Alternatively, change the "
device_add" command in QEMU so that,
if "CPU hotplug with SMI" has been negotiated, the new CPU is added with the SMI made pending for it at once. (That is, no hot-plugged CPU would exist with the directed SMI *not* pending for it.)
Quoted 8 lines
Quoted 6 lines
(2c) Alternatively, approach (1b) would fix problem (2) as well -- the
firmware would only relocate such CPUs that ACPI collected before injecting the SMI. So all those CPUs would have the SMI pending.I can experiment with (1a) and (2a),
My patches for (1a) and (1b) seem to work -- my workstation has 10
aargh, I meant my patches for (1a) and (2a).
sorry
Laszlo
Quoted 13 lines
PCPUs, and I'm using a guest with 20 possible VCPUs and 2 cold-plugged VCPUs on it, for testing. The patches survive the hot-plugging of 18 VCPUs in one go, or two batches like 9+9. I can see the fixes being exercised.
Unless you strongly disagree (or I find issues in further testing), I propose that I post these fixes to edk2-devel (they should still be in scope for the upcoming release), and that we stick with your current patch series for QEMU (v3 -- upcoming, or maybe already posted).
Thanks!
Laszlo
Re: [PATCH v2 6/7] x68: acpi: trigger SMI before sending hotplug Notify event to OSPM
In reply to Laszlo ErsekQuoted 129 lines · On Wed, 26 Aug 2020 15:32:07 +0200 Laszlo Ersek <[email protected]> wrote:
Quoted 115 lines · Laszlo Ersek
Hi Igor,
Quoted 49 lines · Laszlo Ersek
So I would suggest fetching the CNEW array element back into "uid" first, then using "uid" for both the NOTIFY call, and the (currently missing) restoration of CSEL. Then we can write 1 to CINS.
Expressed as a patch on top of yours:
Quoted 8 lines
hw/acpi/cpu.c +0
-0@@ -564,8 +564,11 @@ void build_cpus_aml(Aml *table, MachineState *machine, CPUHotplugFeatures opts,aml_append (method,aml_store (zero, cpu_idx)); while_ctx =aml_while (aml_lless (cpu_idx, num_added_cpus)); {hw/acpi/cpu.c void build_cpus_aml(Aml *table, MachineState *machine, CPUHotplugFeatures opts, · line 574
Quoted 10 lines
hw/acpi/cpu.c +5
-2-aml_append (while_ctx,aml_call2 (CPU_NOTIFY_METHOD , -aml_derefof (aml_index (new_cpus, cpu_idx)), dev_chk)); +aml_append (while_ctx, +aml_store (aml_derefof (aml_index (new_cpus, cpu_idx)), uid)); +aml_append (while_ctx, +aml_call2 (CPU_NOTIFY_METHOD , uid, dev_chk)); +aml_append (while_ctx,aml_store (uid, cpu_selector));aml_append (while_ctx,aml_store (one, ins_evt));aml_append (while_ctx,aml_increment (cpu_idx)); }This effects the following change, in the decompiled method:
Quoted 9 lines
hw/acpi/cpu.c +0
-0@@ -37,15 +37,17 @@If ((Local_NumAddedCpus != Zero)) { \_SB.PCI0.SMI0.SMIC = 0x04 } Local_CpuIdx = Zero While ((Local_CpuIdx < Local_NumAddedCpus)) {hw/acpi/cpu.c line 53
Quoted 10 lines
hw/acpi/cpu.c +3
-1-CTFY (DerefOf (CNEW [Local_CpuIdx]), One) + Local_Uid =DerefOf (CNEW [Local_CpuIdx]) + CTFY (Local_Uid, One) + \_SB.PCI0.PRES.CSEL = Local_Uid \_SB.PCI0.PRES.CINS = One Local_CpuIdx++ } Release (\_SB.PCI0.PRES.CPLK) }With this change, the
Quoted 7 lines
virsh setvcpus DOMAIN 8 --livecommand works for me. The topology in my test domain has CPU#0 and CPU#2 cold-plugged, so the command adds 6 VCPUs. Viewed from the firmware side, the 6 "
device_add" commands, issued in close succession by libvirtd, coalesce into 4 "batches". (And of course the firmware sees the 4 batches back-to-back.)unfortunately, with more testing, I have run into two more races:
(1) When a "
device_add" occurs after the ACPI loop collects the CPUS from the register block, but before the SMI.Here, the "stray CPU" is processed fine by the firmware. However, the CTFY loop in ACPI does not know about the CPU, so it doesn't clear the pending insert event for it. And when the firmware is entered with an SMI for the *next* time, the firmware sees the same CPU *again* as pending, and tries to relocate it again. Bad things happen.
(2) When a "
device_add" occurs after the SMI, but before the firmware collects the pending CPUs from the register block.Here, the firmware collects the "stray CPU". However, the "broadcast SMI", with which we entered the firmware, did *not* cover the stray CPU -- the
CPU_FOREACH()loop inich9_apm_ctrl_changed()could not make the SMI pending for the new CPU, because at that time, the CPU had not been added yet. As a result, when the firmware sends an INIT-SIPI-SIPI to the new CPU, expecting it to boot right into SMM, the new CPU instead boots straight into the post-RSM (normal mode) "pen", skipping its initial SMI handler. Meaning that the CPU halts nicely, but its SMBASE is never relocated, and the SMRAM message exchange with the BSP falls apart.Possible mitigations I can think of:
For problem (1):
(1a) Change the firmware so it notices that it has relocated the
"stray" CPU before -- such CPUs should be simply skipped in the firmware. The next time the CTFY loop runs in ACPI, it will clear the pending event.(1b) Alternatively, stop consuming the hotplug register block in the
firmware altogether, and work out general message passing, from ACPI to firmware. See the outline here:http://mid.mail-archive.com/[email protected]
For problem (2):
(2a) Change the firmware so that it sends a directed SMI as well to
each CPU, just before sending an INIT-SIPI-SIPI. This should be idempotent -- if the broadcast SMI *has* covered the the CPU, then sending a directed SMI should make no difference.(2b) Alternatively, change the "
device_add" command in QEMU so that,
if "CPU hotplug with SMI" has been negotiated, the new CPU is added with the SMI made pending for it at once. (That is, no hot-plugged CPU would exist with the directed SMI *not* pending for it.)Quoted 6 lines
(2c) Alternatively, approach (1b) would fix problem (2) as well -- the
firmware would only relocate such CPUs that ACPI collected before injecting the SMI. So all those CPUs would have the SMI pending.I can experiment with (1a) and (2a),
My patches for (1a) and (1b) seem to work -- my workstation has 10 PCPUs, and I'm using a guest with 20 possible VCPUs and 2 cold-plugged VCPUs on it, for testing. The patches survive the hot-plugging of 18 VCPUs in one go, or two batches like 9+9. I can see the fixes being exercised.
Quoted 4 lines
Unless you strongly disagree (or I find issues in further testing), I propose that I post these fixes to edk2-devel (they should still be in scope for the upcoming release), and that we stick with your current patch series for QEMU (v3 -- upcoming, or maybe already posted).
Lets do as you suggest.
As for QEMU side, I'll try to post next revision next week.
Quoted 5 lines
Thanks!
Laszlo
PATCH v2 7/7 tests: acpi: update acpi blobs with new AML
In reply to Igor MammedovUpdate CPU hotplug AML with following changes
Method (CSCN, 0, Serialized)
{
Acquire (\_SB.PCI0.PRES.CPLK, 0xFFFF)
+ Name (CNEW, Package (0x01){})
+ Local1 = Zero
Local0 = One
- While ((Local0 == One))
+ Local3 = Zero
+ While (((Local0 == One) && (Local3 < One)))
{
Local0 = Zero
+ \_SB.PCI0.PRES.CSEL = Local3
\_SB.PCI0.PRES.CCMD = Zero+ If ((\_SB.PCI0.PRES.CDAT < Local3))
+ {
+ Break
+ }
+
+ Local3 = \_SB.PCI0.PRES.CDAT
If ((\_SB.PCI0.PRES.CINS == One))
{
- CTFY (\_SB.PCI0.PRES.CDAT, One)
- \_SB.PCI0.PRES.CINS = One
+ CNEW [Local1] = Local3
+ Local1++
Local0 = One
}
ElseIf ((\_SB.PCI0.PRES.CRMV == One))
{
- CTFY (\_SB.PCI0.PRES.CDAT, 0x03)
+ CTFY (Local3, 0x03)
\_SB.PCI0.PRES.CRMV = One
Local0 = One
}+
+ Local3++
+ }
+
+ Local2 = Zero
+ While ((Local2 < Local1))
+ {
+ CTFY (DerefOf (CNEW [Local2]), One)
+ \_SB.PCI0.PRES.CINS = One
+ Local2++
}--- tests/qtest/bios-tables-test-allowed-diff.h | 19 ------------------- tests/data/acpi/pc/DSDT | Bin 4934 -> 5009 bytes tests/data/acpi/pc/DSDT.acpihmat | Bin 6258 -> 6334 bytes tests/data/acpi/pc/DSDT.bridge | Bin 6793 -> 6868 bytes tests/data/acpi/pc/DSDT.cphp | Bin 5397 -> 5473 bytes tests/data/acpi/pc/DSDT.dimmpxm | Bin 6587 -> 6663 bytes tests/data/acpi/pc/DSDT.ipmikcs | Bin 5006 -> 5081 bytes tests/data/acpi/pc/DSDT.memhp | Bin 6293 -> 6368 bytes tests/data/acpi/pc/DSDT.numamem | Bin 4940 -> 5015 bytes tests/data/acpi/q35/DSDT | Bin 7678 -> 7753 bytes tests/data/acpi/q35/DSDT.acpihmat | Bin 9002 -> 9078 bytes tests/data/acpi/q35/DSDT.bridge | Bin 7695 -> 7770 bytes tests/data/acpi/q35/DSDT.cphp | Bin 8141 -> 8217 bytes tests/data/acpi/q35/DSDT.dimmpxm | Bin 9331 -> 9407 bytes tests/data/acpi/q35/DSDT.ipmibt | Bin 7753 -> 7828 bytes tests/data/acpi/q35/DSDT.memhp | Bin 9037 -> 9112 bytes tests/data/acpi/q35/DSDT.mmio64 | Bin 8808 -> 8883 bytes tests/data/acpi/q35/DSDT.numamem | Bin 7684 -> 7759 bytes tests/data/acpi/q35/DSDT.tis | Bin 8283 -> 8358 bytes 19 files changed, 19 deletions(-)
tests/qtest/bios-tables-test-allowed-diff.h +0 -19
@@ -1,20 +1 @@/* List of comma-separated changed AML files to ignore */ -"tests/data/acpi/pc/DSDT" , -"tests/data/acpi/q35/DSDT" , -"tests/data/acpi/q35/DSDT.tis" , -"tests/data/acpi/q35/DSDT.bridge" , -"tests/data/acpi/q35/DSDT.mmio64" , -"tests/data/acpi/q35/DSDT.ipmibt" , -"tests/data/acpi/q35/DSDT.cphp" , -"tests/data/acpi/q35/DSDT.memhp" , -"tests/data/acpi/q35/DSDT.numamem" , -"tests/data/acpi/q35/DSDT.dimmpxm" , -"tests/data/acpi/q35/DSDT.acpihmat" , -"tests/data/acpi/pc/DSDT.bridge" , -"tests/data/acpi/pc/DSDT.ipmikcs" , -"tests/data/acpi/pc/DSDT.cphp" , -"tests/data/acpi/pc/DSDT.memhp" , -"tests/data/acpi/pc/DSDT.numamem" , -"tests/data/acpi/pc/DSDT.dimmpxm" , -"tests/data/acpi/pc/DSDT.acpihmat" , -"tests/data/acpi/pc/DSDT.acpihmat",
tests/data/acpi/pc/DSDT binary +0 -0
tests/data/acpi/pc/DSDT.acpihmat binary +0 -0
tests/data/acpi/pc/DSDT.bridge binary +0 -0
tests/data/acpi/pc/DSDT.cphp binary +0 -0
tests/data/acpi/pc/DSDT.dimmpxm binary +0 -0
tests/data/acpi/pc/DSDT.ipmikcs binary +0 -0
tests/data/acpi/pc/DSDT.memhp binary +0 -0
tests/data/acpi/pc/DSDT.numamem binary +0 -0
tests/data/acpi/q35/DSDT binary +0 -0
tests/data/acpi/q35/DSDT.acpihmat binary +0 -0
tests/data/acpi/q35/DSDT.bridge binary +0 -0
tests/data/acpi/q35/DSDT.cphp binary +0 -0
tests/data/acpi/q35/DSDT.dimmpxm binary +0 -0
tests/data/acpi/q35/DSDT.ipmibt binary +0 -0
tests/data/acpi/q35/DSDT.memhp binary +0 -0
tests/data/acpi/q35/DSDT.mmio64 binary +0 -0
tests/data/acpi/q35/DSDT.numamem binary +0 -0
tests/data/acpi/q35/DSDT.tis binary +0 -0
Signature · 1 line
2.26.2
Patchew URL: https://patchew.org/QEMU/[email protected]/
Patchew URL: https://patchew.org/QEMU/[email protected]/
Hi,
This series failed the docker-quick@centos7 build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
make docker-image-centos7 V=1 NETWORK=1
time make docker-test-quick@centos7 SHOW_ENV=1 J=14 NETWORK=1 === TEST SCRIPT END ===
TEST check-unit: tests/test-char
Unexpected error in object_property_try_add() at /tmp/qemu-test/src/qom/object.c:1181:
attempt to add duplicate property 'serial-id' to object (type 'container')
ERROR test-char - too few tests run (expected 38, got 9)
make: *** [check-unit] Error 1
make: *** Waiting for unfinished jobs....
TEST iotest-qcow2: 024
TEST iotest-qcow2: 025
---
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['sudo', '-n', 'docker', 'run', '--label', 'com.qemu.instance.uuid=f2b52e779ea044a6af8347ae49d4785e', '-u', '1001', '--security-opt', 'seccomp=unconfined', '--rm', '-e', 'TARGET_LIST=', '-e', 'EXTRA_CONFIGURE_OPTS=', '-e', 'V=', '-e', 'J=14', '-e', 'DEBUG=', '-e', 'SHOW_ENV=1', '-e', 'CCACHE_DIR=/var/tmp/ccache', '-v', '/home/patchew/.cache/qemu-docker-ccache:/var/tmp/ccache:z', '-v', '/var/tmp/patchew-tester-tmp-e651x4a8/src/docker-src.2020-08-18-08.43.04.23321:/var/tmp/qemu:z,ro', 'qemu/centos7', '/var/tmp/qemu/run', 'test-quick']' returned non-zero exit status 2. filter=--filter=label=com.qemu.instance.uuid=f2b52e779ea044a6af8347ae49d4785e
make[1]: *** [docker-run] Error 1
make[1]: Leaving directory `/var/tmp/patchew-tester-tmp-e651x4a8/src'
make: *** [docker-run-test-quick@centos7] Error 2
real 13m7.140s
user 0m9.328s
The full log is available at
http://patchew.org/logs/[email protected]/testing.docker-quick@centos7/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to [email protected]
Quoted 16 lines · On 8/18/20 2:56 PM, [email protected] wrote:
Patchew URL: https://patchew.org/QEMU/[email protected]/
Hi,
This series failed the docker-quick@centos7 build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
make docker-image-centos7 V=1 NETWORK=1
time make docker-test-quick@centos7 SHOW_ENV=1 J=14 NETWORK=1 === TEST SCRIPT END ===
Quoted 3 lines
TEST check-unit: tests/test-char
Unexpected error inobject_property_try_add()at/tmp/qemu-test/src/qom/object.c:1181:
attempt to add duplicate property 'serial-id' to object (type 'container')
Unrelated error.
Quoted 23 lines
ERROR test-char - too few tests run (expected 38, got 9)
make: *** [check-unit] Error 1
make: *** Waiting for unfinished jobs....
TEST iotest-qcow2: 024
TEST iotest-qcow2: 025
---
raiseCalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['sudo', '-n', 'docker', 'run', '--label', 'com.qemu.instance.uuid=f2b52e779ea044a6af8347ae49d4785e', '-u', '1001', '--security-opt', 'seccomp=unconfined', '--rm', '-e', 'TARGET_LIST=', '-e', 'EXTRA_CONFIGURE_OPTS=', '-e', 'V=', '-e', 'J=14', '-e', 'DEBUG=', '-e', 'SHOW_ENV=1', '-e', 'CCACHE_DIR=/var/tmp/ccache', '-v', '/home/patchew/.cache/qemu-docker-ccache:/var/tmp/ccache:z', '-v', '/var/tmp/patchew-tester-tmp-e651x4a8/src/docker-src.2020-08-18-08.43.04.23321:/var/tmp/qemu:z,ro', 'qemu/centos7', '/var/tmp/qemu/run', 'test-quick']' returned non-zero exit status 2. filter=--filter=label=com.qemu.instance.uuid=f2b52e779ea044a6af8347ae49d4785e
make[1]: *** [docker-run] Error 1
make[1]: Leaving directory `/var/tmp/patchew-tester-tmp-e651x4a8/src'
make: *** [docker-run-test-quick@centos7] Error 2real 13m7.140s
user 0m9.328sThe full log is available at
http://patchew.org/logs/[email protected]/testing.docker-quick@centos7/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to [email protected]
Patchew URL: https://patchew.org/QEMU/[email protected]/
Patchew URL: https://patchew.org/QEMU/[email protected]/
Hi,
This series failed the docker-quick@centos7 build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
make docker-image-centos7 V=1 NETWORK=1
time make docker-test-quick@centos7 SHOW_ENV=1 J=14 NETWORK=1 === TEST SCRIPT END ===
TEST check-unit: tests/test-char
Unexpected error in object_property_try_add() at /tmp/qemu-test/src/qom/object.c:1181:
attempt to add duplicate property 'serial-id' to object (type 'container')
ERROR test-char - too few tests run (expected 38, got 9)
make: *** [check-unit] Error 1
make: *** Waiting for unfinished jobs....
TEST check-qtest-x86_64: tests/qtest/hd-geo-test
qemu-system-aarch64: -accel kvm: invalid accelerator kvm
---
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['sudo', '-n', 'docker', 'run', '--label', 'com.qemu.instance.uuid=0c3122d22095423b9f3e2db213296b3e', '-u', '1001', '--security-opt', 'seccomp=unconfined', '--rm', '-e', 'TARGET_LIST=', '-e', 'EXTRA_CONFIGURE_OPTS=', '-e', 'V=', '-e', 'J=14', '-e', 'DEBUG=', '-e', 'SHOW_ENV=1', '-e', 'CCACHE_DIR=/var/tmp/ccache', '-v', '/home/patchew/.cache/qemu-docker-ccache:/var/tmp/ccache:z', '-v', '/var/tmp/patchew-tester-tmp-4deda8a6/src/docker-src.2020-08-18-09.26.35.1749:/var/tmp/qemu:z,ro', 'qemu/centos7', '/var/tmp/qemu/run', 'test-quick']' returned non-zero exit status 2. filter=--filter=label=com.qemu.instance.uuid=0c3122d22095423b9f3e2db213296b3e
make[1]: *** [docker-run] Error 1
make[1]: Leaving directory `/var/tmp/patchew-tester-tmp-4deda8a6/src'
make: *** [docker-run-test-quick@centos7] Error 2
real 13m18.695s
user 0m8.887s
The full log is available at
http://patchew.org/logs/[email protected]/testing.docker-quick@centos7/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to [email protected]
Quoted 16 lines · On 8/18/20 3:39 PM, [email protected] wrote:
Patchew URL: https://patchew.org/QEMU/[email protected]/
Hi,
This series failed the docker-quick@centos7 build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
make docker-image-centos7 V=1 NETWORK=1
time make docker-test-quick@centos7 SHOW_ENV=1 J=14 NETWORK=1 === TEST SCRIPT END ===
Quoted 3 lines
TEST check-unit: tests/test-char
Unexpected error inobject_property_try_add()at/tmp/qemu-test/src/qom/object.c:1181:
attempt to add duplicate property 'serial-id' to object (type 'container')
Unrelated issue.
Quoted 23 lines
ERROR test-char - too few tests run (expected 38, got 9)
make: *** [check-unit] Error 1
make: *** Waiting for unfinished jobs....
TEST check-qtest-x86_64: tests/qtest/hd-geo-test
qemu-system-aarch64: -accel kvm: invalid accelerator kvm
---
raiseCalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['sudo', '-n', 'docker', 'run', '--label', 'com.qemu.instance.uuid=0c3122d22095423b9f3e2db213296b3e', '-u', '1001', '--security-opt', 'seccomp=unconfined', '--rm', '-e', 'TARGET_LIST=', '-e', 'EXTRA_CONFIGURE_OPTS=', '-e', 'V=', '-e', 'J=14', '-e', 'DEBUG=', '-e', 'SHOW_ENV=1', '-e', 'CCACHE_DIR=/var/tmp/ccache', '-v', '/home/patchew/.cache/qemu-docker-ccache:/var/tmp/ccache:z', '-v', '/var/tmp/patchew-tester-tmp-4deda8a6/src/docker-src.2020-08-18-09.26.35.1749:/var/tmp/qemu:z,ro', 'qemu/centos7', '/var/tmp/qemu/run', 'test-quick']' returned non-zero exit status 2. filter=--filter=label=com.qemu.instance.uuid=0c3122d22095423b9f3e2db213296b3e
make[1]: *** [docker-run] Error 1
make[1]: Leaving directory `/var/tmp/patchew-tester-tmp-4deda8a6/src'
make: *** [docker-run-test-quick@centos7] Error 2real 13m18.695s
user 0m8.887sThe full log is available at
http://patchew.org/logs/[email protected]/testing.docker-quick@centos7/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to [email protected]