hw/acpi: bump MADT to revision 5
v2 cover hw/acpi: bump MADT to revision 5
The following Linux kernel change broke CPU hotplug for MADT revision less than 5.
e2869bd7af60 ("x86/acpi/boot: Do not register processors that cannot be onlined for x2APIC")
Discussion on this topic can be located here:
https://lore.kernel.org/linux-acpi/[email protected]/T/#t
which resulted in the following fixes Linux in 6.3-rc5:
a74fabfbd1b7: ("x86/ACPI/boot: Use FADT version to check support for online capable")
fed8d8773b8e: ("x86/acpi/boot: Correct acpi_is_processor_usable() check")
However, as part of the investigation into resolving this breakage, I learned that i386 QEMU reports revision 1, while technically it generates revision 3. Aarch64 generates and reports revision 4.
ACPI 6.3 bumps MADT revision to 5 as it introduces an Online Capable flag that the above Linux patch utilizes to denote hot pluggable CPUs.
So in order to bump MADT to the current revision of 5, need to validate that all MADT table changes between 1 and 5 are present in QEMU.
Below is a table summarizing the changes to the MADT. This information gleamed from the ACPI specs on uefi.org.
ACPI MADT What
Version Version
1.0 MADT not present 2.0 1 Section 5.2.10.4 3.0 2 Section 5.2.11.4
5.2.11.13 Local SAPIC Structure added two new fields:
ACPI Processor UID Value
ACPI Processor UID String
5.2.10.14 Platform Interrupt Sources Structure:
Reserved changed to Platform Interrupt Sources Flags
3.0b 2 Section 5.2.11.4
Added a section describing guidelines for the ordering of processors in the MADT to support proper boot processor and multi-threaded logical processor operation.
4.0 3 Section 5.2.12
Adds Processor Local x2APIC structure type 9 Adds Local x2APIC NMI structure type 0xA
5.0 3 Section 5.2.12
6.0 3 Section 5.2.12
6.0a 4 Section 5.2.12
Adds ARM GIC structure types 0xB-0xF
6.2a 45 Section 5.2.12 <--- version 45, is indeed accurate!
6.2b 5 Section 5.2.12 GIC ITS last Reserved offset changed to 16 from 20 (typo)
6.3 5 Section 5.2.12
Adds Local APIC Flags Online Capable!
Adds GICC SPE Overflow Interrupt field
6.4 5 Section 5.2.12
Adds Multiprocessor Wakeup Structure type 0x10 (change notes says structure previously misplaced?)
6.5 5 Section 5.2.12
For the MADT revision change 1 -> 2, the spec has a change to the SAPIC structure. In general, QEMU does not generate/support SAPIC. So the QEMU i386 MADT revision can safely be moved to 2.
For the MADT revision change 2 -> 3, the spec adds Local x2APIC structures. QEMU has long supported x2apic ACPI structures. A simple search of x2apic within QEMU source and hw/i386/acpi-common.c specifically reveals this. So the QEMU i386 MADT revision can safely be moved to 3.
For the MADT revision change 3 -> 4, the spec adds support for the ARM GIC structures. QEMU ARM does in fact generate and report revision 4. As these will not be used by i386 QEMU, so then the QEMU i386 MADT revision can safely be moved to 4 as well.
Now for the MADT revision change 4 -> 5, the spec adds the Online Capable flag to the Local APIC structure, and the ARM GICC SPE Overflow Interrupt field.
For the ARM SPE, an existing 3-byte Reserved field is broken into a 1- byte Reserved field and a 2-byte SPE field. The spec says that is SPE Overflow is not supported, it should be zero.
For the i386 Local APIC flag Online Capable, the spec has certain rules about this value. And in particuar setting this value now explicitly indicates a hotpluggable CPU.
So this patch makes the needed changes to move both i386 MADT to revision 5.
Without these changes, the information below shows "how" CPU hotplug breaks with the current upstream Linux kernel 6.3. For example, a Linux guest started with:
qemu-system-x86_64 -smp 30,maxcpus=32 ...
and then attempting to hotplug a CPU:
(QEMU) device_add id=cpu30 driver=host-x86_64-cpu socket-id=0 core-id=30 thread-id=0
fails with the following:
APIC: NR_CPUS/possible_cpus limit of 30 reached. Processor 30/0x.
ACPI: Unable to map lapic to logical cpu number
acpi LNXCPU:1e: Enumeration failure
# dmesg | grep smpboot smpboot: Allowing 30 CPUs, 0 hotplug CPUs smpboot: CPU0: Intel(R) Xeon(R) CPU D-1533 @ 2.10GHz (family: 0x) smpboot: Max logical packages: 1 smpboot: Total of 30 processors activated (125708.76 BogoMIPS)
# iasl -d /sys/firmware/tables/acpi/APIC [000h 0000 4] Signature : "APIC" [Multiple APIC Descript [004h 0004 4] Table Length : 00000170 [008h 0008 1] Revision : 01 <===== [009h 0009 1] Checksum : 9C [00Ah 0010 6] Oem ID : "BOCHS " [010h 0016 8] Oem Table ID : "BXPC " [018h 0024 4] Oem Revision : 00000001 [01Ch 0028 4] Asl Compiler ID : "BXPC" [020h 0032 4] Asl Compiler Revision : 00000001
...
[114h 0276 1] Subtable Type : 00 [Processor Local APIC]
[115h 0277 1] Length : 08
[116h 0278 1] Processor ID : 1D
[117h 0279 1] Local Apic ID : 1D
[118h 0280 4] Flags (decoded below) : 00000001
Processor Enabled : 1 <===== [11Ch 0284 1] Subtable Type : 00 [Processor Local APIC]
[11Dh 0285 1] Length : 08
[11Eh 0286 1] Processor ID : 1E
[11Fh 0287 1] Local Apic ID : 1E
[120h 0288 4] Flags (decoded below) : 00000000
Processor Enabled : 0 <===== [124h 0292 1] Subtable Type : 00 [Processor Local APIC]
[125h 0293 1] Length : 08
[126h 0294 1] Processor ID : 1F
[127h 0295 1] Local Apic ID : 1F
[128h 0296 4] Flags (decoded below) : 00000000
Processor Enabled : 0 <=====The (latest upstream) Linux kernel sees 30 Enabled processors, and does not consider processors 31 and 32 to be hotpluggable.
With this patch series applied, by bumping MADT to revision 5, the latest upstream Linux kernel correctly identifies 30 CPUs plus 2 hotpluggable CPUS.
CPU30 has been hot-added
smpboot: Booting Node 0 Processor 30 APIC 0x1e
Will online and init hotplugged CPU: 30
# dmesg | grep smpboot smpboot: Allowing 32 CPUs, 2 hotplug CPUs smpboot: CPU0: Intel(R) Xeon(R) CPU D-1533 @ 2.10GHz (family: 0x6, model: 0x56, stepping: 0x3) smpboot: Max logical packages: 2 smpboot: Total of 30 processors activated (125708.76 BogoMIPS)
# iasl -d /sys/firmware/tables/acpi/APIC [000h 0000 004h] Signature : "APIC" [Multiple APIC Descript [004h 0004 004h] Table Length : 00000170 [008h 0008 001h] Revision : 05 <===== [009h 0009 001h] Checksum : 94 [00Ah 0010 006h] Oem ID : "BOCHS " [010h 0016 008h] Oem Table ID : "BXPC " [018h 0024 004h] Oem Revision : 00000001 [01Ch 0028 004h] Asl Compiler ID : "BXPC" [020h 0032 004h] Asl Compiler Revision : 00000001
...
[114h 0276 001h] Subtable Type : 00 [Processor Local APIC]
[115h 0277 001h] Length : 08
[116h 0278 001h] Processor ID : 1D
[117h 0279 001h] Local Apic ID : 1D
[118h 0280 004h] Flags (decoded below) : 00000001
Processor Enabled : 1 <=====
Runtime Online Capable : 0 <===== [11Ch 0284 001h] Subtable Type : 00 [Processor Local APIC]
[11Dh 0285 001h] Length : 08
[11Eh 0286 001h] Processor ID : 1E
[11Fh 0287 001h] Local Apic ID : 1E
[120h 0288 004h] Flags (decoded below) : 00000002
Processor Enabled : 0 <=====
Runtime Online Capable : 1 <===== [124h 0292 001h] Subtable Type : 00 [Processor Local APIC]
[125h 0293 001h] Length : 08
[126h 0294 001h] Processor ID : 1F
[127h 0295 001h] Local Apic ID : 1F
[128h 0296 004h] Flags (decoded below) : 00000002
Processor Enabled : 0 <=====
Runtime Online Capable : 1 <=====In terms of testing older operating systems, I did:
- Windows Server 2008.
By opening Device Manager -> Processors, and watching/counting the listed CPUs before and after hot un/plug operations. When hot plugging a CPU, the new processor shows in the list; one more processor is available after the hotplug. When hot unplugging a CPU, Windows refuses, with the message:
The 'Intel(R) Xeon(R) CPU D-1533 @ 2.10GHz' device is not removable and cannot be ejected or unplugged.
This is expected as hot unplug did not work in Windows 2008.
- RHEL 6.9
Kernel 2.6.32-696.el6.x86_64
Build Feb 21 2017
From dmesg:
ACPI: APIC 000000007ffe32f0 000F0 (v05 BOCHS BXPC 00000001 BXPC 00000001)
SMP: Allowing 16 CPUs, 8 hotplug CPUs
# cat /sys/devices/system/cpu/online 0-7
(QEMU) device_add id=cpu8 driver=host-x86_64-cpu socket-id=0 core-id=8 thread-id=0
CPU 8 got hotplugged
Booting Node 0 Processor 8 APIC 0x8
kvm-clock: cpu 8, msr 2830ed00
Will online and init hotplugged CPU: 8
microcode: CPU8 sig=0x50663, pf=0x1, revision=0x700001c platform microcode: firmware: requesting intel-ucode/06-56-03
# cat /sys/devices/system/cpu/online 0-8
(QEMU) device_del id=cpu8
Broke affinity for irq 24
CPU 8 is now offline
# cat /sys/devices/system/cpu/online 0-7
RHEL 6.9
kernel 2.6.32-696.el6.x86_64
build Feb 21 2017
Both of the above 'legacy' operating systems behaved as expected.
Regards,
Eric
---
v2: 18apr2023
- Code formatting changes per Igor Mammedov
- Included the steps in bios-tables-test.
v1: 28mar2023
https://lists.gnu.org/archive/html/qemu-devel/2023-03/msg06705.html
- Initial series for ARM and i386 MADT revision bump to 5.
Eric DeVolder (4):
ACPI: bios-tables-test.c step 2 (allowed-diff entries) hw/acpi: arm: bump MADT to revision 5
hw/acpi: i386: bump MADT to revision 5
ACPI: bios-tables-test.c step 5 (updated expected table binaries)
hw/arm/virt-acpi-build.c | 6 ++++-- hw/i386/acpi-common.c | 13 ++++++++++--- tests/data/acpi/microvm/APIC | Bin 70 -> 70 bytes tests/data/acpi/microvm/APIC.ioapic2 | Bin 82 -> 82 bytes tests/data/acpi/microvm/APIC.pcie | Bin 110 -> 110 bytes tests/data/acpi/pc/APIC | Bin 120 -> 120 bytes tests/data/acpi/pc/APIC.acpihmat | Bin 128 -> 128 bytes tests/data/acpi/pc/APIC.cphp | Bin 160 -> 160 bytes tests/data/acpi/pc/APIC.dimmpxm | Bin 144 -> 144 bytes tests/data/acpi/q35/APIC | Bin 120 -> 120 bytes tests/data/acpi/q35/APIC.acpihmat | Bin 128 -> 128 bytes tests/data/acpi/q35/APIC.acpihmat-noinitiator | Bin 144 -> 144 bytes tests/data/acpi/q35/APIC.core-count2 | Bin 2478 -> 2478 bytes tests/data/acpi/q35/APIC.cphp | Bin 160 -> 160 bytes tests/data/acpi/q35/APIC.dimmpxm | Bin 144 -> 144 bytes tests/data/acpi/q35/APIC.xapic | Bin 2686 -> 2686 bytes tests/data/acpi/virt/APIC | Bin 172 -> 172 bytes tests/data/acpi/virt/APIC.acpihmatvirt | Bin 412 -> 412 bytes tests/data/acpi/virt/APIC.topology | Bin 732 -> 732 bytes 19 files changed, 14 insertions(+), 5 deletions(-)
Signature · 1 line
2.31.1
PATCH v2 1/4 ACPI: bios-tables-test.c step 2 (allowed-diff entries)
Following the guidelines in tests/qtest/bios-tables-test.c, this change sets-up bios-tables-test-allowed-diff.h to exclude the imminent changes to the APIC tables, per step 2.
--- tests/qtest/bios-tables-test-allowed-diff.h | 4 ++++ 1 file changed, 4 insertions(+)
tests/qtest/bios-tables-test-allowed-diff.h +4 -0
@@ -1 +1,5 @@/* List of comma-separated changed AML files to ignore */ +"tests/data/acpi/pc/APIC" , +"tests/data/acpi/q35/APIC" , +"tests/data/acpi/microvm/APIC" , +"tests/data/acpi/virt/APIC",
Signature · 1 line
2.31.1
PATCH v2 2/4 hw/acpi: arm: bump MADT to revision 5
In reply to Eric DeVolderCurrently ARM QEMU generates, and reports, MADT revision 4. ACPI 6.3 introduces MADT revision 5.
For MADT revision 5, the GICC structure adds an SPE Overflow Interrupt field. This new 2-byte field is created from the existing 3-byte Reserved field. The spec indicates if the SPE overflow interrupt is not supported, to zero the field.
--- hw/arm/virt-acpi-build.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
hw/arm/virt-acpi-build.c +4 -2
@@ -705,7 +705,7 @@ build_madt(GArray *table_data, BIOSLinker *linker, VirtMachineState *vms)int i;VirtMachineClass *vmc =VIRT_MACHINE_GET_CLASS (vms);const MemMapEntry *memmap = vms->memmap; -AcpiTable table = { .sig ="APIC" , .rev =4 , .oem_id = vms->oem_id, +AcpiTable table = { .sig ="APIC" , .rev =5 , .oem_id = vms->oem_id, .oem_table_id = vms->oem_table_id };acpi_table_begin (&table, table_data);
@@ -763,7 +763,9 @@ build_madt(GArray *table_data, BIOSLinker *linker, VirtMachineState *vms)/* Processor Power Efficiency Class */ build_append_int_noprefix (table_data,0 ,1 );/* Reserved */ -build_append_int_noprefix (table_data,0 ,3 ); +build_append_int_noprefix (table_data,0 ,1 ); +/* SPE overflow Interrupt */ +build_append_int_noprefix (table_data,0 ,2 ); }if (vms->gic_version !=VIRT_GIC_VERSION_2 ) {
Signature · 1 line
2.31.1
Re: [PATCH v2 2/4] hw/acpi: arm: bump MADT to revision 5
Quoted 9 lines · Eric DeVolder
Currently ARM QEMU generates, and reports, MADT revision 4. ACPI 6.3 introduces MADT revision 5.
For MADT revision 5, the GICC structure adds an SPE Overflow Interrupt field. This new 2-byte field is created from the existing 3-byte Reserved field. The spec indicates if the SPE overflow interrupt is not supported, to zero the field.
Signed-off-by Eric DeVolder <[email protected]>
So why do we bother changing this? I'd rather defer until we actually intend to fill this field.
Quoted 30 lines
--- hw/arm/virt-acpi-build.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)hw/arm/virt-acpi-build.c +4
-2@@ -705,7 +705,7 @@ build_madt(GArray *table_data, BIOSLinker *linker, VirtMachineState *vms)int i;VirtMachineClass *vmc =VIRT_MACHINE_GET_CLASS (vms);const MemMapEntry *memmap = vms->memmap; -AcpiTable table = { .sig ="APIC" , .rev =4 , .oem_id = vms->oem_id, +AcpiTable table = { .sig ="APIC" , .rev =5 , .oem_id = vms->oem_id, .oem_table_id = vms->oem_table_id };acpi_table_begin (&table, table_data);@@ -763,7 +763,9 @@ build_madt(GArray *table_data, BIOSLinker *linker, VirtMachineState *vms)/* Processor Power Efficiency Class */ build_append_int_noprefix (table_data,0 ,1 );/* Reserved */ -build_append_int_noprefix (table_data,0 ,3 ); +build_append_int_noprefix (table_data,0 ,1 ); +/* SPE overflow Interrupt */ +build_append_int_noprefix (table_data,0 ,2 ); }if (vms->gic_version !=VIRT_GIC_VERSION_2 ) {Signature · 1 line
2.31.1
Re: [PATCH v2 2/4] hw/acpi: arm: bump MADT to revision 5
Quoted 9 lines · Michael S. Tsirkin
Quoted 8 lines · Eric DeVolder
Currently ARM QEMU generates, and reports, MADT revision 4. ACPI 6.3 introduces MADT revision 5.
For MADT revision 5, the GICC structure adds an SPE Overflow Interrupt field. This new 2-byte field is created from the existing 3-byte Reserved field. The spec indicates if the SPE overflow interrupt is not supported, to zero the field.
Quoted 4 lines
Quoted 1 line
Signed-off-by Eric DeVolder <[email protected]>So why do we bother changing this? I'd rather defer until we actually intend to fill this field.
Perfectly reasonable to me. I'll drop the ARM change going forward. eric
Quoted 32 lines
Quoted 31 lines
--- hw/arm/virt-acpi-build.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)hw/arm/virt-acpi-build.c +4
-2@@ -705,7 +705,7 @@ build_madt(GArray *table_data, BIOSLinker *linker, VirtMachineState *vms)int i;VirtMachineClass *vmc =VIRT_MACHINE_GET_CLASS (vms);const MemMapEntry *memmap = vms->memmap; -AcpiTable table = { .sig ="APIC" , .rev =4 , .oem_id = vms->oem_id, +AcpiTable table = { .sig ="APIC" , .rev =5 , .oem_id = vms->oem_id, .oem_table_id = vms->oem_table_id };acpi_table_begin (&table, table_data);@@ -763,7 +763,9 @@ build_madt(GArray *table_data, BIOSLinker *linker, VirtMachineState *vms)/* Processor Power Efficiency Class */ build_append_int_noprefix (table_data,0 ,1 );/* Reserved */ -build_append_int_noprefix (table_data,0 ,3 ); +build_append_int_noprefix (table_data,0 ,1 ); +/* SPE overflow Interrupt */ +build_append_int_noprefix (table_data,0 ,2 ); }if (vms->gic_version !=VIRT_GIC_VERSION_2 ) {Signature · 1 line
2.31.1
PATCH v2 3/4 hw/acpi: i386: bump MADT to revision 5
In reply to Eric DeVolderCurrently i386 QEMU generates MADT revision 3, and reports MADT revision 1. ACPI 6.3 introduces MADT revision 5.
For MADT revision 4, that introduces ARM GIC structures, which do not apply to i386.
For MADT revision 5, the Local APIC flags introduces the Online Capable bitfield.
Making MADT generate and report revision 5 will solve problems with CPU hotplug (the Online Capable flag indicates hotpluggable CPUs).
--- hw/i386/acpi-common.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)
hw/i386/acpi-common.c +10 -3
@@ -38,8 +38,15 @@ void pc_madt_cpu_entry(int uid, const CPUArchIdList *apic_ids, {uint32_t apic_id = apic_ids->cpus[uid].arch_id;/* Flags – Local APIC Flags */ -uint32_t flags = apic_ids->cpus[uid].cpu !=NULL || force_enabled ? -1 /* Enabled */ :0 ; +bool enabled = apic_ids->cpus[uid].cpu !=NULL || force_enabled ? + true : false; +/* +* ACPI 6.3 5.2.12.2 Local APIC Flags: OnlineCapable must be 0 +* if Enabled is set. +*/ +bool onlinecapable = enabled ? false : true; +uint32_t flags = onlinecapable ?0x2 :0x0 |/* Online Capable */ + enabled ?0x1 :0x0 ;/* Enabled */ /* ACPI spec says that LAPIC entry for non present * CPU may be omitted from MADT or it must be marked
@@ -102,7 +109,7 @@ void acpi_build_madt(GArray *table_data, BIOSLinker *linker,MachineClass *mc =MACHINE_GET_CLASS (x86ms);const CPUArchIdList *apic_ids = mc->possible_cpu_arch_ids (MACHINE (x86ms));AcpiDeviceIfClass *adevc =ACPI_DEVICE_IF_GET_CLASS (adev); -AcpiTable table = { .sig ="APIC" , .rev =1 , .oem_id = oem_id, +AcpiTable table = { .sig ="APIC" , .rev =5 , .oem_id = oem_id, .oem_table_id = oem_table_id };acpi_table_begin (&table, table_data);
Signature · 1 line
2.31.1
Re: [PATCH v2 3/4] hw/acpi: i386: bump MADT to revision 5
Quoted 25 lines · Eric DeVolder
Currently i386 QEMU generates MADT revision 3, and reports MADT revision 1. ACPI 6.3 introduces MADT revision 5.
For MADT revision 4, that introduces ARM GIC structures, which do not apply to i386.
For MADT revision 5, the Local APIC flags introduces the Online Capable bitfield.
Making MADT generate and report revision 5 will solve problems with CPU hotplug (the Online Capable flag indicates hotpluggable CPUs).
Signed-off-by Eric DeVolder <[email protected]>--- hw/i386/acpi-common.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)hw/i386/acpi-common.c +0
-0@@ -38,8 +38,15 @@ void pc_madt_cpu_entry(int uid, const CPUArchIdList *apic_ids, {uint32_t apic_id = apic_ids->cpus[uid].arch_id;
hw/i386/acpi-common.c void pc_madt_cpu_entry(int uid, const CPUArchIdList *apic_ids, · line 47
Quoted 10 lines
hw/i386/acpi-common.c +7
-2/* Flags – Local APIC Flags */ -uint32_t flags = apic_ids->cpus[uid].cpu !=NULL || force_enabled ? -1 /* Enabled */ :0 ; +bool enabled = apic_ids->cpus[uid].cpu !=NULL || force_enabled ? + true : false; +/* +* ACPI 6.3 5.2.12.2 Local APIC Flags: OnlineCapable must be 0 +* if Enabled is set. +*/ +bool onlinecapable = enabled ? false : true;
Pls write this as onlinecapable = !enabled or just open-code on the next line - does not look like this variable adds a lot of value.
Quoted 16 lines
hw/i386/acpi-common.c +3
-1+uint32_t flags = onlinecapable ?0x2 :0x0 |/* Online Capable */ + enabled ?0x1 :0x0 ;/* Enabled */ /* ACPI spec says that LAPIC entry for non present * CPU may be omitted from MADT or it must be marked @@ -102,7 +109,7 @@ void acpi_build_madt(GArray *table_data, BIOSLinker *linker,MachineClass *mc =MACHINE_GET_CLASS (x86ms);const CPUArchIdList *apic_ids = mc->possible_cpu_arch_ids (MACHINE (x86ms));AcpiDeviceIfClass *adevc =ACPI_DEVICE_IF_GET_CLASS (adev); -AcpiTable table = { .sig ="APIC" , .rev =1 , .oem_id = oem_id, +AcpiTable table = { .sig ="APIC" , .rev =5 , .oem_id = oem_id, .oem_table_id = oem_table_id };acpi_table_begin (&table, table_data);Signature · 1 line
2.31.1
Re: [PATCH v2 3/4] hw/acpi: i386: bump MADT to revision 5
Quoted 31 lines · Michael S. Tsirkin
Quoted 30 lines · Eric DeVolder
Currently i386 QEMU generates MADT revision 3, and reports MADT revision 1. ACPI 6.3 introduces MADT revision 5.
For MADT revision 4, that introduces ARM GIC structures, which do not apply to i386.
For MADT revision 5, the Local APIC flags introduces the Online Capable bitfield.
Making MADT generate and report revision 5 will solve problems with CPU hotplug (the Online Capable flag indicates hotpluggable CPUs).
Signed-off-by Eric DeVolder <[email protected]>--- hw/i386/acpi-common.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)hw/i386/acpi-common.c +2
-2@@ -38,8 +38,15 @@ void pc_madt_cpu_entry(int uid, const CPUArchIdList *apic_ids, {uint32_t apic_id = apic_ids->cpus[uid].arch_id;/* Flags – Local APIC Flags */ -uint32_t flags = apic_ids->cpus[uid].cpu !=NULL || force_enabled ? -1 /* Enabled */ :0 ; +bool enabled = apic_ids->cpus[uid].cpu !=NULL || force_enabled ? + true : false;
Quoted 9 lines
hw/i386/acpi-common.c void pc_madt_cpu_entry(int uid, const CPUArchIdList *apic_ids, · line 47
Quoted 5 lines
hw/i386/acpi-common.c +5
-0+/* +* ACPI 6.3 5.2.12.2 Local APIC Flags: OnlineCapable must be 0 +* if Enabled is set. +*/ +bool onlinecapable = enabled ? false : true;Pls write this as onlinecapable = !enabled or just open-code on the next line - does not look like this variable adds a lot of value.
Will do!
Quoted 17 lines
Quoted 16 lines
hw/i386/acpi-common.c +3
-1+uint32_t flags = onlinecapable ?0x2 :0x0 |/* Online Capable */ + enabled ?0x1 :0x0 ;/* Enabled */ /* ACPI spec says that LAPIC entry for non present * CPU may be omitted from MADT or it must be marked @@ -102,7 +109,7 @@ void acpi_build_madt(GArray *table_data, BIOSLinker *linker,MachineClass *mc =MACHINE_GET_CLASS (x86ms);const CPUArchIdList *apic_ids = mc->possible_cpu_arch_ids (MACHINE (x86ms));AcpiDeviceIfClass *adevc =ACPI_DEVICE_IF_GET_CLASS (adev); -AcpiTable table = { .sig ="APIC" , .rev =1 , .oem_id = oem_id, +AcpiTable table = { .sig ="APIC" , .rev =5 , .oem_id = oem_id, .oem_table_id = oem_table_id };acpi_table_begin (&table, table_data);Signature · 1 line
2.31.1
Re: [PATCH v2 3/4] hw/acpi: i386: bump MADT to revision 5
In reply to Eric DeVolderQuoted 24 lines · Eric DeVolder
Currently i386 QEMU generates MADT revision 3, and reports MADT revision 1. ACPI 6.3 introduces MADT revision 5.
For MADT revision 4, that introduces ARM GIC structures, which do not apply to i386.
For MADT revision 5, the Local APIC flags introduces the Online Capable bitfield.
Making MADT generate and report revision 5 will solve problems with CPU hotplug (the Online Capable flag indicates hotpluggable CPUs).
Signed-off-by Eric DeVolder <[email protected]>--- hw/i386/acpi-common.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)hw/i386/acpi-common.c +0
-0
hw/i386/acpi-common.c void pc_madt_cpu_entry(int uid, const CPUArchIdList *apic_ids, · line 42
Quoted 7 lines
hw/i386/acpi-common.c +2
-2@@ -38,8 +38,15 @@ void pc_madt_cpu_entry(int uid, const CPUArchIdList *apic_ids, {uint32_t apic_id = apic_ids->cpus[uid].arch_id;/* Flags – Local APIC Flags */ -uint32_t flags = apic_ids->cpus[uid].cpu !=NULL || force_enabled ? -1 /* Enabled */ :0 ; +bool enabled = apic_ids->cpus[uid].cpu !=NULL || force_enabled ? + true : false;
how about "processor_enabled" instead of just "enabled" as the variable name.
hw/i386/acpi-common.c void pc_madt_cpu_entry(int uid, const CPUArchIdList *apic_ids, · line 47
Quoted 5 lines
hw/i386/acpi-common.c +5
-0+/* +* ACPI 6.3 5.2.12.2 Local APIC Flags: OnlineCapable must be 0 +* if Enabled is set. +*/ +bool onlinecapable = enabled ? false : true;
ugh, how about uint32 onlinecapable = enabled? 0x0 : 0x2 ?
hw/i386/acpi-common.c void pc_madt_cpu_entry(int uid, const CPUArchIdList *apic_ids, · line 49
Quoted 2 lines
hw/i386/acpi-common.c +2
-0+uint32_t flags = onlinecapable ?0x2 :0x0 |/* Online Capable */ + enabled ?0x1 :0x0 ;/* Enabled */
then here, flags = onlinecapable | processor_enabled? 0x1 : 0x0;
Quoted 15 lines
hw/i386/acpi-common.c +1
-2/* ACPI spec says that LAPIC entry for non present * CPU may be omitted from MADT or it must be marked @@ -102,7 +109,7 @@ void acpi_build_madt(GArray *table_data, BIOSLinker *linker,MachineClass *mc =MACHINE_GET_CLASS (x86ms);const CPUArchIdList *apic_ids = mc->possible_cpu_arch_ids (MACHINE (x86ms));AcpiDeviceIfClass *adevc =ACPI_DEVICE_IF_GET_CLASS (adev); -AcpiTable table = { .sig ="APIC" , .rev =1 , .oem_id = oem_id, +AcpiTable table = { .sig ="APIC" , .rev =5 , .oem_id = oem_id, .oem_table_id = oem_table_id };acpi_table_begin (&table, table_data); --2.31.1
Re: [PATCH v2 3/4] hw/acpi: i386: bump MADT to revision 5
Quoted 41 lines · On Thu, 20 Apr 2023 13:35:58 +0530 Ani Sinha <[email protected]> wrote:
Quoted 24 lines · Eric DeVolder
Currently i386 QEMU generates MADT revision 3, and reports MADT revision 1. ACPI 6.3 introduces MADT revision 5.
For MADT revision 4, that introduces ARM GIC structures, which do not apply to i386.
For MADT revision 5, the Local APIC flags introduces the Online Capable bitfield.
Making MADT generate and report revision 5 will solve problems with CPU hotplug (the Online Capable flag indicates hotpluggable CPUs).
Signed-off-by Eric DeVolder <[email protected]>--- hw/i386/acpi-common.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)hw/i386/acpi-common.c +0
-0hw/i386/acpi-common.c void pc_madt_cpu_entry(int uid, const CPUArchIdList *apic_ids, · line 42
Quoted 7 lines
hw/i386/acpi-common.c +2
-2@@ -38,8 +38,15 @@ void pc_madt_cpu_entry(int uid, const CPUArchIdList *apic_ids, {uint32_t apic_id = apic_ids->cpus[uid].arch_id;/* Flags – Local APIC Flags */ -uint32_t flags = apic_ids->cpus[uid].cpu !=NULL || force_enabled ? -1 /* Enabled */ :0 ; +bool enabled = apic_ids->cpus[uid].cpu !=NULL || force_enabled ? + true : false;how about "
processor_enabled" instead of just "enabled" as the variable name.hw/i386/acpi-common.c void pc_madt_cpu_entry(int uid, const CPUArchIdList *apic_ids, · line 47
Quoted 5 lines
hw/i386/acpi-common.c +5
-0+/* +* ACPI 6.3 5.2.12.2 Local APIC Flags: OnlineCapable must be 0 +* if Enabled is set. +*/ +bool onlinecapable = enabled ? false : true;
Quoted 6 lines
ugh, how about uint32 onlinecapable = enabled?
0x0:0x2?hw/i386/acpi-common.c void pc_madt_cpu_entry(int uid, const CPUArchIdList *apic_ids, · line 49
Quoted 2 lines
hw/i386/acpi-common.c +2
-0+uint32_t flags = onlinecapable ?0x2 :0x0 |/* Online Capable */ + enabled ?0x1 :0x0 ;/* Enabled */ then here, flags = onlinecapable |
processor_enabled?0x1:0x0;
onlinecapable is unnecessary complication.
See my reply on v1, we don't really have a reason to bump MADT revision to 5, It brings no value whatsoever. (and kernel fix went another route instead of dealing with messed up MADT revision numbering in spec)
All we need is to just bump revision to 3 or 4 to match actually used features.
Quoted 17 lines
Quoted 16 lines
hw/i386/acpi-common.c +1
-2/* ACPI spec says that LAPIC entry for non present * CPU may be omitted from MADT or it must be marked @@ -102,7 +109,7 @@ void acpi_build_madt(GArray *table_data, BIOSLinker *linker,MachineClass *mc =MACHINE_GET_CLASS (x86ms);const CPUArchIdList *apic_ids = mc->possible_cpu_arch_ids (MACHINE (x86ms));AcpiDeviceIfClass *adevc =ACPI_DEVICE_IF_GET_CLASS (adev); -AcpiTable table = { .sig ="APIC" , .rev =1 , .oem_id = oem_id, +AcpiTable table = { .sig ="APIC" , .rev =5 , .oem_id = oem_id, .oem_table_id = oem_table_id };acpi_table_begin (&table, table_data); --2.31.1
Re: [PATCH v2 3/4] hw/acpi: i386: bump MADT to revision 5
In reply to Ani SinhaQuoted 41 lines · Ani Sinha
Quoted 24 lines · Eric DeVolder
Currently i386 QEMU generates MADT revision 3, and reports MADT revision 1. ACPI 6.3 introduces MADT revision 5.
For MADT revision 4, that introduces ARM GIC structures, which do not apply to i386.
For MADT revision 5, the Local APIC flags introduces the Online Capable bitfield.
Making MADT generate and report revision 5 will solve problems with CPU hotplug (the Online Capable flag indicates hotpluggable CPUs).
Signed-off-by Eric DeVolder <[email protected]>--- hw/i386/acpi-common.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)hw/i386/acpi-common.c +0
-0hw/i386/acpi-common.c void pc_madt_cpu_entry(int uid, const CPUArchIdList *apic_ids, · line 42
Quoted 7 lines
hw/i386/acpi-common.c +2
-2@@ -38,8 +38,15 @@ void pc_madt_cpu_entry(int uid, const CPUArchIdList *apic_ids, {uint32_t apic_id = apic_ids->cpus[uid].arch_id;/* Flags – Local APIC Flags */ -uint32_t flags = apic_ids->cpus[uid].cpu !=NULL || force_enabled ? -1 /* Enabled */ :0 ; +bool enabled = apic_ids->cpus[uid].cpu !=NULL || force_enabled ? + true : false;how about "
processor_enabled" instead of just "enabled" as the variable name.hw/i386/acpi-common.c void pc_madt_cpu_entry(int uid, const CPUArchIdList *apic_ids, · line 47
Quoted 5 lines
hw/i386/acpi-common.c +5
-0+/* +* ACPI 6.3 5.2.12.2 Local APIC Flags: OnlineCapable must be 0 +* if Enabled is set. +*/ +bool onlinecapable = enabled ? false : true;
Quoted 7 lines
ugh, how about uint32 onlinecapable = enabled?
0x0:0x2?hw/i386/acpi-common.c void pc_madt_cpu_entry(int uid, const CPUArchIdList *apic_ids, · line 49
Quoted 2 lines
hw/i386/acpi-common.c +2
-0+uint32_t flags = onlinecapable ?0x2 :0x0 |/* Online Capable */ + enabled ?0x1 :0x0 ;/* Enabled */ then here, flags = onlinecapable |
processor_enabled?0x1:0x0;
Colleague Miguel Luis pointed out that this is simpler and equivalent:
uint32_t flags = apic_ids->cpus[uid].cpu != NULL || force_enabled ? 1 /* Enabled */ : 2 /* Online Capable */;
Is that acceptable?
eric
Quoted 15 lines
Quoted 15 lines
hw/i386/acpi-common.c +1
-2/* ACPI spec says that LAPIC entry for non present * CPU may be omitted from MADT or it must be marked @@ -102,7 +109,7 @@ void acpi_build_madt(GArray *table_data, BIOSLinker *linker,MachineClass *mc =MACHINE_GET_CLASS (x86ms);const CPUArchIdList *apic_ids = mc->possible_cpu_arch_ids (MACHINE (x86ms));AcpiDeviceIfClass *adevc =ACPI_DEVICE_IF_GET_CLASS (adev); -AcpiTable table = { .sig ="APIC" , .rev =1 , .oem_id = oem_id, +AcpiTable table = { .sig ="APIC" , .rev =5 , .oem_id = oem_id, .oem_table_id = oem_table_id };acpi_table_begin (&table, table_data); --2.31.1
Re: [PATCH v2 3/4] hw/acpi: i386: bump MADT to revision 5
Quoted 52 lines · Eric DeVolder
Quoted 41 lines · Ani Sinha
Quoted 24 lines · Eric DeVolder
Currently i386 QEMU generates MADT revision 3, and reports MADT revision 1. ACPI 6.3 introduces MADT revision 5.
For MADT revision 4, that introduces ARM GIC structures, which do not apply to i386.
For MADT revision 5, the Local APIC flags introduces the Online Capable bitfield.
Making MADT generate and report revision 5 will solve problems with CPU hotplug (the Online Capable flag indicates hotpluggable CPUs).
Signed-off-by Eric DeVolder <[email protected]>--- hw/i386/acpi-common.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)hw/i386/acpi-common.c +0
-0hw/i386/acpi-common.c void pc_madt_cpu_entry(int uid, const CPUArchIdList *apic_ids, · line 42
Quoted 7 lines
hw/i386/acpi-common.c +2
-2@@ -38,8 +38,15 @@ void pc_madt_cpu_entry(int uid, const CPUArchIdList *apic_ids, {uint32_t apic_id = apic_ids->cpus[uid].arch_id;/* Flags – Local APIC Flags */ -uint32_t flags = apic_ids->cpus[uid].cpu !=NULL || force_enabled ? -1 /* Enabled */ :0 ; +bool enabled = apic_ids->cpus[uid].cpu !=NULL || force_enabled ? + true : false;how about "
processor_enabled" instead of just "enabled" as the variable name.hw/i386/acpi-common.c void pc_madt_cpu_entry(int uid, const CPUArchIdList *apic_ids, · line 47
Quoted 5 lines
hw/i386/acpi-common.c +5
-0+/* +* ACPI 6.3 5.2.12.2 Local APIC Flags: OnlineCapable must be 0 +* if Enabled is set. +*/ +bool onlinecapable = enabled ? false : true;Quoted 7 lines
ugh, how about uint32 onlinecapable = enabled?
0x0:0x2?hw/i386/acpi-common.c void pc_madt_cpu_entry(int uid, const CPUArchIdList *apic_ids, · line 49
Quoted 2 lines
hw/i386/acpi-common.c +2
-0+uint32_t flags = onlinecapable ?0x2 :0x0 |/* Online Capable */ + enabled ?0x1 :0x0 ;/* Enabled */ then here, flags = onlinecapable |
processor_enabled?0x1:0x0;
Quoted 7 lines
Colleague Miguel Luis pointed out that this is simpler and equivalent:
uint32_tflags = apic_ids->cpus[uid].cpu != NULL ||force_enabled? 1 /* Enabled */ : 2 /* Online Capable */;Is that acceptable?
eric
Looks ok to me.
Quoted 15 lines
Quoted 15 lines
Quoted 15 lines
hw/i386/acpi-common.c +1
-2/* ACPI spec says that LAPIC entry for non present * CPU may be omitted from MADT or it must be marked @@ -102,7 +109,7 @@ void acpi_build_madt(GArray *table_data, BIOSLinker *linker,MachineClass *mc =MACHINE_GET_CLASS (x86ms);const CPUArchIdList *apic_ids = mc->possible_cpu_arch_ids (MACHINE (x86ms));AcpiDeviceIfClass *adevc =ACPI_DEVICE_IF_GET_CLASS (adev); -AcpiTable table = { .sig ="APIC" , .rev =1 , .oem_id = oem_id, +AcpiTable table = { .sig ="APIC" , .rev =5 , .oem_id = oem_id, .oem_table_id = oem_table_id };acpi_table_begin (&table, table_data); --2.31.1
PATCH v2 4/4 ACPI: bios-tables-test.c step 5 (updated expected table binaries)
In reply to Eric DeVolderFollowing the guidelines in tests/qtest/bios-tables-test.c, this is step 6.
For the cpuhp test case, it is started with:
-smp 2,cores=3,sockets=2,maxcpus=6
So two of six CPUs are present, leaving 4 hot-pluggable CPUs. This is what the disassembly diff below shows (two entries with Enabled=1 and the new Online Capable bit 0, and four entries with Enabled=0 and Online Capable bit 1).
--- /tmp/asl-NP2E31.dsl 2023-04-18 10:46:26.483612104 -0400
+++ /tmp/asl-C03E31.dsl 2023-04-18 10:46:26.481612093 -0400
@@ -1,89 +1,89 @@
/*
* Intel ACPI Component Architecture
* AML/ASL+ Disassembler version 20230331 (64-bit version)
* Copyright (c) 2000 - 2023 Intel Corporation
*
- * Disassembly of tests/data/acpi/pc/APIC.cphp, Tue Apr 18 10:46:26 2023
+ * Disassembly of /tmp/aml-6A5E31, Tue Apr 18 10:46:26 2023
*
* ACPI Data Table [APIC]
*
* Format: [HexOffset DecimalOffset ByteLength] FieldName : FieldValue (in hex) */
[000h 0000 004h] Signature : "APIC" [Multiple APIC Description Table (MADT)]
[004h 0004 004h] Table Length : 000000A0
-[008h 0008 001h] Revision : 01 -[009h 0009 001h] Checksum : 18 +[008h 0008 001h] Revision : 05 +[009h 0009 001h] Checksum : 0C
[00Ah 0010 006h] Oem ID : "BOCHS "
[010h 0016 008h] Oem Table ID : "BXPC "
[018h 0024 004h] Oem Revision : 00000001
[01Ch 0028 004h] Asl Compiler ID : "BXPC"
[020h 0032 004h] Asl Compiler Revision : 00000001
[024h 0036 004h] Local Apic Address : FEE00000
[028h 0040 004h] Flags (decoded below) : 00000001
PC-AT Compatibility : 1
[02Ch 0044 001h] Subtable Type : 00 [Processor Local APIC]
[02Dh 0045 001h] Length : 08
[02Eh 0046 001h] Processor ID : 00
[02Fh 0047 001h] Local Apic ID : 00
[030h 0048 004h] Flags (decoded below) : 00000001
Processor Enabled : 1
Runtime Online Capable : 0
[034h 0052 001h] Subtable Type : 00 [Processor Local APIC]
[035h 0053 001h] Length : 08
[036h 0054 001h] Processor ID : 01
[037h 0055 001h] Local Apic ID : 01
[038h 0056 004h] Flags (decoded below) : 00000001
Processor Enabled : 1
Runtime Online Capable : 0
[03Ch 0060 001h] Subtable Type : 00 [Processor Local APIC]
[03Dh 0061 001h] Length : 08
[03Eh 0062 001h] Processor ID : 02
[03Fh 0063 001h] Local Apic ID : 02
-[040h 0064 004h] Flags (decoded below) : 00000000
+[040h 0064 004h] Flags (decoded below) : 00000002
Processor Enabled : 0
- Runtime Online Capable : 0
+ Runtime Online Capable : 1
[044h 0068 001h] Subtable Type : 00 [Processor Local APIC]
[045h 0069 001h] Length : 08
[046h 0070 001h] Processor ID : 03
[047h 0071 001h] Local Apic ID : 04
-[048h 0072 004h] Flags (decoded below) : 00000000
+[048h 0072 004h] Flags (decoded below) : 00000002
Processor Enabled : 0
- Runtime Online Capable : 0
+ Runtime Online Capable : 1
[04Ch 0076 001h] Subtable Type : 00 [Processor Local APIC]
[04Dh 0077 001h] Length : 08
[04Eh 0078 001h] Processor ID : 04
[04Fh 0079 001h] Local Apic ID : 05
-[050h 0080 004h] Flags (decoded below) : 00000000
+[050h 0080 004h] Flags (decoded below) : 00000002
Processor Enabled : 0
- Runtime Online Capable : 0
+ Runtime Online Capable : 1
[054h 0084 001h] Subtable Type : 00 [Processor Local APIC]
[055h 0085 001h] Length : 08
[056h 0086 001h] Processor ID : 05
[057h 0087 001h] Local Apic ID : 06
-[058h 0088 004h] Flags (decoded below) : 00000000
+[058h 0088 004h] Flags (decoded below) : 00000002
Processor Enabled : 0
- Runtime Online Capable : 0
+ Runtime Online Capable : 1
[05Ch 0092 001h] Subtable Type : 01 [I/O APIC]
[05Dh 0093 001h] Length : 0C
[05Eh 0094 001h] I/O Apic ID : 00
[05Fh 0095 001h] Reserved : 00
[060h 0096 004h] Address : FEC00000
[064h 0100 004h] Interrupt : 00000000
[068h 0104 001h] Subtable Type : 02 [Interrupt Source Override]
[069h 0105 001h] Length : 0A
[06Ah 0106 001h] Bus : 00
[06Bh 0107 001h] Source : 00
[06Ch 0108 004h] Interrupt : 00000002
[070h 0112 002h] Flags (decoded below) : 0000
Polarity : 0
Trigger Mode : 0
@@ -121,26 +121,26 @@
[093h 0147 001h] Source : 0B
[094h 0148 004h] Interrupt : 0000000B
[098h 0152 002h] Flags (decoded below) : 000D
Polarity : 1
Trigger Mode : 3
[09Ah 0154 001h] Subtable Type : 04 [Local APIC NMI]
[09Bh 0155 001h] Length : 06
[09Ch 0156 001h] Processor ID : FF
[09Dh 0157 002h] Flags (decoded below) : 0000
Polarity : 0
Trigger Mode : 0
[09Fh 0159 001h] Interrupt Input LINT : 01
Raw Table Data: Length 160 (0xA0)
- 0000: 41 50 49 43 A0 00 00 00 01 18 42 4F 43 48 53 20 // APIC......BOCHS
+ 0000: 41 50 49 43 A0 00 00 00 05 0C 42 4F 43 48 53 20 // APIC......BOCHS
0010: 42 58 50 43 20 20 20 20 01 00 00 00 42 58 50 43 // BXPC ....BXPC
0020: 01 00 00 00 00 00 E0 FE 01 00 00 00 00 08 00 00 // ................
0030: 01 00 00 00 00 08 01 01 01 00 00 00 00 08 02 02 // ................
- 0040: 00 00 00 00 00 08 03 04 00 00 00 00 00 08 04 05 // ................
- 0050: 00 00 00 00 00 08 05 06 00 00 00 00 01 0C 00 00 // ................
+ 0040: 02 00 00 00 00 08 03 04 02 00 00 00 00 08 04 05 // ................
+ 0050: 02 00 00 00 00 08 05 06 02 00 00 00 01 0C 00 00 // ................
0060: 00 00 C0 FE 00 00 00 00 02 0A 00 00 02 00 00 00 // ................
0070: 00 00 02 0A 00 05 05 00 00 00 0D 00 02 0A 00 09 // ................
0080: 09 00 00 00 0D 00 02 0A 00 0A 0A 00 00 00 0D 00 // ................
0090: 02 0A 00 0B 0B 00 00 00 0D 00 04 06 FF 00 00 01 // ................**
The i386 diff below shows the change of MADT revision to 5.
--- /tmp/asl-STSA31.dsl 2023-04-18 10:44:37.544026591 -0400
+++ /tmp/asl-HEUA31.dsl 2023-04-18 10:44:37.542026578 -0400
@@ -1,32 +1,32 @@
/*
* Intel ACPI Component Architecture
* AML/ASL+ Disassembler version 20230331 (64-bit version)
* Copyright (c) 2000 - 2023 Intel Corporation
*
- * Disassembly of tests/data/acpi/pc/APIC, Tue Apr 18 10:44:37 2023
+ * Disassembly of /tmp/aml-64TA31, Tue Apr 18 10:44:37 2023
*
* ACPI Data Table [APIC]
*
* Format: [HexOffset DecimalOffset ByteLength] FieldName : FieldValue (in hex) */
[000h 0000 004h] Signature : "APIC" [Multiple APIC Description Table (MADT)]
[004h 0004 004h] Table Length : 00000078
-[008h 0008 001h] Revision : 01 -[009h 0009 001h] Checksum : 8A +[008h 0008 001h] Revision : 05 +[009h 0009 001h] Checksum : 86
[00Ah 0010 006h] Oem ID : "BOCHS "
[010h 0016 008h] Oem Table ID : "BXPC "
[018h 0024 004h] Oem Revision : 00000001
[01Ch 0028 004h] Asl Compiler ID : "BXPC"
[020h 0032 004h] Asl Compiler Revision : 00000001
[024h 0036 004h] Local Apic Address : FEE00000
[028h 0040 004h] Flags (decoded below) : 00000001
PC-AT Compatibility : 1
[02Ch 0044 001h] Subtable Type : 00 [Processor Local APIC]
[02Dh 0045 001h] Length : 08
[02Eh 0046 001h] Processor ID : 00
[02Fh 0047 001h] Local Apic ID : 00
[030h 0048 004h] Flags (decoded below) : 00000001
Processor Enabled : 1
@@ -81,24 +81,24 @@
[06Bh 0107 001h] Source : 0B
[06Ch 0108 004h] Interrupt : 0000000B
[070h 0112 002h] Flags (decoded below) : 000D
Polarity : 1
Trigger Mode : 3
[072h 0114 001h] Subtable Type : 04 [Local APIC NMI]
[073h 0115 001h] Length : 06
[074h 0116 001h] Processor ID : FF
[075h 0117 002h] Flags (decoded below) : 0000
Polarity : 0
Trigger Mode : 0
[077h 0119 001h] Interrupt Input LINT : 01
Raw Table Data: Length 120 (0x78)
- 0000: 41 50 49 43 78 00 00 00 01 8A 42 4F 43 48 53 20 // APICx.....BOCHS
+ 0000: 41 50 49 43 78 00 00 00 05 86 42 4F 43 48 53 20 // APICx.....BOCHS
0010: 42 58 50 43 20 20 20 20 01 00 00 00 42 58 50 43 // BXPC ....BXPC
0020: 01 00 00 00 00 00 E0 FE 01 00 00 00 00 08 00 00 // ................
0030: 01 00 00 00 01 0C 00 00 00 00 C0 FE 00 00 00 00 // ................
0040: 02 0A 00 00 02 00 00 00 00 00 02 0A 00 05 05 00 // ................
0050: 00 00 0D 00 02 0A 00 09 09 00 00 00 0D 00 02 0A // ................
0060: 00 0A 0A 00 00 00 0D 00 02 0A 00 0B 0B 00 00 00 // ................
0070: 0D 00 04 06 FF 00 00 01 // ........The diff below show ARM MADT revision change to 5.
--- /tmp/asl-O2P921.dsl 2023-04-18 10:41:56.560930849 -0400
+++ /tmp/asl-XJR921.dsl 2023-04-18 10:41:56.558930836 -0400
@@ -1,32 +1,32 @@
/*
* Intel ACPI Component Architecture
* AML/ASL+ Disassembler version 20230331 (64-bit version)
* Copyright (c) 2000 - 2023 Intel Corporation
*
- * Disassembly of tests/data/acpi/virt/APIC, Tue Apr 18 10:41:56 2023
+ * Disassembly of /tmp/aml-ACR921, Tue Apr 18 10:41:56 2023
*
* ACPI Data Table [APIC]
*
* Format: [HexOffset DecimalOffset ByteLength] FieldName : FieldValue (in hex) */
[000h 0000 004h] Signature : "APIC" [Multiple APIC Description Table (MADT)]
[004h 0004 004h] Table Length : 000000AC
-[008h 0008 001h] Revision : 04 -[009h 0009 001h] Checksum : 47 +[008h 0008 001h] Revision : 05 +[009h 0009 001h] Checksum : 46
[00Ah 0010 006h] Oem ID : "BOCHS "
[010h 0016 008h] Oem Table ID : "BXPC "
[018h 0024 004h] Oem Revision : 00000001
[01Ch 0028 004h] Asl Compiler ID : "BXPC"
[020h 0032 004h] Asl Compiler Revision : 00000001
[024h 0036 004h] Local Apic Address : 00000000
[028h 0040 004h] Flags (decoded below) : 00000000
PC-AT Compatibility : 0
[02Ch 0044 001h] Subtable Type : 0C [Generic Interrupt Distributor]
[02Dh 0045 001h] Length : 18
[02Eh 0046 002h] Reserved : 0000
[030h 0048 004h] Local GIC Hardware ID : 00000000
[034h 0052 008h] Base Address : 0000000008000000
[03Ch 0060 004h] Interrupt Base : 00000000
@@ -55,27 +55,27 @@
[091h 0145 001h] Reserved : 00
[092h 0146 002h] SPE Overflow Interrupt : 0000
[094h 0148 002h] TRBE Interrupt : 180D
[094h 0148 001h] Subtable Type : 0D [Generic MSI Frame]
[095h 0149 001h] Length : 18
[096h 0150 002h] Reserved : 0000
[098h 0152 004h] MSI Frame ID : 00000000
[09Ch 0156 008h] Base Address : 0000000008020000
[0A4h 0164 004h] Flags (decoded below) : 00000001
Select SPI : 1
[0A8h 0168 002h] SPI Count : 0040
[0AAh 0170 002h] SPI Base : 0050
Raw Table Data: Length 172 (0xAC)
- 0000: 41 50 49 43 AC 00 00 00 04 47 42 4F 43 48 53 20 // APIC.....GBOCHS
+ 0000: 41 50 49 43 AC 00 00 00 05 46 42 4F 43 48 53 20 // APIC.....FBOCHS
0010: 42 58 50 43 20 20 20 20 01 00 00 00 42 58 50 43 // BXPC ....BXPC
0020: 01 00 00 00 00 00 00 00 00 00 00 00 0C 18 00 00 // ................
0030: 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00 00 // ................
0040: 02 00 00 00 0B 50 00 00 00 00 00 00 00 00 00 00 // .....P..........
0050: 01 00 00 00 00 00 00 00 17 00 00 00 00 00 00 00 // ................
0060: 00 00 00 00 00 00 01 08 00 00 00 00 00 00 04 08 // ................
0070: 00 00 00 00 00 00 03 08 00 00 00 00 00 00 00 00 // ................
0080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 // ................
0090: 00 00 00 00 0D 18 00 00 00 00 00 00 00 00 02 08 // ................
00A0: 00 00 00 00 01 00 00 00 40 00 50 00 // [email protected].--- tests/data/acpi/microvm/APIC | Bin 70 -> 70 bytes tests/data/acpi/microvm/APIC.ioapic2 | Bin 82 -> 82 bytes tests/data/acpi/microvm/APIC.pcie | Bin 110 -> 110 bytes tests/data/acpi/pc/APIC | Bin 120 -> 120 bytes tests/data/acpi/pc/APIC.acpihmat | Bin 128 -> 128 bytes tests/data/acpi/pc/APIC.cphp | Bin 160 -> 160 bytes tests/data/acpi/pc/APIC.dimmpxm | Bin 144 -> 144 bytes tests/data/acpi/q35/APIC | Bin 120 -> 120 bytes tests/data/acpi/q35/APIC.acpihmat | Bin 128 -> 128 bytes tests/data/acpi/q35/APIC.acpihmat-noinitiator | Bin 144 -> 144 bytes tests/data/acpi/q35/APIC.core-count2 | Bin 2478 -> 2478 bytes tests/data/acpi/q35/APIC.cphp | Bin 160 -> 160 bytes tests/data/acpi/q35/APIC.dimmpxm | Bin 144 -> 144 bytes tests/data/acpi/q35/APIC.xapic | Bin 2686 -> 2686 bytes tests/data/acpi/virt/APIC | Bin 172 -> 172 bytes tests/data/acpi/virt/APIC.acpihmatvirt | Bin 412 -> 412 bytes tests/data/acpi/virt/APIC.topology | Bin 732 -> 732 bytes tests/qtest/bios-tables-test-allowed-diff.h | 4 ---- 18 files changed, 4 deletions(-)
tests/data/acpi/microvm/APIC binary +0 -0
tests/data/acpi/microvm/APIC.ioapic2 binary +0 -0
tests/data/acpi/microvm/APIC.pcie binary +0 -0
tests/data/acpi/pc/APIC binary +0 -0
tests/data/acpi/pc/APIC.acpihmat binary +0 -0
tests/data/acpi/pc/APIC.cphp binary +0 -0
tests/data/acpi/pc/APIC.dimmpxm binary +0 -0
tests/data/acpi/q35/APIC binary +0 -0
tests/data/acpi/q35/APIC.acpihmat binary +0 -0
tests/data/acpi/q35/APIC.acpihmat-noinitiator binary +0 -0
tests/data/acpi/q35/APIC.core-count2 binary +0 -0
tests/data/acpi/q35/APIC.cphp binary +0 -0
tests/data/acpi/q35/APIC.dimmpxm binary +0 -0
tests/data/acpi/q35/APIC.xapic binary +0 -0
tests/data/acpi/virt/APIC binary +0 -0
tests/data/acpi/virt/APIC.acpihmatvirt binary +0 -0
tests/data/acpi/virt/APIC.topology binary +0 -0
tests/qtest/bios-tables-test-allowed-diff.h +0 -4
@@ -1,5 +1 @@/* List of comma-separated changed AML files to ignore */ -"tests/data/acpi/pc/APIC" , -"tests/data/acpi/q35/APIC" , -"tests/data/acpi/microvm/APIC" , -"tests/data/acpi/virt/APIC",
Signature · 1 line
2.31.1