Add ACPI CPER firmware first error injection on ARM emulation
PATCH v5 1/7 arm/virt: place power button pin number on a define
In reply to Mauro Carvalho ChehabHaving magic numbers inside the code is not a good idea, as it is error-prone. So, instead, create a macro with the number definition.
--- hw/arm/virt-acpi-build.c | 6 +++--- hw/arm/virt.c | 7 ++++--- include/hw/arm/virt.h | 3 +++ 3 files changed, 10 insertions(+), 6 deletions(-)
hw/arm/virt-acpi-build.c +3 -3
@@ -154,10 +154,10 @@ static void acpi_dsdt_add_gpio(Aml *scope, const MemMapEntry *gpio_memmap,aml_append (dev,aml_name_decl ("_CRS" , crs));Aml *aei =aml_resource_template (); -/* Pin 3 for power button */ -const uint32_t pin_list[1 ] = {3 }; + +const uint32_t pin =GPIO_PIN_POWER_BUTTON ;aml_append (aei,aml_gpio_int (AML_CONSUMER ,AML_EDGE ,AML_ACTIVE_HIGH , -AML_EXCLUSIVE ,AML_PULL_UP ,0 , pin_list,1 , +AML_EXCLUSIVE ,AML_PULL_UP ,0 , &pin,1 ,"GPO0" ,NULL ,0 ));aml_append (dev,aml_name_decl ("_AEI" , aei));
hw/arm/virt.c +4 -3
@@ -1004,7 +1004,7 @@ static void virt_powerdown_req(Notifier *n, void *opaque)if (s->acpi_dev) {acpi_send_event (s->acpi_dev,ACPI_POWER_DOWN_STATUS ); }else { -/* use gpio Pin 3 for power button event */ +/* use gpio Pin for power button event */ qemu_set_irq (qdev_get_gpio_in (gpio_key_dev,0 ),1 ); } }
@@ -1013,7 +1013,8 @@ static void create_gpio_keys(char *fdt, DeviceState *pl061_dev, uint32_t phandle) { gpio_key_dev =sysbus_create_simple ("gpio-key" ,-1 , -qdev_get_gpio_in (pl061_dev,3 )); +qdev_get_gpio_in (pl061_dev, +GPIO_PIN_POWER_BUTTON ));qemu_fdt_add_subnode (fdt,"/gpio-keys" );qemu_fdt_setprop_string (fdt,"/gpio-keys" ,"compatible" ,"gpio-keys" );
@@ -1024,7 +1025,7 @@ static void create_gpio_keys(char *fdt, DeviceState *pl061_dev,qemu_fdt_setprop_cell (fdt,"/gpio-keys/poweroff" ,"linux,code" ,KEY_POWER );qemu_fdt_setprop_cells (fdt,"/gpio-keys/poweroff" , -"gpios" , phandle,3 ,0 ); +"gpios" , phandle,GPIO_PIN_POWER_BUTTON ,0 ); }#define SECURE_GPIO_POWEROFF 0
include/hw/arm/virt.h +3 -0
@@ -47,6 +47,9 @@/* See Linux kernel arch/arm64/include/asm/pvclock-abi.h */ #define PVTIME_SIZE_PER_CPU 64 +/* GPIO pins */ +#define GPIO_PIN_POWER_BUTTON 3 +enum {VIRT_FLASH ,VIRT_MEM ,
Signature · 1 line
2.45.2
PATCH v5 2/7 acpi/generic_event_device: add an APEI error device
In reply to Mauro Carvalho ChehabAdds a Generic Event Device to handle generic hardware error events, supporting General Purpose Event (GPE) as specified at ACPI 6.5 specification at 18.3.2.7.2:
https://uefi.org/specs/ACPI/6.5/18_Platform_Error_Interfaces.html#event-notification-for-generic-error-sources
using HID PNP0C33.
The PNP0C33 device is used to report hardware errors to the bios via ACPI APEI Generic Hardware Error Source (GHES).
--- hw/acpi/generic_event_device.c | 17 +++++++++++++++++ include/hw/acpi/acpi_dev_interface.h | 1 + include/hw/acpi/generic_event_device.h | 3 +++ 3 files changed, 21 insertions(+)
hw/acpi/generic_event_device.c +17 -0
@@ -26,6 +26,7 @@ static const uint32_t ged_supported_events[] = {ACPI_GED_PWR_DOWN_EVT ,ACPI_GED_NVDIMM_HOTPLUG_EVT ,ACPI_GED_CPU_HOTPLUG_EVT , + ACPI_GED_ERROR_EVT };/*
@@ -116,6 +117,11 @@ void build_ged_aml(Aml *table, const char *name, HotplugHandler *hotplug_dev,aml_notify (aml_name (ACPI_POWER_BUTTON_DEVICE ), aml_int(0x80)));break ; +case ACPI_GED_ERROR_EVT : +aml_append (if_ctx, +aml_notify (aml_name (ACPI_APEI_ERROR_DEVICE ), +aml_int (0x80 ))); +break ;case ACPI_GED_NVDIMM_HOTPLUG_EVT : aml_append(if_ctx, aml_notify(aml_name("\\_SB.NVDR"),
@@ -153,6 +159,15 @@ void acpi_dsdt_add_power_button(Aml *scope)aml_append (scope, dev); } +void acpi_dsdt_add_error_device (Aml *scope) +{ +Aml *dev =aml_device (ACPI_APEI_ERROR_DEVICE ); +aml_append (dev,aml_name_decl ("_HID" ,aml_string ("PNP0C33" ))); +aml_append (dev,aml_name_decl ("_UID" ,aml_int (0 ))); +aml_append (dev,aml_name_decl ("_STA" ,aml_int (0xF ))); +aml_append (scope, dev); +} +/* Memory read by the GED _EVT AML dynamic method */ static uint64_t ged_evt_read (void *opaque,hwaddr addr,unsigned size) {
@@ -295,6 +310,8 @@ static void acpi_ged_send_event(AcpiDeviceIf *adev, AcpiEventStatusBits ev) sel =ACPI_GED_MEM_HOTPLUG_EVT ; }else if (ev &ACPI_POWER_DOWN_STATUS ) { sel =ACPI_GED_PWR_DOWN_EVT ; + }else if (ev &ACPI_GENERIC_ERROR ) { + sel =ACPI_GED_ERROR_EVT ; }else if (ev &ACPI_NVDIMM_HOTPLUG_STATUS ) { sel =ACPI_GED_NVDIMM_HOTPLUG_EVT ; }else if (ev &ACPI_CPU_HOTPLUG_STATUS ) {
include/hw/acpi/acpi_dev_interface.h +1 -0
@@ -13,6 +13,7 @@ typedef enum {ACPI_NVDIMM_HOTPLUG_STATUS =16 ,ACPI_VMGENID_CHANGE_STATUS =32 ,ACPI_POWER_DOWN_STATUS =64 , +ACPI_GENERIC_ERROR =128 , } AcpiEventStatusBits;#define TYPE_ACPI_DEVICE_IF "acpi-device-interface"
include/hw/acpi/generic_event_device.h +3 -0
@@ -66,6 +66,7 @@#include "qom/object.h" #define ACPI_POWER_BUTTON_DEVICE "PWRB" +#define ACPI_APEI_ERROR_DEVICE "GEDD"#define TYPE_ACPI_GED "acpi-ged"OBJECT_DECLARE_SIMPLE_TYPE (AcpiGedState,ACPI_GED )
@@ -98,6 +99,7 @@ OBJECT_DECLARE_SIMPLE_TYPE(AcpiGedState, ACPI_GED)#define ACPI_GED_PWR_DOWN_EVT 0x2#define ACPI_GED_NVDIMM_HOTPLUG_EVT 0x4#define ACPI_GED_CPU_HOTPLUG_EVT 0x8 +#define ACPI_GED_ERROR_EVT 0x10 typedef struct GEDState { MemoryRegion evt;
@@ -120,5 +122,6 @@ struct AcpiGedState {void build_ged_aml (Aml *table,const char * name,HotplugHandler *hotplug_dev,uint32_t ged_irq,AmlRegionSpace rs,hwaddr ged_base);void acpi_dsdt_add_power_button (Aml *scope); +void acpi_dsdt_add_error_device (Aml *scope);#endif
Signature · 1 line
2.45.2
PATCH v5 3/7 arm/virt: Wire up GPIO error source for ACPI / GHES
In reply to Mauro Carvalho ChehabAdds support to ARM virtualization to allow handling a General Purpose Event (GPE) via GED error device.
It is aligned with Linux Kernel patch:
https://lore.kernel.org/lkml/[email protected]/
--- hw/acpi/ghes.c | 3 +++ hw/arm/virt-acpi-build.c | 1 + hw/arm/virt.c | 16 +++++++++++++++- include/hw/acpi/ghes.h | 3 +++ include/hw/arm/virt.h | 1 + 5 files changed, 23 insertions(+), 1 deletion(-)
hw/acpi/ghes.c +3 -0
@@ -444,6 +444,9 @@ int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address)return ret; } +NotifierList generic_error_notifiers = +NOTIFIER_LIST_INITIALIZER (error_device_notifiers); +bool acpi_ghes_present (void ) {AcpiGedState *acpi_ged_state;
hw/arm/virt-acpi-build.c +1 -0
@@ -858,6 +858,7 @@ build_dsdt(GArray *table_data, BIOSLinker *linker, VirtMachineState *vms) }acpi_dsdt_add_power_button (scope); +acpi_dsdt_add_error_device (scope);#ifdef CONFIG_TPM acpi_dsdt_add_tpm (scope, vms);#endif
hw/arm/virt.c +15 -1
@@ -73,6 +73,7 @@#include "standard-headers/linux/input.h" #include "hw/arm/smmuv3.h" #include "hw/acpi/acpi.h" +#include "hw/acpi/ghes.h" #include "target/arm/cpu-qom.h" #include "target/arm/internals.h" #include "target/arm/multiprocessing.h"
@@ -677,7 +678,7 @@ static inline DeviceState *create_acpi_ged(VirtMachineState *vms)DeviceState *dev;MachineState *ms =MACHINE (vms);int irq = vms->irqmap[VIRT_ACPI_GED ]; -uint32_t event =ACPI_GED_PWR_DOWN_EVT ; +uint32_t event =ACPI_GED_PWR_DOWN_EVT |ACPI_GED_ERROR_EVT ;if (ms->ram_slots) { event |=ACPI_GED_MEM_HOTPLUG_EVT ;
@@ -1009,6 +1010,15 @@ static void virt_powerdown_req(Notifier *n, void *opaque) } } +static void virt_generic_error_req (Notifier *n,void *opaque) +{ +VirtMachineState *s =container_of (n, VirtMachineState, generic_error_notifier); + +if (s->acpi_dev) { +acpi_send_event (s->acpi_dev,ACPI_GENERIC_ERROR ); + } +} +static void create_gpio_keys (char *fdt,DeviceState *pl061_dev,uint32_t phandle) {
@@ -2397,6 +2407,10 @@ static void machvirt_init(MachineState *machine) vms->powerdown_notifier.notify = virt_powerdown_req;qemu_register_powerdown_notifier (&vms->powerdown_notifier); + vms->generic_error_notifier.notify = virt_generic_error_req; +notifier_list_add (&generic_error_notifiers, + &vms->generic_error_notifier); +/* Create mmio transports, so the user can create virtio backends * (which will be automatically plugged in to the transports). If * no backend is created the transport will just sit harmlessly idle.
include/hw/acpi/ghes.h +3 -0
@@ -23,6 +23,9 @@#define ACPI_GHES_H #include "hw/acpi/bios-linker-loader.h" +#include "qemu/notify.h" + +extern NotifierList generic_error_notifiers;/* * Values for Hardware Error Notification Type field
include/hw/arm/virt.h +1 -0
@@ -175,6 +175,7 @@ struct VirtMachineState {DeviceState *gic;DeviceState *acpi_dev;Notifier powerdown_notifier; +Notifier generic_error_notifier;PCIBus *bus;char *oem_id;char *oem_table_id;
Signature · 1 line
2.45.2
PATCH v5 4/7 acpi/ghes: Support GPIO error source
In reply to Mauro Carvalho ChehabFrom: Jonathan Cameron <[email protected]>
Add error notification to GHES v2 using the GPIO source.
[mchehab: do some cleanups at ACPI_HEST_SRC_ID_* checks]
--- hw/acpi/ghes.c | 16 ++++++++++------ include/hw/acpi/ghes.h | 3 ++- 2 files changed, 12 insertions(+), 7 deletions(-)
hw/acpi/ghes.c +10 -6
@@ -34,8 +34,8 @@/* The max size in bytes for one error block */ #define ACPI_GHES_MAX_RAW_DATA_LENGTH (1 * KiB) -/* Now only support ARMv8 SEA notification type error source */ -#define ACPI_GHES_ERROR_SOURCE_COUNT 1 +/* Support ARMv8 SEA notification type error source and GPIO interrupt. */ +#define ACPI_GHES_ERROR_SOURCE_COUNT 2/* Generic Hardware Error Source version 2 */ #define ACPI_GHES_SOURCE_GENERIC_ERROR_V2 10
@@ -290,6 +290,9 @@ void build_ghes_error_table(GArray *hardware_errors, BIOSLinker *linker)static void build_ghes_v2 (GArray *table_data,int source_id,BIOSLinker *linker) {uint64_t address_offset; + +assert (source_id <ACPI_HEST_SRC_ID_RESERVED ); +/* * Type: * Generic Hardware Error Source version 2(GHESv2 - Type 10)
@@ -327,6 +330,9 @@ static void build_ghes_v2(GArray *table_data, int source_id, BIOSLinker *linker)*/ build_ghes_hw_error_notification (table_data,ACPI_GHES_NOTIFY_SEA );break ; +case ACPI_HEST_SRC_ID_GPIO : +build_ghes_hw_error_notification (table_data,ACPI_GHES_NOTIFY_GPIO ); +break ;default :error_report ("Not support this error source" );abort ();
@@ -370,6 +376,7 @@ void acpi_build_hest(GArray *table_data, BIOSLinker *linker,/* Error Source Count */ build_append_int_noprefix (table_data,ACPI_GHES_ERROR_SOURCE_COUNT ,4 );build_ghes_v2 (table_data,ACPI_HEST_SRC_ID_SEA , linker); +build_ghes_v2 (table_data,ACPI_HEST_SRC_ID_GPIO , linker);acpi_table_end (linker, &table); }
@@ -406,10 +413,7 @@ int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address) start_addr =le64_to_cpu (ags->ghes_addr_le);if (physical_address) { - -if (source_id <ACPI_HEST_SRC_ID_RESERVED ) { - start_addr += source_id *sizeof (uint64_t ); - } + start_addr += source_id *sizeof (uint64_t );cpu_physical_memory_read (start_addr, &error_block_addr,sizeof (error_block_addr));
include/hw/acpi/ghes.h +2 -1
@@ -59,9 +59,10 @@ enum AcpiGhesNotifyType { ACPI_GHES_NOTIFY_RESERVED = 12 }; +/* Those are used as table indexes when building GHES tables */ enum {ACPI_HEST_SRC_ID_SEA =0 , -/* future ids go here */ +ACPI_HEST_SRC_ID_GPIO ,ACPI_HEST_SRC_ID_RESERVED , };
Signature · 1 line
2.45.2
PATCH v5 5/7 qapi/ghes-cper: add an interface to do generic CPER error injection
In reply to Mauro Carvalho ChehabCreates a QMP command to be used for generic ACPI APEI hardware error injection (HEST) via GHESv2.
The actual GHES code will be added at the followup patch.
--- MAINTAINERS | 7 +++++ hw/acpi/Kconfig | 5 ++++ hw/acpi/ghes_cper.c | 45 ++++++++++++++++++++++++++++++++ hw/acpi/ghes_cper_stub.c | 18 +++++++++++++ hw/acpi/meson.build | 2 ++ hw/arm/Kconfig | 5 ++++ include/hw/acpi/ghes.h | 7 +++++ qapi/ghes-cper.json | 55 ++++++++++++++++++++++++++++++++++++++++ qapi/meson.build | 1 + qapi/qapi-schema.json | 1 + 10 files changed, 146 insertions(+) create mode 100644 hw/acpi/ghes_cper.c create mode 100644 hw/acpi/ghes_cper_stub.c create mode 100644 qapi/ghes-cper.json
MAINTAINERS +7 -0
@@ -2075,6 +2075,13 @@ F: hw/acpi/ghes.c F: include/hw/acpi/ghes.h F: docs/specs/acpi_hest_ghes.rst +ACPI/HEST/GHES/ARM processor CPER +R: Mauro Carvalho Chehab <[email protected]> +S: Maintained +F: hw/arm/ghes_cper.c +F: hw/acpi/ghes_cper_stub.c +F: qapi/ghes-cper.json + ppc4xx L: [email protected] S: Orphan
hw/acpi/Kconfig +5 -0
@@ -51,6 +51,11 @@ config ACPI_APEI bool depends on ACPI +config GHES_CPER + bool + depends on ACPI_APEI + default y + config ACPI_PCI bool depends on ACPI && PCI
hw/acpi/ghes_cper.c new file +45 -0
45 lines not on this page · raw message
hw/acpi/ghes_cper_stub.c new file +18 -0
@@ -0,0 +1,18 @@ +/* +* ARM Processor error injection +* +* Copyright(C) 2024 Huawei LTD. +* +* This code is licensed under the GPL version 2 or later. See the +* COPYING file in the top-level directory. +* +*/ + +#include "qemu/osdep.h" +#include "qapi/error.h" +#include "qapi/qapi-commands-ghes-cper.h" +#include "hw/acpi/ghes.h" + +void qmp_ghes_cper (CommonPlatformErrorRecord *cper,Error **errp) +{ +}
hw/acpi/meson.build +2 -0
@@ -34,4 +34,6 @@ endif system_ss.add(when: 'CONFIG_ACPI', if_false: files('acpi-stub.c', 'aml-build-stub.c', 'ghes-stub.c', 'acpi_interface.c')) system_ss.add(when: 'CONFIG_ACPI_PCI_BRIDGE', if_false: files('pci-bridge-stub.c')) system_ss.add_all(when: 'CONFIG_ACPI', if_true: acpi_ss) +system_ss.add(when: 'CONFIG_GHES_CPER', if_true: files('ghes_cper.c')) +system_ss.add(when: 'CONFIG_GHES_CPER', if_false: files('ghes_cper_stub.c')) system_ss.add(files('acpi-qmp-cmds.c'))
hw/arm/Kconfig +5 -0
@@ -712,3 +712,8 @@ config ARMSSE select UNIMP select SSE_COUNTER select SSE_TIMER + +config GHES_CPER + bool + depends on ARM + default y if AARCH64
include/hw/acpi/ghes.h +7 -0
@@ -23,6 +23,7 @@#define ACPI_GHES_H #include "hw/acpi/bios-linker-loader.h" +#include "qapi/error.h" #include "qemu/notify.h" extern NotifierList generic_error_notifiers;
@@ -78,6 +79,12 @@ void acpi_ghes_add_fw_cfg(AcpiGhesState *vms, FWCfgState *s, GArray *hardware_errors);int acpi_ghes_record_errors (uint8_t notify,uint64_t error_physical_addr); +typedef struct AcpiGhesCper { +uint8_t *guid; +uint8_t *data; +size_t data_len; +}AcpiGhesCper ; +/** * acpi_ghes_present: Report whether ACPI GHES table is present *
qapi/ghes-cper.json new file +55 -0
55 lines not on this page · raw message
qapi/meson.build +1 -0
@@ -35,6 +35,7 @@ qapi_all_modules = [ 'dump', 'ebpf', 'error', + 'ghes-cper', 'introspect', 'job', 'machine-common',
qapi/qapi-schema.json +1 -0
@@ -75,6 +75,7 @@ { 'include': 'misc-target.json' } { 'include': 'audio.json' } { 'include': 'acpi.json' } +{ 'include': 'ghes-cper.json' } { 'include': 'pci.json' } { 'include': 'stats.json' } { 'include': 'virtio.json' }
Signature · 1 line
2.45.2
PATCH v5 6/7 acpi/ghes: add support for generic error injection via QAPI
In reply to Mauro Carvalho ChehabProvide a generic interface for error injection via GHESv2.
This patch is co-authored:
- original ghes logic to inject a simple ARM record by Shiju Jose;
- generic logic to handle block addresses by Jonathan Cameron;
- generic GHESv2 error inject by Mauro Carvalho Chehab;
--- hw/acpi/ghes.c | 159 ++++++++++++++++++++++++++++++++++++++--- hw/acpi/ghes_cper.c | 2 +- include/hw/acpi/ghes.h | 3 + 3 files changed, 152 insertions(+), 12 deletions(-)
hw/acpi/ghes.c +148 -11
@@ -395,23 +395,22 @@ void acpi_ghes_add_fw_cfg(AcpiGhesState *ags, FWCfgState *s, ags->present = true; } +static uint64_t ghes_get_state_start_address (void ) +{ +AcpiGedState *acpi_ged_state = +ACPI_GED (object_resolve_path_type ("" ,TYPE_ACPI_GED ,NULL )); +AcpiGhesState *ags = &acpi_ged_state->ghes_state; + +return le64_to_cpu (ags->ghes_addr_le); +} +int acpi_ghes_record_errors (uint8_t source_id,uint64_t physical_address) {uint64_t error_block_addr, read_ack_register_addr, read_ack_register =0 ; -uint64_t start_addr; +uint64_t start_addr =ghes_get_state_start_address ();bool ret =-1 ; -AcpiGedState *acpi_ged_state; -AcpiGhesState *ags; -assert (source_id <ACPI_HEST_SRC_ID_RESERVED ); - acpi_ged_state =ACPI_GED (object_resolve_path_type ("" ,TYPE_ACPI_GED , -NULL )); -g_assert (acpi_ged_state); - ags = &acpi_ged_state->ghes_state; - - start_addr =le64_to_cpu (ags->ghes_addr_le); -if (physical_address) { start_addr += source_id *sizeof (uint64_t );
@@ -448,9 +447,147 @@ int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address)return ret; } +/* +* Error register block data layout +* +* | +---------------------+ ges.ghes_addr_le +* | |error_block_address0 | +* | +---------------------+ +* | |error_block_address1 | +* | +---------------------+ --+-- +* | | ............. | GHES_ADDRESS_SIZE +* | +---------------------+ --+-- +* | |error_block_addressN | +* | +---------------------+ +* | | read_ack0 | +* | +---------------------+ --+-- +* | | read_ack1 | GHES_ADDRESS_SIZE +* | +---------------------+ --+-- +* | | ............. | +* | +---------------------+ +* | | read_ackN | +* | +---------------------+ --+-- +* | | CPER | | +* | | .... | GHES_MAX_RAW_DATA_LENGT +* | | CPER | | +* | +---------------------+ --+-- +* | | .......... | +* | +---------------------+ +* | | CPER | +* | | .... | +* | | CPER | +* | +---------------------+ +*/ + +/* Map from uint32_t notify to entry offset in GHES */ +static const uint8_t error_source_to_index[] = {0xff ,0xff ,0xff ,0xff , +0xff ,0xff ,0xff ,1 ,0 }; + +static bool ghes_get_addr (uint32_t notify,uint64_t *error_block_addr, +uint64_t *read_ack_addr) +{ +uint64_t base; + +if (notify >=ACPI_GHES_NOTIFY_RESERVED ) { +return false; + } + +/* Find and check the source id for this new CPER */ +if (error_source_to_index[notify] ==0xff ) { +return false; + } + + base =ghes_get_state_start_address (); + + *read_ack_addr = base + +ACPI_GHES_ERROR_SOURCE_COUNT *sizeof (uint64_t ) + + error_source_to_index[notify] *sizeof (uint64_t ); + +/* Could also be read back from the error_block_address register */ + *error_block_addr = base + +ACPI_GHES_ERROR_SOURCE_COUNT *sizeof (uint64_t ) + +ACPI_GHES_ERROR_SOURCE_COUNT *sizeof (uint64_t ) + + error_source_to_index[notify] *ACPI_GHES_MAX_RAW_DATA_LENGTH ; + +return true; +} +NotifierList generic_error_notifiers =NOTIFIER_LIST_INITIALIZER (error_device_notifiers); +void ghes_record_cper_errors (AcpiGhesCper *cper,Error **errp, +uint32_t notify) +{ +int read_ack =0 ; +uint32_t i; +uint64_t read_ack_addr =0 ; +uint64_t error_block_addr =0 ; +uint32_t data_length; +GArray *block; + +if (!ghes_get_addr (notify, &error_block_addr, &read_ack_addr)) { +error_setg (errp,"GHES: Invalid error block/ack address(es)" ); +return ; + } + +cpu_physical_memory_read (read_ack_addr, + &read_ack,sizeof (uint64_t )); + +/* zero means OSPM does not acknowledge the error */ +if (!read_ack) { +error_setg (errp, +"Last CPER record was not acknowledged yet" ); + read_ack =1 ; +cpu_physical_memory_write (read_ack_addr, + &read_ack,sizeof (uint64_t )); +return ; + } + + read_ack =cpu_to_le64 (0 ); +cpu_physical_memory_write (read_ack_addr, + &read_ack,sizeof (uint64_t )); + +/* Build CPER record */ + +/* +* Invalid fru id: ACPI 4.0: 17.3.2.6.1 Generic Error Data, +* Table 17-13 Generic Error Data Entry +*/ +QemuUUID fru_id = {}; + + block =g_array_new (false, true/* clear */ ,1 ); + data_length =ACPI_GHES_DATA_LENGTH + cper->data_len; + +/* +* It should not run out of the preallocated memory if +* adding a new generic error data entry +*/ +assert ((data_length +ACPI_GHES_GESB_SIZE ) <= +ACPI_GHES_MAX_RAW_DATA_LENGTH ); + +/* Build the new generic error status block header */ +acpi_ghes_generic_error_status (block,ACPI_GEBS_UNCORRECTABLE , +0 ,0 , data_length, +ACPI_CPER_SEV_RECOVERABLE ); + +/* Build this new generic error data entry header */ +acpi_ghes_generic_error_data (block, cper->guid, +ACPI_CPER_SEV_RECOVERABLE ,0 ,0 , + cper->data_len, fru_id,0 ); + +/* Add CPER data */ +for (i =0 ; i < cper->data_len; i++) { +build_append_int_noprefix (block, cper->data[i],1 ); + } + +/* Write the generic error data entry into guest memory */ +cpu_physical_memory_write (error_block_addr, block->data, block->len); + +g_array_free (block, true); + +notifier_list_notify (&generic_error_notifiers,NULL ); +} +bool acpi_ghes_present (void ) {AcpiGedState *acpi_ged_state;
hw/acpi/ghes_cper.c +1 -1
@@ -39,7 +39,7 @@ void qmp_ghes_cper(CommonPlatformErrorRecord *qmp_cper,return ; } -/* TODO: call a function at ghes */ +ghes_record_cper_errors (&cper, errp,ACPI_GHES_NOTIFY_GPIO );g_free (cper.data); }
include/hw/acpi/ghes.h +3 -0
@@ -85,6 +85,9 @@ typedef struct AcpiGhesCper {size_t data_len; } AcpiGhesCper; +void ghes_record_cper_errors (AcpiGhesCper *cper,Error **errp, +uint32_t notify); +/** * acpi_ghes_present: Report whether ACPI GHES table is present *
Signature · 1 line
2.45.2
PATCH v5 7/7 scripts/ghes_inject: add a script to generate GHES error inject
In reply to Mauro Carvalho ChehabUsing the QMP GHESv2 API requires preparing a raw data array containing a CPER record.
Add a helper script with subcommands to prepare such data.
Currently, only ARM Processor error CPER record is supported.
--- MAINTAINERS | 3 + scripts/arm_processor_error.py | 352 +++++++++++++++++++++++++++++++++ scripts/ghes_inject.py | 59 ++++++ scripts/qmp_helper.py | 249 +++++++++++++++++++++++ 4 files changed, 663 insertions(+) create mode 100644 scripts/arm_processor_error.py create mode 100755 scripts/ghes_inject.py create mode 100644 scripts/qmp_helper.py
MAINTAINERS +3 -0
@@ -2081,6 +2081,9 @@ S: Maintained F: hw/arm/ghes_cper.c F: hw/acpi/ghes_cper_stub.c F: qapi/ghes-cper.json +F: scripts/ghes_inject.py +F: scripts/arm_processor_error.py +F: scripts/qmp_helper.py ppc4xx L: [email protected]
scripts/arm_processor_error.py new file +352 -0
352 lines not on this page · raw message
scripts/ghes_inject.py new file +59 -0
59 lines not on this page · raw message
scripts/qmp_helper.py new file +249 -0
249 lines not on this page · raw message
Signature · 1 line
2.45.2
v5 cover Add ACPI CPER firmware first error injection on ARM emulation
Testing OS kernel ACPI APEI CPER support is tricky, as one depends on having hardware with special-purpose BIOS and/or hardware.
With QEMU, it becomes a lot easier, as it can be done via QMP.
This series add support for injecting CPER records on ARM emulation.
The QEMU side changes add a QAPI able to do CPER error injection on ARM, with a raw data parameter, making it very flexible.
A script is provided at the final patch implementing support for ARM Processor CPER error injection according with ACPI 6.x and UEFI 2.9A/2.10 specs, via QMP.
Injecting such errors can be done using the provided script:
$ ./scripts/ghes_inject.py arm Error injected.
Produces a simple CPER register, properly handled by the Linux Kernel:
[ 794.983753] {4}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1
[ 794.984150] {4}[Hardware Error]: event severity: recoverable
[ 794.984391] {4}[Hardware Error]: Error 0, type: recoverable
[ 794.984652] {4}[Hardware Error]: section_type: ARM processor error
[ 794.984926] {4}[Hardware Error]: MIDR: 0x0000000000000000
[ 794.985184] {4}[Hardware Error]: running state: 0x0
[ 794.985411] {4}[Hardware Error]: Power State Coordination Interface state: 0
[ 794.985720] {4}[Hardware Error]: Error info structure 0:
[ 794.985960] {4}[Hardware Error]: num errors: 2
[ 794.986175] {4}[Hardware Error]: error_type: 0x02: cache error
[ 794.986442] {4}[Hardware Error]: error_info: 0x000000000091000f
[ 794.986755] {4}[Hardware Error]: transaction type: Data Access
[ 794.987027] {4}[Hardware Error]: cache error, operation type: Data write
[ 794.987310] {4}[Hardware Error]: cache level: 2
[ 794.987529] {4}[Hardware Error]: processor context not corrupted
[ 794.987867] [Firmware Warn]: GHES: Unhandled processor error type 0x02: cache errorMore complex use cases can be done, like:
$ ./scripts/ghes_inject.py arm --mpidr 0x444 --running --affinity 1 \ --error-info 12345678 --vendor 0x13,123,4,5,1 --ctx-array 0,1,2,3,4,5 \ -t cache tlb bus micro-arch tlb,micro-arch Error injected.
[ 899.181246] {5}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1
[ 899.181769] {5}[Hardware Error]: event severity: recoverable
[ 899.182069] {5}[Hardware Error]: Error 0, type: recoverable
[ 899.182370] {5}[Hardware Error]: section_type: ARM processor error
[ 899.182689] {5}[Hardware Error]: MIDR: 0x0000000000000000
[ 899.182980] {5}[Hardware Error]: Multiprocessor Affinity Register (MPIDR): 0x0000000000000000
[ 899.183395] {5}[Hardware Error]: error affinity level: 0
[ 899.183683] {5}[Hardware Error]: running state: 0x1
[ 899.183962] {5}[Hardware Error]: Power State Coordination Interface state: 0
[ 899.184332] {5}[Hardware Error]: Error info structure 0:
[ 899.184610] {5}[Hardware Error]: num errors: 2
[ 899.184864] {5}[Hardware Error]: error_type: 0x02: cache error
[ 899.185181] {5}[Hardware Error]: error_info: 0x0000000000bc614e
[ 899.185504] {5}[Hardware Error]: cache level: 2
[ 899.185771] {5}[Hardware Error]: processor context not corrupted
[ 899.186082] {5}[Hardware Error]: Error info structure 1:
[ 899.186366] {5}[Hardware Error]: num errors: 2
[ 899.186613] {5}[Hardware Error]: error_type: 0x04: TLB error
[ 899.186929] {5}[Hardware Error]: error_info: 0x000000000054007f
[ 899.187236] {5}[Hardware Error]: transaction type: Instruction
[ 899.187588] {5}[Hardware Error]: TLB error, operation type: Instruction fetch
[ 899.187962] {5}[Hardware Error]: TLB level: 1
[ 899.188209] {5}[Hardware Error]: processor context not corrupted
[ 899.188535] {5}[Hardware Error]: the error has not been corrected
[ 899.188853] {5}[Hardware Error]: PC is imprecise
[ 899.189114] {5}[Hardware Error]: Error info structure 2:
[ 899.189404] {5}[Hardware Error]: num errors: 2
[ 899.189653] {5}[Hardware Error]: error_type: 0x08: bus error
[ 899.189967] {5}[Hardware Error]: error_info: 0x00000080d6460fff
[ 899.190293] {5}[Hardware Error]: transaction type: Generic
[ 899.190611] {5}[Hardware Error]: bus error, operation type: Generic read (type of instruction or data request cannot be determined)
[ 899.191174] {5}[Hardware Error]: affinity level at which the bus error occurred: 1
[ 899.191563] {5}[Hardware Error]: processor context corrupted
[ 899.191872] {5}[Hardware Error]: the error has been corrected
[ 899.192185] {5}[Hardware Error]: PC is imprecise
[ 899.192445] {5}[Hardware Error]: Program execution can be restarted reliably at the PC associated with the error.
[ 899.192939] {5}[Hardware Error]: participation type: Local processor observed
[ 899.193324] {5}[Hardware Error]: request timed out
[ 899.193596] {5}[Hardware Error]: address space: External Memory Access
[ 899.193945] {5}[Hardware Error]: memory access attributes:0x20
[ 899.194273] {5}[Hardware Error]: access mode: secure
[ 899.194544] {5}[Hardware Error]: Error info structure 3:
[ 899.194838] {5}[Hardware Error]: num errors: 2
[ 899.195088] {5}[Hardware Error]: error_type: 0x10: micro-architectural error
[ 899.195456] {5}[Hardware Error]: error_info: 0x0000000078da03ff
[ 899.195782] {5}[Hardware Error]: Error info structure 4:
[ 899.196070] {5}[Hardware Error]: num errors: 2
[ 899.196331] {5}[Hardware Error]: error_type: 0x14: TLB error|micro-architectural error
[ 899.196733] {5}[Hardware Error]: Context info structure 0:
[ 899.197024] {5}[Hardware Error]: register context type: AArch64 EL1 context registers
[ 899.197427] {5}[Hardware Error]: 00000000: 00000000 00000000
[ 899.197741] {5}[Hardware Error]: Vendor specific error info has 5 bytes:
[ 899.198096] {5}[Hardware Error]: 00000000: 13 7b 04 05 01 .{...
[ 899.198610] [Firmware Warn]: GHES: Unhandled processor error type 0x02: cache error
[ 899.199000] [Firmware Warn]: GHES: Unhandled processor error type 0x04: TLB error
[ 899.199388] [Firmware Warn]: GHES: Unhandled processor error type 0x08: bus error
[ 899.199767] [Firmware Warn]: GHES: Unhandled processor error type 0x10: micro-architectural error
[ 899.200194] [Firmware Warn]: GHES: Unhandled processor error type 0x14: TLB error|micro-architectural error---
v5:
- CPER guid is now passing as string;
- raw-data is now passed with base64 encode;
- Removed several GPIO left-overs from arm/virt.c changes;
- Lots of cleanups and improvements at the error injection script. It now better handles QMP dialog and doesn't print debug messages. Also, code was split on two modules, to make easier to add more error injection commands.
v4:
- CPER generation moved to happen outside QEMU;
- One patch adding support for mpidr query was removed.
v3:
- patch 1 cleanups with some comment changes and adding another place where the poweroff GPIO define should be used. No changes on other patches (except due to conflict resolution).
v2:
- added a new patch using a define for GPIO power pin;
- patch 2 changed to also use a define for generic error GPIO pin;
- a couple cleanups at patch 2 removing uneeded else clauses.
Jonathan Cameron (1):
acpi/ghes: Support GPIO error source
Mauro Carvalho Chehab (6):
arm/virt: place power button pin number on a define acpi/generic_event_device: add an APEI error device arm/virt: Wire up GPIO error source for ACPI / GHES qapi/ghes-cper: add an interface to do generic CPER error injection acpi/ghes: add support for generic error injection via QAPI scripts/ghes_inject: add a script to generate GHES error inject
MAINTAINERS | 10 + hw/acpi/Kconfig | 5 + hw/acpi/generic_event_device.c | 17 ++ hw/acpi/ghes.c | 178 +++++++++++-- hw/acpi/ghes_cper.c | 45 ++++ hw/acpi/ghes_cper_stub.c | 18 ++ hw/acpi/meson.build | 2 + hw/arm/Kconfig | 5 + hw/arm/virt-acpi-build.c | 7 +- hw/arm/virt.c | 23 +- include/hw/acpi/acpi_dev_interface.h | 1 + include/hw/acpi/generic_event_device.h | 3 + include/hw/acpi/ghes.h | 16 +- include/hw/arm/virt.h | 4 + qapi/ghes-cper.json | 55 ++++ qapi/meson.build | 1 + qapi/qapi-schema.json | 1 + scripts/arm_processor_error.py | 352 +++++++++++++++++++++++++ scripts/ghes_inject.py | 59 +++++ scripts/qmp_helper.py | 249 +++++++++++++++++ 20 files changed, 1026 insertions(+), 25 deletions(-) create mode 100644 hw/acpi/ghes_cper.c create mode 100644 hw/acpi/ghes_cper_stub.c create mode 100644 qapi/ghes-cper.json create mode 100644 scripts/arm_processor_error.py create mode 100755 scripts/ghes_inject.py create mode 100644 scripts/qmp_helper.py
Signature · 1 line
2.45.2
Re: [PATCH v5 2/7] acpi/generic_event_device: add an APEI error device
In reply to Mauro Carvalho ChehabQuoted 6 lines · On Fri, 2 Aug 2024 23:43:57 +0200 Mauro Carvalho Chehab…
Adds a Generic Event Device to handle generic hardware error events, supporting General Purpose Event (GPE) as specified at ACPI 6.5 specification at 18.3.2.7.2:
https://uefi.org/specs/ACPI/6.5/18_Platform_Error_Interfaces.html#event-notification-for-generic-error-sources
using HID PNP0C33.
Quoted 6 lines
The PNP0C33 device is used to report hardware errors to the bios via ACPI APEI Generic Hardware Error Source (GHES).
Co-authored-by Mauro Carvalho Chehab <[email protected]>Co-authored-by Jonathan Cameron <[email protected]>Cc Jonathan Cameron <[email protected]>
Much nicer with a GED event.
Happy to give SoB on this as you requested due to changes.
One minor comment though.
The pnp0c33 device isn't technically coupled to the generic_event_device. Perhaps that should be in aml_build.h/.c instead of where you have it here?
Maybe we can move it later though if anyone implements non GED signalling?
Jonathan
Quoted 95 lines
Signed-off-by Mauro Carvalho Chehab <[email protected]>--- hw/acpi/generic_event_device.c | 17 +++++++++++++++++ include/hw/acpi/acpi_dev_interface.h | 1 + include/hw/acpi/generic_event_device.h | 3 +++ 3 files changed, 21 insertions(+)hw/acpi/generic_event_device.c +17
-0@@ -26,6 +26,7 @@ static const uint32_t ged_supported_events[] = {ACPI_GED_PWR_DOWN_EVT ,ACPI_GED_NVDIMM_HOTPLUG_EVT ,ACPI_GED_CPU_HOTPLUG_EVT , + ACPI_GED_ERROR_EVT };/* @@ -116,6 +117,11 @@ void build_ged_aml(Aml *table, const char *name, HotplugHandler *hotplug_dev,aml_notify (aml_name (ACPI_POWER_BUTTON_DEVICE ), aml_int(0x80)));break ; +case ACPI_GED_ERROR_EVT : +aml_append (if_ctx, +aml_notify (aml_name (ACPI_APEI_ERROR_DEVICE ), +aml_int (0x80 ))); +break ;case ACPI_GED_NVDIMM_HOTPLUG_EVT : aml_append(if_ctx, aml_notify(aml_name("\\_SB.NVDR"),@@ -153,6 +159,15 @@ void acpi_dsdt_add_power_button(Aml *scope)aml_append (scope, dev); } +void acpi_dsdt_add_error_device (Aml *scope) +{ +Aml *dev =aml_device (ACPI_APEI_ERROR_DEVICE ); +aml_append (dev,aml_name_decl ("_HID" ,aml_string ("PNP0C33" ))); +aml_append (dev,aml_name_decl ("_UID" ,aml_int (0 ))); +aml_append (dev,aml_name_decl ("_STA" ,aml_int (0xF ))); +aml_append (scope, dev); +} +/* Memory read by the GED _EVT AML dynamic method */ static uint64_t ged_evt_read (void *opaque,hwaddr addr,unsigned size) {@@ -295,6 +310,8 @@ static void acpi_ged_send_event(AcpiDeviceIf *adev, AcpiEventStatusBits ev) sel =ACPI_GED_MEM_HOTPLUG_EVT ; }else if (ev &ACPI_POWER_DOWN_STATUS ) { sel =ACPI_GED_PWR_DOWN_EVT ; + }else if (ev &ACPI_GENERIC_ERROR ) { + sel =ACPI_GED_ERROR_EVT ; }else if (ev &ACPI_NVDIMM_HOTPLUG_STATUS ) { sel =ACPI_GED_NVDIMM_HOTPLUG_EVT ; }else if (ev &ACPI_CPU_HOTPLUG_STATUS ) {include/hw/acpi/acpi_dev_interface.h +1
-0@@ -13,6 +13,7 @@ typedef enum {ACPI_NVDIMM_HOTPLUG_STATUS =16 ,ACPI_VMGENID_CHANGE_STATUS =32 ,ACPI_POWER_DOWN_STATUS =64 , +ACPI_GENERIC_ERROR =128 , } AcpiEventStatusBits;#define TYPE_ACPI_DEVICE_IF "acpi-device-interface"include/hw/acpi/generic_event_device.h +3
-0@@ -66,6 +66,7 @@#include "qom/object.h" #define ACPI_POWER_BUTTON_DEVICE "PWRB" +#define ACPI_APEI_ERROR_DEVICE "GEDD"#define TYPE_ACPI_GED "acpi-ged"OBJECT_DECLARE_SIMPLE_TYPE (AcpiGedState,ACPI_GED )@@ -98,6 +99,7 @@ OBJECT_DECLARE_SIMPLE_TYPE(AcpiGedState, ACPI_GED)#define ACPI_GED_PWR_DOWN_EVT 0x2#define ACPI_GED_NVDIMM_HOTPLUG_EVT 0x4#define ACPI_GED_CPU_HOTPLUG_EVT 0x8 +#define ACPI_GED_ERROR_EVT 0x10 typedef struct GEDState { MemoryRegion evt;@@ -120,5 +122,6 @@ struct AcpiGedState {void build_ged_aml (Aml *table,const char * name,HotplugHandler *hotplug_dev,uint32_t ged_irq,AmlRegionSpace rs,hwaddr ged_base);void acpi_dsdt_add_power_button (Aml *scope); +void acpi_dsdt_add_error_device (Aml *scope);#endif
Re: [PATCH v5 3/7] arm/virt: Wire up GPIO error source for ACPI / GHES
In reply to Mauro Carvalho ChehabOn Fri, 2 Aug 2024 23:43:58 +0200
Mauro Carvalho Chehab <[email protected]> wrote:
Do we need to rename this now there is a GED involved? Is it even technically a GPIO any more?
Spec says in 18.3.2.7
HW-reduced ACPI platforms signal the error using a GPIO interrupt or another interrupt declared under a generic event device (Interrupt-signaled ACPI events) and goes on to say that a _CRS entry is used to list the interrupt.
Give the Generic Event Device has a _CRS
with aml_interrupt() as the type I think we should even have the hest entry say it's an interrupt (external?) rather than a gpio.
Quoted 9 lines
Adds support to ARM virtualization to allow handling a General Purpose Event (GPE) via GED error device.
It is aligned with Linux Kernel patch:
https://lore.kernel.org/lkml/[email protected]/Co-authored-by Mauro Carvalho Chehab <[email protected]>Co-authored-by Jonathan Cameron <[email protected]>Cc Jonathan Cameron <[email protected]>
Again, more or less fine with this
to go with that co-auth
Quoted 109 lines
Signed-off-by Mauro Carvalho Chehab <[email protected]>--- hw/acpi/ghes.c | 3 +++ hw/arm/virt-acpi-build.c | 1 + hw/arm/virt.c | 16 +++++++++++++++- include/hw/acpi/ghes.h | 3 +++ include/hw/arm/virt.h | 1 + 5 files changed, 23 insertions(+), 1 deletion(-)hw/acpi/ghes.c +3
-0@@ -444,6 +444,9 @@ int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address)return ret; } +NotifierList generic_error_notifiers = +NOTIFIER_LIST_INITIALIZER (error_device_notifiers); +bool acpi_ghes_present (void ) {AcpiGedState *acpi_ged_state;hw/arm/virt-acpi-build.c +1
-0@@ -858,6 +858,7 @@ build_dsdt(GArray *table_data, BIOSLinker *linker, VirtMachineState *vms) }acpi_dsdt_add_power_button (scope); +acpi_dsdt_add_error_device (scope);#ifdef CONFIG_TPM acpi_dsdt_add_tpm (scope, vms);#endif hw/arm/virt.c +15
-1@@ -73,6 +73,7 @@#include "standard-headers/linux/input.h" #include "hw/arm/smmuv3.h" #include "hw/acpi/acpi.h" +#include "hw/acpi/ghes.h" #include "target/arm/cpu-qom.h" #include "target/arm/internals.h" #include "target/arm/multiprocessing.h" @@ -677,7 +678,7 @@ static inline DeviceState *create_acpi_ged(VirtMachineState *vms)DeviceState *dev;MachineState *ms =MACHINE (vms);int irq = vms->irqmap[VIRT_ACPI_GED ]; -uint32_t event =ACPI_GED_PWR_DOWN_EVT ; +uint32_t event =ACPI_GED_PWR_DOWN_EVT |ACPI_GED_ERROR_EVT ;if (ms->ram_slots) { event |=ACPI_GED_MEM_HOTPLUG_EVT ;@@ -1009,6 +1010,15 @@ static void virt_powerdown_req(Notifier *n, void *opaque) } } +static void virt_generic_error_req (Notifier *n,void *opaque) +{ +VirtMachineState *s =container_of (n, VirtMachineState, generic_error_notifier); + +if (s->acpi_dev) { +acpi_send_event (s->acpi_dev,ACPI_GENERIC_ERROR ); + } +} +static void create_gpio_keys (char *fdt,DeviceState *pl061_dev,uint32_t phandle) {@@ -2397,6 +2407,10 @@ static void machvirt_init(MachineState *machine) vms->powerdown_notifier.notify = virt_powerdown_req;qemu_register_powerdown_notifier (&vms->powerdown_notifier); + vms->generic_error_notifier.notify = virt_generic_error_req; +notifier_list_add (&generic_error_notifiers, + &vms->generic_error_notifier); +/* Create mmio transports, so the user can create virtio backends * (which will be automatically plugged in to the transports). If * no backend is created the transport will just sit harmlessly idle. include/hw/acpi/ghes.h +3
-0@@ -23,6 +23,9 @@#define ACPI_GHES_H #include "hw/acpi/bios-linker-loader.h" +#include "qemu/notify.h" + +extern NotifierList generic_error_notifiers;/* * Values for Hardware Error Notification Type field include/hw/arm/virt.h +1
-0@@ -175,6 +175,7 @@ struct VirtMachineState {DeviceState *gic;DeviceState *acpi_dev;Notifier powerdown_notifier; +Notifier generic_error_notifier;PCIBus *bus;char *oem_id;char *oem_table_id;
Re: [PATCH v5 4/7] acpi/ghes: Support GPIO error source
In reply to Mauro Carvalho ChehabQuoted 3 lines · On Fri, 2 Aug 2024 23:43:59 +0200 Mauro Carvalho Chehab…
From: Jonathan Cameron <[email protected]>
Add error notification to GHES v2 using the GPIO source.
The gpio / external interrupt follows through.
Quoted 81 lines
[mchehab: do some cleanups at ACPI_HEST_SRC_ID_* checks]
Signed-off-by Jonathan Cameron <[email protected]>Signed-off-by Mauro Carvalho Chehab <[email protected]>--- hw/acpi/ghes.c | 16 ++++++++++------ include/hw/acpi/ghes.h | 3 ++- 2 files changed, 12 insertions(+), 7 deletions(-)hw/acpi/ghes.c +10
-6@@ -34,8 +34,8 @@/* The max size in bytes for one error block */ #define ACPI_GHES_MAX_RAW_DATA_LENGTH (1 * KiB) -/* Now only support ARMv8 SEA notification type error source */ -#define ACPI_GHES_ERROR_SOURCE_COUNT 1 +/* Support ARMv8 SEA notification type error source and GPIO interrupt. */ +#define ACPI_GHES_ERROR_SOURCE_COUNT 2/* Generic Hardware Error Source version 2 */ #define ACPI_GHES_SOURCE_GENERIC_ERROR_V2 10@@ -290,6 +290,9 @@ void build_ghes_error_table(GArray *hardware_errors, BIOSLinker *linker)static void build_ghes_v2 (GArray *table_data,int source_id,BIOSLinker *linker) {uint64_t address_offset; + +assert (source_id <ACPI_HEST_SRC_ID_RESERVED ); +/* * Type: * Generic Hardware Error Source version 2(GHESv2 - Type 10) @@ -327,6 +330,9 @@ static void build_ghes_v2(GArray *table_data, int source_id, BIOSLinker *linker)*/ build_ghes_hw_error_notification (table_data,ACPI_GHES_NOTIFY_SEA );break ; +case ACPI_HEST_SRC_ID_GPIO : +build_ghes_hw_error_notification (table_data,ACPI_GHES_NOTIFY_GPIO ); +break ;default :error_report ("Not support this error source" );abort ();@@ -370,6 +376,7 @@ void acpi_build_hest(GArray *table_data, BIOSLinker *linker,/* Error Source Count */ build_append_int_noprefix (table_data,ACPI_GHES_ERROR_SOURCE_COUNT ,4 );build_ghes_v2 (table_data,ACPI_HEST_SRC_ID_SEA , linker); +build_ghes_v2 (table_data,ACPI_HEST_SRC_ID_GPIO , linker);acpi_table_end (linker, &table); }@@ -406,10 +413,7 @@ int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address) start_addr =le64_to_cpu (ags->ghes_addr_le);if (physical_address) { - -if (source_id <ACPI_HEST_SRC_ID_RESERVED ) { - start_addr += source_id *sizeof (uint64_t ); - } + start_addr += source_id *sizeof (uint64_t );cpu_physical_memory_read (start_addr, &error_block_addr,sizeof (error_block_addr));include/hw/acpi/ghes.h +2
-1@@ -59,9 +59,10 @@ enum AcpiGhesNotifyType { ACPI_GHES_NOTIFY_RESERVED = 12 }; +/* Those are used as table indexes when building GHES tables */ enum {ACPI_HEST_SRC_ID_SEA =0 , -/* future ids go here */ +ACPI_HEST_SRC_ID_GPIO ,ACPI_HEST_SRC_ID_RESERVED , };
Re: [PATCH v5 5/7] qapi/ghes-cper: add an interface to do generic CPER error injection
In reply to Mauro Carvalho ChehabQuoted 6 lines · On Fri, 2 Aug 2024 23:44:00 +0200 Mauro Carvalho Chehab…
Creates a QMP command to be used for generic ACPI APEI hardware error injection (HEST) via GHESv2.
The actual GHES code will be added at the followup patch.
Signed-off-by Mauro Carvalho Chehab <[email protected]>
Looks good to me.
Re: [PATCH v5 6/7] acpi/ghes: add support for generic error injection via QAPI
In reply to Mauro Carvalho ChehabQuoted 7 lines · On Fri, 2 Aug 2024 23:44:01 +0200 Mauro Carvalho Chehab…
Provide a generic interface for error injection via GHESv2.
This patch is co-authored:
- original ghes logic to inject a simple ARM record by Shiju Jose;
- generic logic to handle block addresses by Jonathan Cameron;
- generic GHESv2 error inject by Mauro Carvalho Chehab;
Quoted 6 lines
Co-authored-by Jonathan Cameron <[email protected]>Co-authored-by Shiju Jose <[email protected]>Co-authored-by Mauro Carvalho Chehab <[email protected]>Cc Jonathan Cameron <[email protected]>Cc Shiju Jose <[email protected]>Signed-off-by Mauro Carvalho Chehab <[email protected]>
Looks fine to me.
Feel free to put in my SoB on the resulting co-auth
if appropriate? Does this work same as kernel co-developed-by?
Quoted 34 lines
hw/acpi/ghes.c +34
-0+void ghes_record_cper_errors (AcpiGhesCper *cper,Error **errp, +uint32_t notify) +{ +int read_ack =0 ; +uint32_t i; +uint64_t read_ack_addr =0 ; +uint64_t error_block_addr =0 ; +uint32_t data_length; +GArray *block; + +if (!ghes_get_addr (notify, &error_block_addr, &read_ack_addr)) { +error_setg (errp,"GHES: Invalid error block/ack address(es)" ); +return ; + } + +cpu_physical_memory_read (read_ack_addr, + &read_ack,sizeof (uint64_t )); + +/* zero means OSPM does not acknowledge the error */ +if (!read_ack) { +error_setg (errp, +"Last CPER record was not acknowledged yet" ); + read_ack =1 ; +cpu_physical_memory_write (read_ack_addr, + &read_ack,sizeof (uint64_t )); +return ; + } + + read_ack =cpu_to_le64 (0 ); +cpu_physical_memory_write (read_ack_addr, + &read_ack,sizeof (uint64_t )); + +/* Build CPER record */ +
hw/acpi/ghes.c int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address) · line 561
Quoted 10 lines
hw/acpi/ghes.c +10
-0+/* +* Invalid fru id: ACPI 4.0: 17.3.2.6.1 Generic Error Data, +* Table 17-13 Generic Error Data Entry +*/ +QemuUUID fru_id = {}; + + block =g_array_new (false, true/* clear */ ,1 ); + data_length =ACPI_GHES_DATA_LENGTH + cper->data_len; + +/*
Odd formatting.
Quoted 32 lines
hw/acpi/ghes.c +29
-0+* It should not run out of the preallocated memory if +* adding a new generic error data entry +*/ +assert ((data_length +ACPI_GHES_GESB_SIZE ) <= +ACPI_GHES_MAX_RAW_DATA_LENGTH ); + +/* Build the new generic error status block header */ +acpi_ghes_generic_error_status (block,ACPI_GEBS_UNCORRECTABLE , +0 ,0 , data_length, +ACPI_CPER_SEV_RECOVERABLE ); + +/* Build this new generic error data entry header */ +acpi_ghes_generic_error_data (block, cper->guid, +ACPI_CPER_SEV_RECOVERABLE ,0 ,0 , + cper->data_len, fru_id,0 ); + +/* Add CPER data */ +for (i =0 ; i < cper->data_len; i++) { +build_append_int_noprefix (block, cper->data[i],1 ); + } + +/* Write the generic error data entry into guest memory */ +cpu_physical_memory_write (error_block_addr, block->data, block->len); + +g_array_free (block, true); + +notifier_list_notify (&generic_error_notifiers,NULL ); +} +bool acpi_ghes_present (void ) {AcpiGedState *acpi_ged_state;
Re: [PATCH v5 2/7] acpi/generic_event_device: add an APEI error device
In reply to Jonathan CameronEm Mon, 5 Aug 2024 17:39:46 +0100
Jonathan Cameron <[email protected]> escreveu:
Quoted 19 lines
Quoted 6 lines · On Fri, 2 Aug 2024 23:43:57 +0200 Mauro Carvalho Chehab…
Adds a Generic Event Device to handle generic hardware error events, supporting General Purpose Event (GPE) as specified at ACPI 6.5 specification at 18.3.2.7.2:
https://uefi.org/specs/ACPI/6.5/18_Platform_Error_Interfaces.html#event-notification-for-generic-error-sources
using HID PNP0C33.Quoted 6 lines
The PNP0C33 device is used to report hardware errors to the bios via ACPI APEI Generic Hardware Error Source (GHES).
Co-authored-by Mauro Carvalho Chehab <[email protected]>Co-authored-by Jonathan Cameron <[email protected]>Cc Jonathan Cameron <[email protected]>Much nicer with a GED event.
Happy to give SoB on this as you requested due to changes.
Quoted 8 lines
Signed-off-by Jonathan Cameron <[email protected]>One minor comment though.
The pnp0c33 device isn't technically coupled to thegeneric_event_device. Perhaps that should be in aml_build.h/.c instead of where you have it here?Maybe we can move it later though if anyone implements non GED signalling?
I opted to place it there at hw/acpi/generic_event_device.c, just after PNP0C0C, e. g.:
void acpi_dsdt_add_power_button(Aml *scope)
{
Aml *dev = aml_device(ACPI_POWER_BUTTON_DEVICE);
aml_append(dev, aml_name_decl("_HID", aml_string("PNP0C0C")));
aml_append(dev, aml_name_decl("_UID", aml_int(0)));
aml_append(scope, dev);
}
void acpi_dsdt_add_error_device(Aml *scope)
{
Aml *dev = aml_device(ACPI_APEI_ERROR_DEVICE);
aml_append(dev, aml_name_decl("_HID", aml_string("PNP0C33")));
aml_append(dev, aml_name_decl("_UID", aml_int(0)));
aml_append(dev, aml_name_decl("_STA", aml_int(0xF)));
aml_append(scope, dev);
}IMO this way it will be kept closer to other PNP devices. If this starts to grow, then some later cleanup could move those to some separate file, but, as now there are just two, I would just keep both there at GED file.
Quoted 98 lines
Jonathan
Quoted 94 lines
Signed-off-by Mauro Carvalho Chehab <[email protected]>--- hw/acpi/generic_event_device.c | 17 +++++++++++++++++ include/hw/acpi/acpi_dev_interface.h | 1 + include/hw/acpi/generic_event_device.h | 3 +++ 3 files changed, 21 insertions(+)hw/acpi/generic_event_device.c +17
-0@@ -26,6 +26,7 @@ static const uint32_t ged_supported_events[] = {ACPI_GED_PWR_DOWN_EVT ,ACPI_GED_NVDIMM_HOTPLUG_EVT ,ACPI_GED_CPU_HOTPLUG_EVT , + ACPI_GED_ERROR_EVT };/* @@ -116,6 +117,11 @@ void build_ged_aml(Aml *table, const char *name, HotplugHandler *hotplug_dev,aml_notify (aml_name (ACPI_POWER_BUTTON_DEVICE ), aml_int(0x80)));break ; +case ACPI_GED_ERROR_EVT : +aml_append (if_ctx, +aml_notify (aml_name (ACPI_APEI_ERROR_DEVICE ), +aml_int (0x80 ))); +break ;case ACPI_GED_NVDIMM_HOTPLUG_EVT : aml_append(if_ctx, aml_notify(aml_name("\\_SB.NVDR"),@@ -153,6 +159,15 @@ void acpi_dsdt_add_power_button(Aml *scope)aml_append (scope, dev); } +void acpi_dsdt_add_error_device (Aml *scope) +{ +Aml *dev =aml_device (ACPI_APEI_ERROR_DEVICE ); +aml_append (dev,aml_name_decl ("_HID" ,aml_string ("PNP0C33" ))); +aml_append (dev,aml_name_decl ("_UID" ,aml_int (0 ))); +aml_append (dev,aml_name_decl ("_STA" ,aml_int (0xF ))); +aml_append (scope, dev); +} +/* Memory read by the GED _EVT AML dynamic method */ static uint64_t ged_evt_read (void *opaque,hwaddr addr,unsigned size) {@@ -295,6 +310,8 @@ static void acpi_ged_send_event(AcpiDeviceIf *adev, AcpiEventStatusBits ev) sel =ACPI_GED_MEM_HOTPLUG_EVT ; }else if (ev &ACPI_POWER_DOWN_STATUS ) { sel =ACPI_GED_PWR_DOWN_EVT ; + }else if (ev &ACPI_GENERIC_ERROR ) { + sel =ACPI_GED_ERROR_EVT ; }else if (ev &ACPI_NVDIMM_HOTPLUG_STATUS ) { sel =ACPI_GED_NVDIMM_HOTPLUG_EVT ; }else if (ev &ACPI_CPU_HOTPLUG_STATUS ) {include/hw/acpi/acpi_dev_interface.h +1
-0@@ -13,6 +13,7 @@ typedef enum {ACPI_NVDIMM_HOTPLUG_STATUS =16 ,ACPI_VMGENID_CHANGE_STATUS =32 ,ACPI_POWER_DOWN_STATUS =64 , +ACPI_GENERIC_ERROR =128 , } AcpiEventStatusBits;#define TYPE_ACPI_DEVICE_IF "acpi-device-interface"include/hw/acpi/generic_event_device.h +3
-0@@ -66,6 +66,7 @@#include "qom/object.h" #define ACPI_POWER_BUTTON_DEVICE "PWRB" +#define ACPI_APEI_ERROR_DEVICE "GEDD"#define TYPE_ACPI_GED "acpi-ged"OBJECT_DECLARE_SIMPLE_TYPE (AcpiGedState,ACPI_GED )@@ -98,6 +99,7 @@ OBJECT_DECLARE_SIMPLE_TYPE(AcpiGedState, ACPI_GED)#define ACPI_GED_PWR_DOWN_EVT 0x2#define ACPI_GED_NVDIMM_HOTPLUG_EVT 0x4#define ACPI_GED_CPU_HOTPLUG_EVT 0x8 +#define ACPI_GED_ERROR_EVT 0x10 typedef struct GEDState { MemoryRegion evt;@@ -120,5 +122,6 @@ struct AcpiGedState {void build_ged_aml (Aml *table,const char * name,HotplugHandler *hotplug_dev,uint32_t ged_irq,AmlRegionSpace rs,hwaddr ged_base);void acpi_dsdt_add_power_button (Aml *scope); +void acpi_dsdt_add_error_device (Aml *scope);
Quoted 2 lines
include/hw/acpi/generic_event_device.h struct AcpiGedState { · line 127
Quoted 1 line
include/hw/acpi/generic_event_device.h +0
-0#endif
Thanks,
Mauro
Re: [PATCH v5 3/7] arm/virt: Wire up GPIO error source for ACPI / GHES
In reply to Jonathan CameronEm Mon, 5 Aug 2024 17:54:00 +0100
Jonathan Cameron <[email protected]> escreveu:
Quoted 12 lines
On Fri, 2 Aug 2024 23:43:58 +0200
Mauro Carvalho Chehab <[email protected]> wrote:Do we need to rename this now there is a GED involved? Is it even technically a GPIO any more?
Spec says in 18.3.2.7
HW-reduced ACPI platforms signal the error using a GPIO interrupt or another interrupt declared under a generic event device (Interrupt-signaled ACPI events) and goes on to say that a_CRSentry is used to list the interrupt.
Quoted 4 lines
Give the Generic Event Device has a
_CRS
withaml_interrupt()as the type I think we should even have the hest entry say it's an interrupt (external?) rather than a gpio.
True. I'll change patch description to:
arm/virt: Wire up a GED error device for ACPI / GHES
Adds support to ARM virtualization to allow handling a General Purpose Event (GPE) via GED error device.
It is aligned with Linux Kernel patch:
https://lore.kernel.org/lkml/[email protected]/
As the spec at
https://uefi.org/specs/ACPI/6.5/18_Platform_Error_Interfaces.html#event-notification-for-generic-error-sources
revers to it as:
"The implementation of Event notification requires the platform
to define a device with PNP ID PNP0C33 in the ACPI namespace, referred to as the error device."
Quoted 6 lines
Quoted 6 lines
Adds support to ARM virtualization to allow handling a General Purpose Event (GPE) via GED error device.
It is aligned with Linux Kernel patch:
https://lore.kernel.org/lkml/[email protected]/
Quoted 7 lines
Quoted 3 lines
Co-authored-by Mauro Carvalho Chehab <[email protected]>Co-authored-by Jonathan Cameron <[email protected]>Cc Jonathan Cameron <[email protected]>Again, more or less fine with this
Signed-off-by Jonathan Cameron <[email protected]>to go with that co-auth
Thanks!
Mauro
Re: [PATCH v5 4/7] acpi/ghes: Support GPIO error source
In reply to Jonathan CameronEm Mon, 5 Aug 2024 17:56:17 +0100
Jonathan Cameron <[email protected]> escreveu:
Quoted 8 lines
Quoted 3 lines · On Fri, 2 Aug 2024 23:43:59 +0200 Mauro Carvalho Chehab…
From: Jonathan Cameron <[email protected]>
Add error notification to GHES v2 using the GPIO source.
The gpio / external interrupt follows through.
True. As session 18.3.2.7 of the spec says:
The OSPM evaluates the control method associated with this event as indicated in The Event Method for Handling GPIO Signaled Events and The Event Method for Handling Interrupt Signaled Events.
E. g. defining two methods:
- GED GPIO;
- GED interrupt
I'm doing this rename:
ACPI_HEST_SRC_ID_GPIO -> ACPI_HEST_SRC_ID_GED_INT
To clearly state what it is implemented there.
I'm also changing patch description to:
acpi/ghes: Add support for General Purpose Event
As a GED error device is now defined, add another type of notification.
Add error notification to GHES v2 using the GPIO source.
[mchehab: do some cleanups at ACPI_HEST_SRC_ID_* checks and
rename HEST event to better identify GED interrupt OSPM]
Regards,
Mauro
Re: [PATCH v5 2/7] acpi/generic_event_device: add an APEI error device
In reply to Mauro Carvalho ChehabOn Fri, 2 Aug 2024 23:43:57 +0200
Mauro Carvalho Chehab <[email protected]> wrote:
subj: s/APEI/error/
to match spec
Quoted 1 line
Adds a Generic Event Device to handle generic hardware error
^^^^^
Did you want to say: Error ?
Quoted 1 line
events, supporting General Purpose Event (GPE) as specified at
even though GPE can be used (for example with non hw-reduced pc/q35 machines), it's not what you are doing here.
s/General Purpose Event (GPE)/generic event device/
Quoted 6 lines
ACPI 6.5 specification at 18.3.2.7.2:
https://uefi.org/specs/ACPI/6.5/18_Platform_Error_Interfaces.html#event-notification-for-generic-error-sources
using HID PNP0C33.The PNP0C33 device is used to report hardware errors to the bios via ACPI APEI Generic Hardware Error Source (GHES).
event is sent not to 'bios' but to the guest, OSPM in spec language
Quoted 36 lines
Co-authored-by Mauro Carvalho Chehab <[email protected]>Co-authored-by Jonathan Cameron <[email protected]>Cc Jonathan Cameron <[email protected]>Signed-off-by Mauro Carvalho Chehab <[email protected]>--- hw/acpi/generic_event_device.c | 17 +++++++++++++++++ include/hw/acpi/acpi_dev_interface.h | 1 + include/hw/acpi/generic_event_device.h | 3 +++ 3 files changed, 21 insertions(+)hw/acpi/generic_event_device.c +6
-0@@ -26,6 +26,7 @@ static const uint32_t ged_supported_events[] = {ACPI_GED_PWR_DOWN_EVT ,ACPI_GED_NVDIMM_HOTPLUG_EVT ,ACPI_GED_CPU_HOTPLUG_EVT , + ACPI_GED_ERROR_EVT };/* @@ -116,6 +117,11 @@ void build_ged_aml(Aml *table, const char *name, HotplugHandler *hotplug_dev,aml_notify (aml_name (ACPI_POWER_BUTTON_DEVICE ), aml_int(0x80)));break ; +case ACPI_GED_ERROR_EVT : +aml_append (if_ctx, +aml_notify (aml_name (ACPI_APEI_ERROR_DEVICE ), +aml_int (0x80 ))); +break ;case ACPI_GED_NVDIMM_HOTPLUG_EVT : aml_append(if_ctx, aml_notify(aml_name("\\_SB.NVDR"),
hw/acpi/generic_event_device.c void acpi_dsdt_add_power_button(Aml *scope) · line 160
Quoted 2 lines
hw/acpi/generic_event_device.c +0
-0@@ -153,6 +159,15 @@ void acpi_dsdt_add_power_button(Aml *scope)aml_append (scope, dev); }
put mandatory comment here, in format: earliest spec rev + chapter
hw/acpi/generic_event_device.c void acpi_dsdt_add_power_button(Aml *scope) · line 162
Quoted 1 line
hw/acpi/generic_event_device.c +1
-0+void acpi_dsdt_add_error_device (Aml *scope)
s/void acpi_dsdt_add_error_device/Aml* aml_error_device()/
hw/acpi/generic_event_device.c void acpi_dsdt_add_power_button(Aml *scope) · line 167
Quoted 6 lines
hw/acpi/generic_event_device.c +5
-0+{ +Aml *dev =aml_device (ACPI_APEI_ERROR_DEVICE ); +aml_append (dev,aml_name_decl ("_HID" ,aml_string ("PNP0C33" ))); +aml_append (dev,aml_name_decl ("_UID" ,aml_int (0 ))); +aml_append (dev,aml_name_decl ("_STA" ,aml_int (0xF )));
not necessary unless you want set it anything else beside 0xF
hw/acpi/generic_event_device.c void acpi_dsdt_add_power_button(Aml *scope) · line 169
Quoted 2 lines
hw/acpi/generic_event_device.c +2
-0+aml_append (scope, dev); +}
and maybe move the function to aml-build.c
Quoted 29 lines
hw/acpi/generic_event_device.c +2
-0/* Memory read by the GED _EVT AML dynamic method */ static uint64_t ged_evt_read (void *opaque,hwaddr addr,unsigned size) {@@ -295,6 +310,8 @@ static void acpi_ged_send_event(AcpiDeviceIf *adev, AcpiEventStatusBits ev) sel =ACPI_GED_MEM_HOTPLUG_EVT ; }else if (ev &ACPI_POWER_DOWN_STATUS ) { sel =ACPI_GED_PWR_DOWN_EVT ; + }else if (ev &ACPI_GENERIC_ERROR ) { + sel =ACPI_GED_ERROR_EVT ; }else if (ev &ACPI_NVDIMM_HOTPLUG_STATUS ) { sel =ACPI_GED_NVDIMM_HOTPLUG_EVT ; }else if (ev &ACPI_CPU_HOTPLUG_STATUS ) {include/hw/acpi/acpi_dev_interface.h +1
-0@@ -13,6 +13,7 @@ typedef enum {ACPI_NVDIMM_HOTPLUG_STATUS =16 ,ACPI_VMGENID_CHANGE_STATUS =32 ,ACPI_POWER_DOWN_STATUS =64 , +ACPI_GENERIC_ERROR =128 , } AcpiEventStatusBits;#define TYPE_ACPI_DEVICE_IF "acpi-device-interface"include/hw/acpi/generic_event_device.h +0
-0
include/hw/acpi/generic_event_device.h line 70
Quoted 5 lines
include/hw/acpi/generic_event_device.h +1
-0@@ -66,6 +66,7 @@#include "qom/object.h" #define ACPI_POWER_BUTTON_DEVICE "PWRB" +#define ACPI_APEI_ERROR_DEVICE "GEDD"
perhaps aml_build.h would be a better place
(if you consider using it with pc/q35 machines)
Quoted 17 lines
include/hw/acpi/generic_event_device.h +2
-0#define TYPE_ACPI_GED "acpi-ged"OBJECT_DECLARE_SIMPLE_TYPE (AcpiGedState,ACPI_GED )@@ -98,6 +99,7 @@ OBJECT_DECLARE_SIMPLE_TYPE(AcpiGedState, ACPI_GED)#define ACPI_GED_PWR_DOWN_EVT 0x2#define ACPI_GED_NVDIMM_HOTPLUG_EVT 0x4#define ACPI_GED_CPU_HOTPLUG_EVT 0x8 +#define ACPI_GED_ERROR_EVT 0x10 typedef struct GEDState { MemoryRegion evt;@@ -120,5 +122,6 @@ struct AcpiGedState {void build_ged_aml (Aml *table,const char * name,HotplugHandler *hotplug_dev,uint32_t ged_irq,AmlRegionSpace rs,hwaddr ged_base);void acpi_dsdt_add_power_button (Aml *scope); +void acpi_dsdt_add_error_device (Aml *scope);#endif
Re: [PATCH v5 1/7] arm/virt: place power button pin number on a define
In reply to Mauro Carvalho ChehabQuoted 6 lines · On Fri, 2 Aug 2024 23:43:56 +0200 Mauro Carvalho Chehab…
Having magic numbers inside the code is not a good idea, as it is error-prone. So, instead, create a macro with the number definition.
Signed-off-by Mauro Carvalho Chehab <[email protected]>Reviewed-by Jonathan Cameron <[email protected]>
Quoted 70 lines
--- hw/arm/virt-acpi-build.c | 6 +++--- hw/arm/virt.c | 7 ++++--- include/hw/arm/virt.h | 3 +++ 3 files changed, 10 insertions(+), 6 deletions(-)hw/arm/virt-acpi-build.c +3
-3@@ -154,10 +154,10 @@ static void acpi_dsdt_add_gpio(Aml *scope, const MemMapEntry *gpio_memmap,aml_append (dev,aml_name_decl ("_CRS" , crs));Aml *aei =aml_resource_template (); -/* Pin 3 for power button */ -const uint32_t pin_list[1 ] = {3 }; + +const uint32_t pin =GPIO_PIN_POWER_BUTTON ;aml_append (aei,aml_gpio_int (AML_CONSUMER ,AML_EDGE ,AML_ACTIVE_HIGH , -AML_EXCLUSIVE ,AML_PULL_UP ,0 , pin_list,1 , +AML_EXCLUSIVE ,AML_PULL_UP ,0 , &pin,1 ,"GPO0" ,NULL ,0 ));aml_append (dev,aml_name_decl ("_AEI" , aei));hw/arm/virt.c +4
-3@@ -1004,7 +1004,7 @@ static void virt_powerdown_req(Notifier *n, void *opaque)if (s->acpi_dev) {acpi_send_event (s->acpi_dev,ACPI_POWER_DOWN_STATUS ); }else { -/* use gpio Pin 3 for power button event */ +/* use gpio Pin for power button event */ qemu_set_irq (qdev_get_gpio_in (gpio_key_dev,0 ),1 ); } }@@ -1013,7 +1013,8 @@ static void create_gpio_keys(char *fdt, DeviceState *pl061_dev, uint32_t phandle) { gpio_key_dev =sysbus_create_simple ("gpio-key" ,-1 , -qdev_get_gpio_in (pl061_dev,3 )); +qdev_get_gpio_in (pl061_dev, +GPIO_PIN_POWER_BUTTON ));qemu_fdt_add_subnode (fdt,"/gpio-keys" );qemu_fdt_setprop_string (fdt,"/gpio-keys" ,"compatible" ,"gpio-keys" );@@ -1024,7 +1025,7 @@ static void create_gpio_keys(char *fdt, DeviceState *pl061_dev,qemu_fdt_setprop_cell (fdt,"/gpio-keys/poweroff" ,"linux,code" ,KEY_POWER );qemu_fdt_setprop_cells (fdt,"/gpio-keys/poweroff" , -"gpios" , phandle,3 ,0 ); +"gpios" , phandle,GPIO_PIN_POWER_BUTTON ,0 ); }#define SECURE_GPIO_POWEROFF 0include/hw/arm/virt.h +3
-0@@ -47,6 +47,9 @@/* See Linux kernel arch/arm64/include/asm/pvclock-abi.h */ #define PVTIME_SIZE_PER_CPU 64 +/* GPIO pins */ +#define GPIO_PIN_POWER_BUTTON 3 +enum {VIRT_FLASH ,VIRT_MEM ,
Re: [PATCH v5 3/7] arm/virt: Wire up GPIO error source for ACPI / GHES
In reply to Mauro Carvalho ChehabOn Fri, 2 Aug 2024 23:43:58 +0200
Mauro Carvalho Chehab <[email protected]> wrote:
subj: s/GPIO/GED signaled/
Quoted 2 lines
Adds support to ARM virtualization to allow handling a General Purpose Event (GPE) via GED error device.
s/General Purpose Event (GPE).../
generic error ACPI Event via GED & error source device
Quoted 20 lines
It is aligned with Linux Kernel patch:
https://lore.kernel.org/lkml/[email protected]/Co-authored-by Mauro Carvalho Chehab <[email protected]>Co-authored-by Jonathan Cameron <[email protected]>Cc Jonathan Cameron <[email protected]>Signed-off-by Mauro Carvalho Chehab <[email protected]>--- hw/acpi/ghes.c | 3 +++ hw/arm/virt-acpi-build.c | 1 + hw/arm/virt.c | 16 +++++++++++++++- include/hw/acpi/ghes.h | 3 +++ include/hw/arm/virt.h | 1 + 5 files changed, 23 insertions(+), 1 deletion(-)hw/acpi/ghes.c +0
-0
hw/acpi/ghes.c int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address) · line 448
Quoted 5 lines
hw/acpi/ghes.c +2
-0@@ -444,6 +444,9 @@ int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address)return ret; } +NotifierList generic_error_notifiers = +NOTIFIER_LIST_INITIALIZER (error_device_notifiers);
s/generic_error_notifiers/acpi_generic_error_notifiers/
hw/arm/virt-acpi-build.c build_dsdt(GArray *table_data, BIOSLinker *linker, VirtMachineState *vms) · line 861
Quoted 12 lines
hw/acpi/ghes.c +0
-0bool acpi_ghes_present (void ) {AcpiGedState *acpi_ged_state;hw/arm/virt-acpi-build.c +1
-0@@ -858,6 +858,7 @@ build_dsdt(GArray *table_data, BIOSLinker *linker, VirtMachineState *vms) }acpi_dsdt_add_power_button (scope); +acpi_dsdt_add_error_device (scope);
with suggested change in 2/7, this will look likeaml_append(scope, aml_foo_device());
Quoted 25 lines
hw/arm/virt-acpi-build.c +0
-0#ifdef CONFIG_TPM acpi_dsdt_add_tpm (scope, vms);#endif hw/arm/virt.c +2
-1@@ -73,6 +73,7 @@#include "standard-headers/linux/input.h" #include "hw/arm/smmuv3.h" #include "hw/acpi/acpi.h" +#include "hw/acpi/ghes.h" #include "target/arm/cpu-qom.h" #include "target/arm/internals.h" #include "target/arm/multiprocessing.h" @@ -677,7 +678,7 @@ static inline DeviceState *create_acpi_ged(VirtMachineState *vms)DeviceState *dev;MachineState *ms =MACHINE (vms);int irq = vms->irqmap[VIRT_ACPI_GED ]; -uint32_t event =ACPI_GED_PWR_DOWN_EVT ; +uint32_t event =ACPI_GED_PWR_DOWN_EVT |ACPI_GED_ERROR_EVT ;if (ms->ram_slots) { event |=ACPI_GED_MEM_HOTPLUG_EVT ;
hw/arm/virt.c static void virt_powerdown_req(Notifier *n, void *opaque) · line 1017
Quoted 8 lines
hw/arm/virt.c +5
-0@@ -1009,6 +1010,15 @@ static void virt_powerdown_req(Notifier *n, void *opaque) } } +static void virt_generic_error_req (Notifier *n,void *opaque) +{ +VirtMachineState *s =container_of (n, VirtMachineState, generic_error_notifier); + +if (s->acpi_dev) {
I'd assert her, and move check to caller so it won't even add a notifier if acpi_dev is not present
Quoted 44 lines
hw/arm/virt.c +8
-0+acpi_send_event (s->acpi_dev,ACPI_GENERIC_ERROR ); + } +} +static void create_gpio_keys (char *fdt,DeviceState *pl061_dev,uint32_t phandle) {@@ -2397,6 +2407,10 @@ static void machvirt_init(MachineState *machine) vms->powerdown_notifier.notify = virt_powerdown_req;qemu_register_powerdown_notifier (&vms->powerdown_notifier); + vms->generic_error_notifier.notify = virt_generic_error_req; +notifier_list_add (&generic_error_notifiers, + &vms->generic_error_notifier); +/* Create mmio transports, so the user can create virtio backends * (which will be automatically plugged in to the transports). If * no backend is created the transport will just sit harmlessly idle. include/hw/acpi/ghes.h +3
-0@@ -23,6 +23,9 @@#define ACPI_GHES_H #include "hw/acpi/bios-linker-loader.h" +#include "qemu/notify.h" + +extern NotifierList generic_error_notifiers;/* * Values for Hardware Error Notification Type field include/hw/arm/virt.h +1
-0@@ -175,6 +175,7 @@ struct VirtMachineState {DeviceState *gic;DeviceState *acpi_dev;Notifier powerdown_notifier; +Notifier generic_error_notifier;PCIBus *bus;char *oem_id;char *oem_table_id;
RE: [PATCH v5 5/7] qapi/ghes-cper: add an interface to do generic CPER error injection
In reply to Mauro Carvalho ChehabQuoted 17 lines
-----Original Message-----
From: Mauro Carvalho Chehab <[email protected]>
Sent: 02 August 2024 22:44
Cc: Jonathan Cameron <[email protected]>; Shiju Jose <[email protected]>; Mauro Carvalho Chehab <[email protected]>; Michael S. Tsirkin <[email protected]>; Ani Sinha <[email protected]>; Dongjiu Geng <[email protected]>; Eric Blake <[email protected]>; Igor Mammedov <[email protected]>; Markus Armbruster <[email protected]>; Michael Roth <[email protected]>; Paolo Bonzini <[email protected]>; Peter Maydell <[email protected]>; [email protected]; qemu- [email protected]; [email protected]
Subject: [PATCH v5 5/7] qapi/ghes-cper: add an interface to do generic CPER error injection
Quoted 6 lines
Creates a QMP command to be used for generic ACPI APEI hardware error injection (HEST) via GHESv2.
The actual GHES code will be added at the followup patch.
Signed-off-by Mauro Carvalho Chehab <[email protected]>
Few minor comments inline.
Quoted 111 lines
---
MAINTAINERS | 7 +++++ hw/acpi/Kconfig | 5 ++++ hw/acpi/ghes_cper.c | 45 ++++++++++++++++++++++++++++++++ hw/acpi/ghes_cper_stub.c | 18 +++++++++++++ hw/acpi/meson.build | 2 ++ hw/arm/Kconfig | 5 ++++ include/hw/acpi/ghes.h | 7 +++++ qapi/ghes-cper.json | 55 ++++++++++++++++++++++++++++++++++++++++ qapi/meson.build | 1 + qapi/qapi-schema.json | 1 + 10 files changed, 146 insertions(+)create mode 100644
hw/acpi/ghes_cper.c
create mode 100644hw/acpi/ghes_cper_stub.ccreate mode 100644qapi/ghes-cper.jsonMAINTAINERS +0
-0@@ -2075,6 +2075,13 @@ F: hw/acpi/ghes.cF:
include/hw/acpi/ghes.h
F:docs/specs/acpi_hest_ghes.rstMAINTAINERS +7
-0+ACPI/HEST/GHES/ARM processor CPER +R: Mauro Carvalho Chehab <[email protected]> +S: Maintained +F: hw/arm/ghes_cper.c +F: hw/acpi/ghes_cper_stub.c +F: qapi/ghes-cper.json +ppc4xx
L: [email protected]
S: Orphanhw/acpi/Kconfig index renamed from hw/acpi/Kconfig +0
-0
e07d3204eb36..73ffbb82c150100644hw/acpi/Kconfig +5
-0@@ -51,6 +51,11 @@ config ACPI_APEI bool depends on ACPI +config GHES_CPER + bool + depends on ACPI_APEI + default y +config
ACPI_PCIbool depends on ACPI && PCIhw/acpi/ghes_cper.c new file +45
-0@@ -0,0 +1,45 @@ +/* +* ARM Processor error injection +* +* Copyright(C) 2024 Huawei LTD. +* +* This code is licensed under the GPL version 2 or later. See the +* COPYING file in the top-level directory. +* +*/ + +#include "qemu/osdep.h" + +#include "qemu/base64.h" +#include "qemu/error-report.h" +#include "qemu/uuid.h" +#include "qapi/qapi-commands-ghes-cper.h" +#include "hw/acpi/ghes.h" + +void qmp_ghes_cper (CommonPlatformErrorRecord *qmp_cper, +Error **errp) +{ +int rc; +AcpiGhesCper cper; +QemuUUID be_uuid, le_uuid; + + rc =qemu_uuid_parse (qmp_cper->notification_type, &be_uuid); +if (rc) { +error_setg (errp,"GHES: Invalid UUID: %s" , + qmp_cper->notification_type); +return ; + } + + le_uuid =qemu_uuid_bswap (be_uuid); + cper.guid = le_uuid.data; + + cper.data =qbase64_decode (qmp_cper->raw_data,-1 , + &cper.data_len, errp); +if (!cper.data) { +return ; + } + +/* TODO: call a function at ghes */ + +g_free (cper.data); +}hw/acpi/ghes_cper_stub.c new file renamed from hw/acpi/ghes_cper_stub.c +0
-0mode 100644 index 000000000000..7ce6ed70a265
hw/acpi/ghes_cper_stub.c new file +6
-0@@ -0,0 +1,18 @@ +/* +* ARM Processor error injection +* +* Copyright(C) 2024 Huawei LTD. +* +* This code is licensed under the GPL version 2 or later. See the
hw/acpi/ghes_cper_stub.c line 16
Quoted 10 lines
hw/acpi/ghes_cper_stub.c new file +10
-0+* COPYING file in the top-level directory. +* +*/ + +#include "qemu/osdep.h" +#include "qapi/error.h" +#include "qapi/qapi-commands-ghes-cper.h" +#include "hw/acpi/ghes.h" + +void qmp_ghes_cper (CommonPlatformErrorRecord *cper,Error **errp) { }
May be add an unsupported or similar log in the stub function?
Quoted 89 lines
hw/acpi/meson.build index renamed from hw/acpi/meson.build +0
-0
fa5c07db9068..6cbf430eb66d100644hw/acpi/meson.build +0
-0@@ -34,4 +34,6 @@ endifsystem_ss.add(when: '
CONFIG_ACPI',if_false:files('acpi-stub.c', 'aml-build- stub.c', 'ghes-stub.c', 'acpi_interface.c'))system_ss.add(when: 'CONFIG_ACPI_PCI_BRIDGE', if_false: files('pci-bridge- stub.c'))system_ss.add_all(when: 'CONFIG_ACPI', if_true: acpi_ss)hw/acpi/meson.build +3
-0+system_ss.add(when: 'CONFIG_GHES_CPER', if_true: files('ghes_cper.c')) +system_ss.add(when: 'CONFIG_GHES_CPER', if_false: +files('ghes_cper_stub.c'))system_ss.add(files('acpi-qmp-cmds.c'))
hw/arm/Kconfig index renamed from hw/arm/Kconfig +0
-0
1ad60da7aa2d..bed6ba27d715100644hw/arm/Kconfig +5
-0@@ -712,3 +712,8 @@ config ARMSSE select UNIMP select SSE_COUNTER select SSE_TIMER + +config GHES_CPER + bool + depends on ARM + default y if AARCH64include/hw/acpi/ghes.h index renamed from include/hw/acpi/ghes.h +0
-0
33be1eb5acf4..06a5b8820cd5100644include/hw/acpi/ghes.h +1
-0@@ -23,6 +23,7 @@#define ACPI_GHES_H #include "hw/acpi/bios-linker-loader.h" +#include "qapi/error.h" #include "qemu/notify.h" extern NotifierList
generic_error_notifiers; @@ -78,6 +79,12 @@ void acpi_ghes_add_fw_cfg(AcpiGhesState *vms, FWCfgState *s,
GArray*hardware_errors); intacpi_ghes_record_errors(uint8_t notify, uint64_t error_physical_addr);include/hw/acpi/ghes.h +6
-0+typedef struct AcpiGhesCper { +uint8_t *guid; +uint8_t *data; +size_t data_len; +}AcpiGhesCper ; +/**
*acpi_ghes_present: Report whether ACPI GHES table is present *qapi/ghes-cper.json new file +22
-0@@ -0,0 +1,55 @@ +# -*- Mode: Python -*- +# vim: filetype=python + +## +# = GHESv2 CPER Error Injection +# +# These are defined at +# ACPI 6.2: 18.3.2.8 Generic Hardware Error Source version 2 # (GHESv2 +- Type 10) ## + +## +# @CommonPlatformErrorRecord: +# +# Common Platform Error Record - CPER - as defined at the UEFI # +specification. See # +https://uefi.org/specs/UEFI/2.10/Apx_N_Common_Platform_Error_Record.htm +l#record-header +# for more details. +# +# @notification-type: pre-assigned GUID string indicating the record +# association with an error event notification type, as defined +# athttps://uefi.org/specs/UEFI/2.10/Apx_N_Common_Platform_Error_Record.html
#record-headerqapi/ghes-cper.json new file +8
-0+# +# @raw-data: Contains a base64 encoded string with the payload of +# the CPER. +# +# Since: 9.2 +## +{ 'struct': 'CommonPlatformErrorRecord', + 'data': {
qapi/ghes-cper.json
Quoted 10 lines
qapi/ghes-cper.json new file +10
-0+ 'notification-type': 'str', + 'raw-data': 'str' + } +} + +## +# @ghes-cper: +# +# Inject ARM Processor error with data to be filled according with # +ACPI 6.2 GHESv2 spec.
Since ghes-cper is generic interface, mentioning term "ARM Processor error" here may not be appropriate?
Quoted 40 lines
qapi/ghes-cper.json new file +15
-0+# +# @cper: a single CPER record to be sent to the guest OS. +# +# Features: +# +# @unstable: This command is experimental. +# +# Since: 9.2 +## +{ 'command': 'ghes-cper', + 'data': { + 'cper': 'CommonPlatformErrorRecord' + }, + 'features': [ 'unstable' ] +}qapi/meson.build index renamed from qapi/meson.build +0
-0
e7bc54e5d047..bd13cd7d40c9100644qapi/meson.build +1
-0@@ -35,6 +35,7 @@ qapi_all_modules = [ 'dump', 'ebpf', 'error', + 'ghes-cper', 'introspect', 'job', 'machine-common',qapi/qapi-schema.json index renamed from qapi/qapi-schema.json +0
-0
b1581988e4eb..c1a267399fe5100644qapi/qapi-schema.json +1
-1@@ -75,6 +75,7 @@ { 'include': 'misc-target.json' } { 'include': 'audio.json' } { 'include': 'acpi.json' } +{ 'include': 'ghes-cper.json' } { 'include': 'pci.json' } { 'include': 'stats.json' } { 'include': 'virtio.json' } --
Quoted 1 line
2.45.2
Thanks,
Shiju
Re: [PATCH v5 4/7] acpi/ghes: Support GPIO error source
In reply to Mauro Carvalho ChehabQuoted 28 lines · On Tue, 6 Aug 2024 08:09:28 +0200 Mauro Carvalho Chehab…
Em Mon, 5 Aug 2024 17:56:17 +0100
Jonathan Cameron <[email protected]> escreveu:Quoted 8 lines
Quoted 3 lines · On Fri, 2 Aug 2024 23:43:59 +0200 Mauro Carvalho Chehab…
From: Jonathan Cameron <[email protected]>
Add error notification to GHES v2 using the GPIO source.
The gpio / external interrupt follows through.
True. As session 18.3.2.7 of the spec says:
The OSPM evaluates the control method associated with this event as indicated in The Event Method for Handling GPIO Signaled Events and The Event Method for Handling Interrupt Signaled Events.
E. g. defining two methods:
- GED GPIO;
- GED interruptI'm doing this rename:
ACPI_HEST_SRC_ID_GPIO -> ACPI_HEST_SRC_ID_GED_INTTo clearly state what it is implemented there.
Quoted 8 lines
I'm also changing patch description to:
acpi/ghes: Add support for General Purpose Event
As a GED error device is now defined, add another type of notification.
Add error notification to GHES v2 using the GPIO source.
^^^^
did you mean: GED?
Quoted 10 lines
[mchehab: do some cleanups at ACPI_HEST_SRC_ID_* checks and
rename HEST event to better identify GED interrupt OSPM]Signed-off-by Jonathan Cameron <[email protected]>Signed-off-by Mauro Carvalho Chehab <[email protected]>Regards,
Mauro
Re: [PATCH v5 4/7] acpi/ghes: Support GPIO error source
In reply to Mauro Carvalho ChehabQuoted 39 lines · On Fri, 2 Aug 2024 23:43:59 +0200 Mauro Carvalho Chehab…
From: Jonathan Cameron <[email protected]>
Add error notification to GHES v2 using the GPIO source.
[mchehab: do some cleanups at ACPI_HEST_SRC_ID_* checks]
Signed-off-by Jonathan Cameron <[email protected]>Signed-off-by Mauro Carvalho Chehab <[email protected]>--- hw/acpi/ghes.c | 16 ++++++++++------ include/hw/acpi/ghes.h | 3 ++- 2 files changed, 12 insertions(+), 7 deletions(-)hw/acpi/ghes.c +5
-2@@ -34,8 +34,8 @@/* The max size in bytes for one error block */ #define ACPI_GHES_MAX_RAW_DATA_LENGTH (1 * KiB) -/* Now only support ARMv8 SEA notification type error source */ -#define ACPI_GHES_ERROR_SOURCE_COUNT 1 +/* Support ARMv8 SEA notification type error source and GPIO interrupt. */ +#define ACPI_GHES_ERROR_SOURCE_COUNT 2/* Generic Hardware Error Source version 2 */ #define ACPI_GHES_SOURCE_GENERIC_ERROR_V2 10@@ -290,6 +290,9 @@ void build_ghes_error_table(GArray *hardware_errors, BIOSLinker *linker)static void build_ghes_v2 (GArray *table_data,int source_id,BIOSLinker *linker) {uint64_t address_offset; + +assert (source_id <ACPI_HEST_SRC_ID_RESERVED ); +/* * Type: * Generic Hardware Error Source version 2(GHESv2 - Type 10)
hw/acpi/ghes.c static void build_ghes_v2(GArray *table_data, int source_id, BIOSLinker *linker) · line 334
Quoted 5 lines
hw/acpi/ghes.c +2
-0@@ -327,6 +330,9 @@ static void build_ghes_v2(GArray *table_data, int source_id, BIOSLinker *linker)*/ build_ghes_hw_error_notification (table_data,ACPI_GHES_NOTIFY_SEA );break ; +case ACPI_HEST_SRC_ID_GPIO : +build_ghes_hw_error_notification (table_data,ACPI_GHES_NOTIFY_GPIO );
perhaps ACPI_GHES_NOTIFY_EXTERNAL fits better here?
Quoted 13 lines
hw/acpi/ghes.c +2
-0+break ;default :error_report ("Not support this error source" );abort ();@@ -370,6 +376,7 @@ void acpi_build_hest(GArray *table_data, BIOSLinker *linker,/* Error Source Count */ build_append_int_noprefix (table_data,ACPI_GHES_ERROR_SOURCE_COUNT ,4 );build_ghes_v2 (table_data,ACPI_HEST_SRC_ID_SEA , linker); +build_ghes_v2 (table_data,ACPI_HEST_SRC_ID_GPIO , linker);acpi_table_end (linker, &table); }
hw/acpi/ghes.c int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address) · line 416
Quoted 8 lines
hw/acpi/ghes.c +1
-4@@ -406,10 +413,7 @@ int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address) start_addr =le64_to_cpu (ags->ghes_addr_le);if (physical_address) { - -if (source_id <ACPI_HEST_SRC_ID_RESERVED ) { - start_addr += source_id *sizeof (uint64_t ); - } + start_addr += source_id *sizeof (uint64_t );
why check is being removed?
Quoted 19 lines
hw/acpi/ghes.c +0
-0cpu_physical_memory_read (start_addr, &error_block_addr,sizeof (error_block_addr));include/hw/acpi/ghes.h +2
-1@@ -59,9 +59,10 @@ enum AcpiGhesNotifyType { ACPI_GHES_NOTIFY_RESERVED = 12 }; +/* Those are used as table indexes when building GHES tables */ enum {ACPI_HEST_SRC_ID_SEA =0 , -/* future ids go here */ +ACPI_HEST_SRC_ID_GPIO ,ACPI_HEST_SRC_ID_RESERVED , };
RE: [PATCH v5 6/7] acpi/ghes: add support for generic error injection via QAPI
In reply to Mauro Carvalho ChehabQuoted 19 lines
-----Original Message-----
From: Mauro Carvalho Chehab <[email protected]>
Sent: 02 August 2024 22:44
Cc: Jonathan Cameron <[email protected]>; Shiju Jose <[email protected]>; Mauro Carvalho Chehab <[email protected]>; Michael S. Tsirkin <[email protected]>; Ani Sinha <[email protected]>; Dongjiu Geng <[email protected]>; Igor Mammedov <[email protected]>; [email protected]; qemu- [email protected]; [email protected]
Subject: [PATCH v5 6/7] acpi/ghes: add support for generic error injection via QAPIProvide a generic interface for error injection via GHESv2.
This patch is co-authored:
- original ghes logic to inject a simple ARM record by Shiju Jose;
- generic logic to handle block addresses by Jonathan Cameron;
- generic GHESv2 error inject by Mauro Carvalho Chehab;
Quoted 6 lines
Co-authored-by Jonathan Cameron <[email protected]>Co-authored-by Shiju Jose <[email protected]>Co-authored-by Mauro Carvalho Chehab <[email protected]>Cc Jonathan Cameron <[email protected]>Cc Shiju Jose <[email protected]>Signed-off-by Mauro Carvalho Chehab <[email protected]>
Quoted 221 lines
---
hw/acpi/ghes.c | 159 ++++++++++++++++++++++++++++++++++++++--- hw/acpi/ghes_cper.c | 2 +- include/hw/acpi/ghes.h | 3 + 3 files changed, 152 insertions(+), 12 deletions(-)hw/acpi/ghes.c index renamed from hw/acpi/ghes.c +0
-0
a745dcc7be5e..e125c9475773100644hw/acpi/ghes.c +74
-11@@ -395,23 +395,22 @@ void acpi_ghes_add_fw_cfg(AcpiGhesState *ags, FWCfgState *s, ags->present = true; } +static uint64_t ghes_get_state_start_address (void ) +{ +AcpiGedState *acpi_ged_state = +ACPI_GED (object_resolve_path_type ("" ,TYPE_ACPI_GED ,NULL )); +AcpiGhesState *ags = &acpi_ged_state->ghes_state; + +return le64_to_cpu (ags->ghes_addr_le); } +int acpi_ghes_record_errors (uint8_t source_id,uint64_t physical_address) {uint64_t error_block_addr, read_ack_register_addr, read_ack_register =0 ; -uint64_t start_addr; +uint64_t start_addr =ghes_get_state_start_address ();bool ret =-1 ; -AcpiGedState *acpi_ged_state; -AcpiGhesState *ags; -assert (source_id <ACPI_HEST_SRC_ID_RESERVED ); - acpi_ged_state =ACPI_GED (object_resolve_path_type ("" ,TYPE_ACPI_GED , -NULL )); -g_assert (acpi_ged_state); - ags = &acpi_ged_state->ghes_state; - - start_addr =le64_to_cpu (ags->ghes_addr_le); -if (physical_address) { start_addr += source_id *sizeof (uint64_t );@@ -448,9 +447,147 @@ int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address)return ret; } +/* +* Error register block data layout +* +* | +---------------------+ ges.ghes_addr_le +* | |error_block_address0 | +* | +---------------------+ +* | |error_block_address1 | +* | +---------------------+ --+-- +* | | ............. | GHES_ADDRESS_SIZE +* | +---------------------+ --+-- +* | |error_block_addressN | +* | +---------------------+ +* | | read_ack0 | +* | +---------------------+ --+-- +* | | read_ack1 | GHES_ADDRESS_SIZE +* | +---------------------+ --+-- +* | | ............. | +* | +---------------------+ +* | | read_ackN | +* | +---------------------+ --+-- +* | | CPER | | +* | | .... | GHES_MAX_RAW_DATA_LENGT +* | | CPER | | +* | +---------------------+ --+-- +* | | .......... | +* | +---------------------+ +* | | CPER | +* | | .... | +* | | CPER | +* | +---------------------+ +*/ + +/* Map from uint32_t notify to entry offset in GHES */ static const +uint8_t error_source_to_index[] = {0xff ,0xff ,0xff ,0xff , +0xff ,0xff ,0xff ,1 , +0 }; + +static bool ghes_get_addr (uint32_t notify,uint64_t *error_block_addr, +uint64_t *read_ack_addr) { +uint64_t base; + +if (notify >=ACPI_GHES_NOTIFY_RESERVED ) { +return false; + } + +/* Find and check the source id for this new CPER */ +if (error_source_to_index[notify] ==0xff ) { +return false; + } + + base =ghes_get_state_start_address (); + + *read_ack_addr = base + +ACPI_GHES_ERROR_SOURCE_COUNT *sizeof (uint64_t ) + + error_source_to_index[notify] *sizeof (uint64_t ); + +/* Could also be read back from the error_block_address register */ + *error_block_addr = base + +ACPI_GHES_ERROR_SOURCE_COUNT *sizeof (uint64_t ) + +ACPI_GHES_ERROR_SOURCE_COUNT *sizeof (uint64_t ) + + error_source_to_index[notify] *ACPI_GHES_MAX_RAW_DATA_LENGTH ; + +return true; +} +NotifierList
generic_error_notifiers=NOTIFIER_LIST_INITIALIZER(error_device_notifiers);hw/acpi/ghes.c +72
-0+void ghes_record_cper_errors (AcpiGhesCper *cper,Error **errp, +uint32_t notify) { +int read_ack =0 ; +uint32_t i; +uint64_t read_ack_addr =0 ; +uint64_t error_block_addr =0 ; +uint32_t data_length; +GArray *block; + +if (!ghes_get_addr (notify, &error_block_addr, &read_ack_addr)) { +error_setg (errp,"GHES: Invalid error block/ack address(es)" ); +return ; + } + +cpu_physical_memory_read (read_ack_addr, + &read_ack,sizeof (uint64_t )); + +/* zero means OSPM does not acknowledge the error */ +if (!read_ack) { +error_setg (errp, +"Last CPER record was not acknowledged yet" ); + read_ack =1 ; +cpu_physical_memory_write (read_ack_addr, + &read_ack,sizeof (uint64_t )); +return ; + } + + read_ack =cpu_to_le64 (0 ); +cpu_physical_memory_write (read_ack_addr, + &read_ack,sizeof (uint64_t )); + +/* Build CPER record */ + +/* +* Invalid fru id: ACPI 4.0: 17.3.2.6.1 Generic Error Data, +* Table 17-13 Generic Error Data Entry +*/ +QemuUUID fru_id = {}; + + block =g_array_new (false, true/* clear */ ,1 ); + data_length =ACPI_GHES_DATA_LENGTH + cper->data_len; + +/* +* It should not run out of the preallocated memory if +* adding a new generic error data entry +*/ +assert ((data_length +ACPI_GHES_GESB_SIZE ) <= +ACPI_GHES_MAX_RAW_DATA_LENGTH ); + +/* Build the new generic error status block header */ +acpi_ghes_generic_error_status (block,ACPI_GEBS_UNCORRECTABLE , +0 ,0 , data_length, +ACPI_CPER_SEV_RECOVERABLE ); + +/* Build this new generic error data entry header */ +acpi_ghes_generic_error_data (block, cper->guid, +ACPI_CPER_SEV_RECOVERABLE ,0 ,0 , + cper->data_len, fru_id,0 ); + +/* Add CPER data */ +for (i =0 ; i < cper->data_len; i++) { +build_append_int_noprefix (block, cper->data[i],1 ); + } + +/* Write the generic error data entry into guest memory */ +cpu_physical_memory_write (error_block_addr, block->data, + block->len); + +g_array_free (block, true); + +notifier_list_notify (&generic_error_notifiers,NULL ); } +bool
acpi_ghes_present(void){ AcpiGedState *acpi_ged_state;hw/acpi/ghes_cper.c index renamed from hw/acpi/ghes_cper.c +0
-0
7aa7e71e90dc..d7ff7debee74100644hw/acpi/ghes_cper.c +1
-1@@ -39,7 +39,7 @@ void qmp_ghes_cper(CommonPlatformErrorRecord *qmp_cper, return; } -/* TODO: call a function at ghes */ +ghes_record_cper_errors (&cper, errp,ACPI_GHES_NOTIFY_GPIO );g_free (cper.data);}
include/hw/acpi/ghes.h index renamed from include/hw/acpi/ghes.h +0
-0
06a5b8820cd5..ee6f6cd96911100644include/hw/acpi/ghes.h +3
-1@@ -85,6 +85,9 @@ typedef struct AcpiGhesCper {size_t data_len; } AcpiGhesCper; +void ghes_record_cper_errors (AcpiGhesCper *cper,Error **errp, +uint32_t notify); +/** * acpi_ghes_present: Report whether ACPI GHES table is present * -- 2.45.2
Re: [PATCH v5 5/7] qapi/ghes-cper: add an interface to do generic CPER error injection
In reply to Mauro Carvalho ChehabQuoted 208 lines · On Fri, 2 Aug 2024 23:44:00 +0200 Mauro Carvalho Chehab…
Creates a QMP command to be used for generic ACPI APEI hardware error injection (HEST) via GHESv2.
The actual GHES code will be added at the followup patch.
Signed-off-by Mauro Carvalho Chehab <[email protected]>--- MAINTAINERS | 7 +++++ hw/acpi/Kconfig | 5 ++++ hw/acpi/ghes_cper.c | 45 ++++++++++++++++++++++++++++++++ hw/acpi/ghes_cper_stub.c | 18 +++++++++++++ hw/acpi/meson.build | 2 ++ hw/arm/Kconfig | 5 ++++ include/hw/acpi/ghes.h | 7 +++++ qapi/ghes-cper.json | 55 ++++++++++++++++++++++++++++++++++++++++ qapi/meson.build | 1 + qapi/qapi-schema.json | 1 + 10 files changed, 146 insertions(+) create mode 100644 hw/acpi/ghes_cper.c create mode 100644 hw/acpi/ghes_cper_stub.c create mode 100644 qapi/ghes-cper.jsonMAINTAINERS +7
-0@@ -2075,6 +2075,13 @@ F: hw/acpi/ghes.c F: include/hw/acpi/ghes.h F: docs/specs/acpi_hest_ghes.rst +ACPI/HEST/GHES/ARM processor CPER +R: Mauro Carvalho Chehab <[email protected]> +S: Maintained +F: hw/arm/ghes_cper.c +F: hw/acpi/ghes_cper_stub.c +F: qapi/ghes-cper.json + ppc4xx L: [email protected] S: Orphanhw/acpi/Kconfig +5
-0@@ -51,6 +51,11 @@ config ACPI_APEI bool depends on ACPI +config GHES_CPER + bool + depends on ACPI_APEI + default y + config ACPI_PCI bool depends on ACPI && PCIhw/acpi/ghes_cper.c new file +45
-0@@ -0,0 +1,45 @@ +/* +* ARM Processor error injection +* +* Copyright(C) 2024 Huawei LTD. +* +* This code is licensed under the GPL version 2 or later. See the +* COPYING file in the top-level directory. +* +*/ + +#include "qemu/osdep.h" + +#include "qemu/base64.h" +#include "qemu/error-report.h" +#include "qemu/uuid.h" +#include "qapi/qapi-commands-ghes-cper.h" +#include "hw/acpi/ghes.h" + +void qmp_ghes_cper (CommonPlatformErrorRecord *qmp_cper, +Error **errp) +{ +int rc; +AcpiGhesCper cper; +QemuUUID be_uuid, le_uuid; + + rc =qemu_uuid_parse (qmp_cper->notification_type, &be_uuid); +if (rc) { +error_setg (errp,"GHES: Invalid UUID: %s" , + qmp_cper->notification_type); +return ; + } + + le_uuid =qemu_uuid_bswap (be_uuid); + cper.guid = le_uuid.data; + + cper.data =qbase64_decode (qmp_cper->raw_data,-1 , + &cper.data_len, errp); +if (!cper.data) { +return ; + } + +/* TODO: call a function at ghes */ + +g_free (cper.data); +}hw/acpi/ghes_cper_stub.c new file +18
-0@@ -0,0 +1,18 @@ +/* +* ARM Processor error injection +* +* Copyright(C) 2024 Huawei LTD. +* +* This code is licensed under the GPL version 2 or later. See the +* COPYING file in the top-level directory. +* +*/ + +#include "qemu/osdep.h" +#include "qapi/error.h" +#include "qapi/qapi-commands-ghes-cper.h" +#include "hw/acpi/ghes.h" + +void qmp_ghes_cper (CommonPlatformErrorRecord *cper,Error **errp) +{ +}hw/acpi/meson.build +2
-0@@ -34,4 +34,6 @@ endif system_ss.add(when: 'CONFIG_ACPI', if_false: files('acpi-stub.c', 'aml-build-stub.c', 'ghes-stub.c', 'acpi_interface.c')) system_ss.add(when: 'CONFIG_ACPI_PCI_BRIDGE', if_false: files('pci-bridge-stub.c')) system_ss.add_all(when: 'CONFIG_ACPI', if_true: acpi_ss) +system_ss.add(when: 'CONFIG_GHES_CPER', if_true: files('ghes_cper.c')) +system_ss.add(when: 'CONFIG_GHES_CPER', if_false: files('ghes_cper_stub.c')) system_ss.add(files('acpi-qmp-cmds.c'))hw/arm/Kconfig +5
-0@@ -712,3 +712,8 @@ config ARMSSE select UNIMP select SSE_COUNTER select SSE_TIMER + +config GHES_CPER + bool + depends on ARM + default y if AARCH64include/hw/acpi/ghes.h +7
-0@@ -23,6 +23,7 @@#define ACPI_GHES_H #include "hw/acpi/bios-linker-loader.h" +#include "qapi/error.h" #include "qemu/notify.h" extern NotifierList generic_error_notifiers;@@ -78,6 +79,12 @@ void acpi_ghes_add_fw_cfg(AcpiGhesState *vms, FWCfgState *s, GArray *hardware_errors);int acpi_ghes_record_errors (uint8_t notify,uint64_t error_physical_addr); +typedef struct AcpiGhesCper { +uint8_t *guid; +uint8_t *data; +size_t data_len; +}AcpiGhesCper ; +/** * acpi_ghes_present: Report whether ACPI GHES table is present * qapi/ghes-cper.json new file +22
-0@@ -0,0 +1,55 @@ +# -*- Mode: Python -*- +# vim: filetype=python + +## +# = GHESv2 CPER Error Injection +# +# These are defined at +# ACPI 6.2: 18.3.2.8 Generic Hardware Error Source version 2 +# (GHESv2 - Type 10) +## + +## +# @CommonPlatformErrorRecord: +# +# Common Platform Error Record - CPER - as defined at the UEFI +# specification. See +# https://uefi.org/specs/UEFI/2.10/Apx_N_Common_Platform_Error_Record.html#record-header +# for more details. +# +# @notification-type: pre-assigned GUID string indicating the record +# association with an error event notification type, as defined +# at https://uefi.org/specs/UEFI/2.10/Apx_N_Common_Platform_Error_Record.html#record-header
qapi/ghes-cper.json line 31
Quoted 10 lines
qapi/ghes-cper.json new file +9
-0+# +# @raw-data: Contains a base64 encoded string with the payload of +# the CPER. +# +# Since: 9.2 +## +{ 'struct': 'CommonPlatformErrorRecord', + 'data': { + 'notification-type': 'str',
this should be source id (type is just impl. detail of how QEMU delivers event for given source id)
unless there is no plan to use more sources,
I'd just drop this from API to avoid confusing user.
Since the patch comes before 5/7, it's not clear how it will be used at this point. I'd move the patch after 5/7.
Quoted 48 lines
qapi/ghes-cper.json new file +24
-0+ 'raw-data': 'str' + } +} + +## +# @ghes-cper: +# +# Inject ARM Processor error with data to be filled according with +# ACPI 6.2 GHESv2 spec. +# +# @cper: a single CPER record to be sent to the guest OS. +# +# Features: +# +# @unstable: This command is experimental. +# +# Since: 9.2 +## +{ 'command': 'ghes-cper', + 'data': { + 'cper': 'CommonPlatformErrorRecord' + }, + 'features': [ 'unstable' ] +}qapi/meson.build +1
-0@@ -35,6 +35,7 @@ qapi_all_modules = [ 'dump', 'ebpf', 'error', + 'ghes-cper', 'introspect', 'job', 'machine-common',qapi/qapi-schema.json +1
-0@@ -75,6 +75,7 @@ { 'include': 'misc-target.json' } { 'include': 'audio.json' } { 'include': 'acpi.json' } +{ 'include': 'ghes-cper.json' } { 'include': 'pci.json' } { 'include': 'stats.json' } { 'include': 'virtio.json' }
Re: [PATCH v5 5/7] qapi/ghes-cper: add an interface to do generic CPER error injection
Em Tue, 6 Aug 2024 14:51:53 +0200
Igor Mammedov <[email protected]> escreveu:
Quoted 5 lines
qapi/ghes-cper.json line 31
Quoted 4 lines
qapi/ghes-cper.json new file +3
-0+{ 'struct': 'CommonPlatformErrorRecord', + 'data': { + 'notification-type': 'str',
Quoted 7 lines
this should be source id (type is just impl. detail of how QEMU delivers event for given source id)
unless there is no plan to use more sources,
I'd just drop this from API to avoid confusing user.Since the patch comes before 5/7, it's not clear how it will be used at this point. I'd move the patch after 5/7.
As described at:
qapi/ghes-cper.json line 22
Quoted 3 lines
qapi/ghes-cper.json new file +3
-0+# @notification-type: pre-assigned GUID string indicating the record +# association with an error event notification type, as defined +# at https://uefi.org/specs/UEFI/2.10/Apx_N_Common_Platform_Error_Record.html#record-header
This is actually GUID of the error to be generated. Perhaps the better would be to change the above to:
{ 'struct': 'CommonPlatformErrorRecord',
'data': {
'guid': 'str',
'raw-data': 'str'
}Making it even clearer. In any case, this is mandatory, as otherwise the interface would be limited to a single type.
Thanks,
Mauro
Re: [PATCH v5 6/7] acpi/ghes: add support for generic error injection via QAPI
In reply to Mauro Carvalho ChehabQuoted 24 lines · On Fri, 2 Aug 2024 23:44:01 +0200 Mauro Carvalho Chehab…
Provide a generic interface for error injection via GHESv2.
This patch is co-authored:
- original ghes logic to inject a simple ARM record by Shiju Jose;
- generic logic to handle block addresses by Jonathan Cameron;
- generic GHESv2 error inject by Mauro Carvalho Chehab;Co-authored-by Jonathan Cameron <[email protected]>Co-authored-by Shiju Jose <[email protected]>Co-authored-by Mauro Carvalho Chehab <[email protected]>Cc Jonathan Cameron <[email protected]>Cc Shiju Jose <[email protected]>Signed-off-by Mauro Carvalho Chehab <[email protected]>--- hw/acpi/ghes.c | 159 ++++++++++++++++++++++++++++++++++++++--- hw/acpi/ghes_cper.c | 2 +- include/hw/acpi/ghes.h | 3 + 3 files changed, 152 insertions(+), 12 deletions(-)hw/acpi/ghes.c +0
-0
hw/acpi/ghes.c void acpi_ghes_add_fw_cfg(AcpiGhesState *ags, FWCfgState *s, · line 398
Quoted 4 lines
hw/acpi/ghes.c +1
-0@@ -395,23 +395,22 @@ void acpi_ghes_add_fw_cfg(AcpiGhesState *ags, FWCfgState *s, ags->present = true; } +static uint64_t ghes_get_state_start_address (void )
ghes_get_hardware_errors_address() might better reflect what address it will return
Quoted 18 lines
hw/acpi/ghes.c +9
-4+{ +AcpiGedState *acpi_ged_state = +ACPI_GED (object_resolve_path_type ("" ,TYPE_ACPI_GED ,NULL )); +AcpiGhesState *ags = &acpi_ged_state->ghes_state; + +return le64_to_cpu (ags->ghes_addr_le); +} +int acpi_ghes_record_errors (uint8_t source_id,uint64_t physical_address) {uint64_t error_block_addr, read_ack_register_addr, read_ack_register =0 ; -uint64_t start_addr; +uint64_t start_addr =ghes_get_state_start_address ();bool ret =-1 ; -AcpiGedState *acpi_ged_state; -AcpiGhesState *ags; -assert (source_id <ACPI_HEST_SRC_ID_RESERVED );
hw/acpi/ghes.c void acpi_ghes_add_fw_cfg(AcpiGhesState *ags, FWCfgState *s, · line 415
Quoted 10 lines
hw/acpi/ghes.c +0
-7- acpi_ged_state =ACPI_GED (object_resolve_path_type ("" ,TYPE_ACPI_GED , -NULL )); -g_assert (acpi_ged_state); - ags = &acpi_ged_state->ghes_state; - - start_addr =le64_to_cpu (ags->ghes_addr_le); -if (physical_address) { start_addr += source_id *sizeof (uint64_t );
above should be a separate patch
Quoted 26 lines
hw/acpi/ghes.c +21
-0@@ -448,9 +447,147 @@ int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address)return ret; } +/* +* Error register block data layout +* +* | +---------------------+ ges.ghes_addr_le +* | |error_block_address0 | +* | +---------------------+ +* | |error_block_address1 | +* | +---------------------+ --+-- +* | | ............. | GHES_ADDRESS_SIZE +* | +---------------------+ --+-- +* | |error_block_addressN | +* | +---------------------+ +* | | read_ack0 | +* | +---------------------+ --+-- +* | | read_ack1 | GHES_ADDRESS_SIZE +* | +---------------------+ --+-- +* | | ............. | +* | +---------------------+ +* | | read_ackN | +* | +---------------------+ --+-- +* | | CPER | |
hw/acpi/ghes.c int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address) · line 480
Quoted 10 lines
hw/acpi/ghes.c +10
-0+* | | .... | GHES_MAX_RAW_DATA_LENGT +* | | CPER | | +* | +---------------------+ --+-- +* | | .......... | +* | +---------------------+ +* | | CPER | +* | | .... | +* | | CPER | +* | +---------------------+ +*/
no need to duplicate docs/specs/acpi_hest_ghes.rst,
I'd just reffer to it and maybe add short comment as to why it's mentioned.
Quoted 22 lines
hw/acpi/ghes.c +22
-0+/* Map from uint32_t notify to entry offset in GHES */ +static const uint8_t error_source_to_index[] = {0xff ,0xff ,0xff ,0xff , +0xff ,0xff ,0xff ,1 ,0 }; + +static bool ghes_get_addr (uint32_t notify,uint64_t *error_block_addr, +uint64_t *read_ack_addr) +{ +uint64_t base; + +if (notify >=ACPI_GHES_NOTIFY_RESERVED ) { +return false; + } + +/* Find and check the source id for this new CPER */ +if (error_source_to_index[notify] ==0xff ) { +return false; + } + + base =ghes_get_state_start_address (); + + *read_ack_addr = base + + ACPI_GHES_ERROR_SOURCE_COUNT * sizeof(uint64_t) +
hw/acpi/ghes.c int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address) · line 513
Quoted 10 lines
hw/acpi/ghes.c +10
-0+ error_source_to_index[notify] *sizeof (uint64_t ); + +/* Could also be read back from the error_block_address register */ + *error_block_addr = base + +ACPI_GHES_ERROR_SOURCE_COUNT *sizeof (uint64_t ) + +ACPI_GHES_ERROR_SOURCE_COUNT *sizeof (uint64_t ) + + error_source_to_index[notify] *ACPI_GHES_MAX_RAW_DATA_LENGTH ; + +return true; +}
I don't like all this pointer math, which is basically a reverse engineered QEMU actions on startup + guest provided etc/hardware_errors address.
For once, it assumes error_source_to_index[] matches order in which HEST error sources were described, which is fragile.
2nd: migration-wive it's disaster, since old/new HEST/hardware_errors tables in RAM migrated from older version might not match above assumptions of target QEMU.
I see 2 ways to rectify it:
1st: preferred/cleanest would be to tell QEMU (via fw_cfg) address of HEST table
in guest RAM, like we do with etc/hardware_errors, see
build_ghes_error_table()
...
tell firmware to write hardware_errors GPA into
and then fetch from HEST table in RAM, the guest patched error/ack addresses for given source_id
code-wise: relatively simple once one wraps their own head over
how this whole APEI thing works in QEMU
workflow is described in docs/specs/acpi_hest_ghes.rst look to me as sufficient to grasp it.
(but my view is very biased given my prior knowledge,
aka: docs/comments/examples wrt acpi patching are good enough)
(if it's not clear how to do it, ask me for pointers)
2nd: sort of hack based on build_ghes_v2() Error Status Address/Read Ack Register
patching instructions
bios_linker_loader_add_pointer(linker, ACPI_BUILD_TABLE_FILE,
address_offset + GAS_ADDR_OFFSET, sizeof(uint64_t), ACPI_GHES_ERRORS_FW_CFG_FILE, source_id * sizeof(uint64_t));
^^^^^^^^^^^^^^^^^^^^^^^^^
during build_ghes_v2() also store on a side mapping
source_id -> error address offset : read ack address
so when you are injecting error, you'd at least use offsets used at start time, to get rid of risk where injection code diverge from HEST:etc/hardware_errors layout at start time.
However to make migration safe, one would need to add a fat comment not to change order ghest error sources in HEST _and_ a dedicated unit test to make sure we catch it when that happens. bios_tables_test should be able to catch the change, but it won't say what's wrong, hence a test case that explicitly checks order and loudly & clear complains when we will break order assumptions.
downside:
* we are are limiting ways HEST could be composed/reshuffled in future
* consumption of extra CI resources
* and well, it relies on above duct tape holding all pieces together
hw/acpi/ghes.c int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address) · line 521
Quoted 7 lines
hw/acpi/ghes.c +4
-0NotifierList generic_error_notifiers =NOTIFIER_LIST_INITIALIZER (error_device_notifiers); +void ghes_record_cper_errors (AcpiGhesCper *cper,Error **errp, +uint32_t notify) +{ +int read_ack =0 ;
^^^
[...]
hw/acpi/ghes.c
Quoted 2 lines
hw/acpi/ghes.c +2
-0+cpu_physical_memory_read (read_ack_addr, + &read_ack,sizeof (uint64_t ));
^^^^
it looks like possible stack corruption, isn't it?
hw/acpi/ghes.c int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address) · line 542
Quoted 7 lines
hw/acpi/ghes.c +7
-0+/* zero means OSPM does not acknowledge the error */ +if (!read_ack) { +error_setg (errp, +"Last CPER record was not acknowledged yet" ); + read_ack =1 ; +cpu_physical_memory_write (read_ack_addr, + &read_ack,sizeof (uint64_t ));
^^^^^
and then who knows what we are writing back here
Quoted 14 lines
hw/acpi/ghes.c +14
-0+return ; + } + + read_ack =cpu_to_le64 (0 ); +cpu_physical_memory_write (read_ack_addr, + &read_ack,sizeof (uint64_t )); + +/* Build CPER record */ + +/* +* Invalid fru id: ACPI 4.0: 17.3.2.6.1 Generic Error Data, +* Table 17-13 Generic Error Data Entry +*/ +QemuUUID fru_id = {};
hw/acpi/ghes.c int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address) · line 566
Quoted 10 lines
hw/acpi/ghes.c +10
-0+ + block =g_array_new (false, true/* clear */ ,1 ); + data_length =ACPI_GHES_DATA_LENGTH + cper->data_len; + +/* +* It should not run out of the preallocated memory if +* adding a new generic error data entry +*/ +assert ((data_length +ACPI_GHES_GESB_SIZE ) <= +ACPI_GHES_MAX_RAW_DATA_LENGTH );
it's better to error out gracefully here instead of crash in case script generated too long record,
not the end of the world, but it's annoying to restart guest on external mistake.
PS:
looking at the code, ACPI_GHES_MAX_RAW_DATA_LENGTH is 1K and it is the total size of a error block for a error source.
However acpi_hest_ghes.rst (3) says it should be 4K, am I mistaken?
hw/acpi/ghes.c int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address) · line 577
Quoted 10 lines
hw/acpi/ghes.c +10
-0+/* Build the new generic error status block header */ +acpi_ghes_generic_error_status (block,ACPI_GEBS_UNCORRECTABLE , +0 ,0 , data_length, +ACPI_CPER_SEV_RECOVERABLE ); + +/* Build this new generic error data entry header */ +acpi_ghes_generic_error_data (block, cper->guid, +ACPI_CPER_SEV_RECOVERABLE ,0 ,0 , + cper->data_len, fru_id,0 ); +
not that I mind, but I'd ax above calls with their hardcoded assumptions and make script generate whole error block,
it's more flexible wrt ACPI_CPER_SEV_RECOVERABLE/ACPI_GEBS_UNCORRECTABLE and then one can ditch from QAPI interface cper->guid.
basically inject whatever user provided via QAPI without any other assumptions.
Quoted 34 lines
hw/acpi/ghes.c +13
-0+/* Add CPER data */ +for (i =0 ; i < cper->data_len; i++) { +build_append_int_noprefix (block, cper->data[i],1 ); + } + +/* Write the generic error data entry into guest memory */ +cpu_physical_memory_write (error_block_addr, block->data, block->len); + +g_array_free (block, true); + +notifier_list_notify (&generic_error_notifiers,NULL ); +} +bool acpi_ghes_present (void ) {AcpiGedState *acpi_ged_state;hw/acpi/ghes_cper.c +1
-1@@ -39,7 +39,7 @@ void qmp_ghes_cper(CommonPlatformErrorRecord *qmp_cper,return ; } -/* TODO: call a function at ghes */ +ghes_record_cper_errors (&cper, errp,ACPI_GHES_NOTIFY_GPIO );g_free (cper.data); }include/hw/acpi/ghes.h +0
-0
include/hw/acpi/ghes.h typedef struct AcpiGhesCper { · line 89
Quoted 5 lines
include/hw/acpi/ghes.h +2
-0@@ -85,6 +85,9 @@ typedef struct AcpiGhesCper {size_t data_len; } AcpiGhesCper; +void ghes_record_cper_errors (AcpiGhesCper *cper,Error **errp, +uint32_t notify);
maybe rename it to acpi_ghes_inject_error_block()
Quoted 4 lines
include/hw/acpi/ghes.h +1
-0+/** * acpi_ghes_present: Report whether ACPI GHES table is present *
Re: [PATCH v5 7/7] scripts/ghes_inject: add a script to generate GHES error inject
In reply to Mauro Carvalho ChehabQuoted 43 lines · On Fri, 2 Aug 2024 23:44:02 +0200 Mauro Carvalho Chehab…
Using the QMP GHESv2 API requires preparing a raw data array containing a CPER record.
Add a helper script with subcommands to prepare such data.
Currently, only ARM Processor error CPER record is supported.
Signed-off-by Mauro Carvalho Chehab <[email protected]>--- MAINTAINERS | 3 + scripts/arm_processor_error.py | 352 +++++++++++++++++++++++++++++++++ scripts/ghes_inject.py | 59 ++++++ scripts/qmp_helper.py | 249 +++++++++++++++++++++++ 4 files changed, 663 insertions(+) create mode 100644 scripts/arm_processor_error.py create mode 100755 scripts/ghes_inject.py create mode 100644 scripts/qmp_helper.pyMAINTAINERS +3
-0@@ -2081,6 +2081,9 @@ S: Maintained F: hw/arm/ghes_cper.c F: hw/acpi/ghes_cper_stub.c F: qapi/ghes-cper.json +F: scripts/ghes_inject.py +F: scripts/arm_processor_error.py +F: scripts/qmp_helper.py ppc4xx L: [email protected]scripts/arm_processor_error.py new file +5
-0@@ -0,0 +1,352 @@ +#!/usr/bin/env python3 +# +# pylint: disable=C0301, C0114, R0912, R0913, R0914, R0915, W0511 +# SPDX-License-Identifier: GPL-2.0 +#
scripts/arm_processor_error.py line 15
Quoted 10 lines
scripts/arm_processor_error.py new file +10
-0+# Copyright (C) 2024 Mauro Carvalho Chehab <[email protected]> + +# TODO: current implementation has dummy defaults. +# +# For a better implementation, a QMP addition/call is needed to +# retrieve some data for ARM Processor Error injection: +# +# - machine emulation architecture, as ARM current default is +# for AArch64; +# - ARM registers: power_state, midr, mpidr.
I'm not really reviewing the script but here some pointers how to fetch properties
start qemu with QMP connection
./qemu-system-aarch64 -M virt -qmp unix:/tmp/s,server,nowait
use script
./scripts/qmp/qom-get --socket /tmp/s /machine/unattached/device[0].midr
you can use ./scripts/qmp/qom-tree to explore what's there
see commit e61cc6b5c69 how to add property (DEFINE_PROP_UINT32 part mainly), as long as it's prefixed with "x-" (meaning internal/unstable) likelihood is that no one would object adding extra ones
Quoted 657 lines
scripts/arm_processor_error.py new file +337
-0+ +import argparse +import json + +from qmp_helper import (qmp_command, get_choice, get_mult_array, + get_mult_choices, get_mult_int, bit, + data_add, to_guid) + +# Arm processor EINJ logic +# +ACPI_GHES_ARM_CPER_LENGTH = 40 +ACPI_GHES_ARM_CPER_PEI_LENGTH = 32 + +# TODO: query it from emulation. Current default valid only for Aarch64 +CONTEXT_AARCH64_EL1 = 5 + +class ArmProcessorEinj: + """ + Implements ARM Processor Error injection via GHES + """ + + def __init__(self): + """Initialize the error injection class""" + + # Valid choice values + self.arm_valid_bits = { + "mpidr": bit(0), + "affinity": bit(1), + "running": bit(2), + "vendor": bit(3), + } + + self.pei_flags = { + "first": bit(0), + "last": bit(1), + "propagated": bit(2), + "overflow": bit(3), + } + + self.pei_error_types = { + "cache": bit(1), + "tlb": bit(2), + "bus": bit(3), + "micro-arch": bit(4), + } + + self.pei_valid_bits = { + "multiple-error": bit(0), + "flags": bit(1), + "error-info": bit(2), + "virt-addr": bit(3), + "phy-addr": bit(4), + } + + self.data = bytearray() + + def create_subparser(self, subparsers): + """Add a subparser to handle for the error fields""" + + parser = subparsers.add_parser("arm", + help="Generate an ARM processor CPER") + + arm_valid_bits = ",".join(self.arm_valid_bits.keys()) + flags = ",".join(self.pei_flags.keys()) + error_types = ",".join(self.pei_error_types.keys()) + pei_valid_bits = ",".join(self.arm_valid_bits.keys()) + + # UEFI N.16 ARM Validation bits + g_arm = parser.add_argument_group("ARM processor") + g_arm.add_argument("--arm", "--arm-valid", + help=f"ARM valid bits: {arm_valid_bits}") + g_arm.add_argument("-a", "--affinity", "--level", "--affinity-level", + type=lambda x: int(x, 0), + help="Affinity level (when multiple levels apply)") + g_arm.add_argument("-l", "--mpidr", type=lambda x: int(x, 0), + help="Multiprocessor Affinity Register") + g_arm.add_argument("-i", "--midr", type=lambda x: int(x, 0), + help="Main ID Register") + g_arm.add_argument("-r", "--running", + action=argparse.BooleanOptionalAction, + default=None, + help="Indicates if the processor is running or not") + g_arm.add_argument("--psci", "--psci-state", + type=lambda x: int(x, 0), + help="Power State Coordination Interface - PSCI state") + + # TODO: Add vendor-specific support + + # UEFI N.17 bitmaps (type and flags) + g_pei = parser.add_argument_group("ARM Processor Error Info (PEI)") + g_pei.add_argument("-t", "--type", nargs="+", + help=f"one or more error types: {error_types}") + g_pei.add_argument("-f", "--flags", nargs="*", + help=f"zero or more error flags: {flags}") + g_pei.add_argument("-V", "--pei-valid", "--error-valid", nargs="*", + help=f"zero or more PEI valid bits: {pei_valid_bits}") + + # UEFI N.17 Integer values + g_pei.add_argument("-m", "--multiple-error", nargs="+", + help="Number of errors: 0: Single error, 1: Multiple errors, 2-65535: Error count if known") + g_pei.add_argument("-e", "--error-info", nargs="+", + help="Error information (UEFI 2.10 tables N.18 to N.20)") + g_pei.add_argument("-p", "--physical-address", nargs="+", + help="Physical address") + g_pei.add_argument("-v", "--virtual-address", nargs="+", + help="Virtual address") + + # UEFI N.21 Context + g_ctx = parser.add_argument_group("Processor Context") + g_ctx.add_argument("--ctx-type", "--context-type", nargs="*", + help="Type of the context (0=ARM32 GPR, 5=ARM64 EL1, other values supported)") + g_ctx.add_argument("--ctx-size", "--context-size", nargs="*", + help="Minimal size of the context") + g_ctx.add_argument("--ctx-array", "--context-array", nargs="*", + help="Comma-separated arrays for each context") + + # Vendor-specific data + g_vendor = parser.add_argument_group("Vendor-specific data") + g_vendor.add_argument("--vendor", "--vendor-specific", nargs="+", + help="Vendor-specific byte arrays of data") + + def parse_args(self, args): + """Parse subcommand arguments""" + + cper = {} + pei = {} + ctx = {} + vendor = {} + + arg = vars(args) + + # Handle global parameters + if args.arm: + arm_valid_init = False + cper["valid"] = get_choice(name="valid", + value=args.arm, + choices=self.arm_valid_bits, + suffixes=["-error", "-err"]) + else: + cper["valid"] = 0 + arm_valid_init = True + + if "running" in arg: + if args.running: + cper["running-state"] = bit(0) + else: + cper["running-state"] = 0 + else: + cper["running-state"] = 0 + + if arm_valid_init: + if args.affinity: + cper["valid"] |= self.arm_valid_bits["affinity"] + + if args.mpidr: + cper["valid"] |= self.arm_valid_bits["mpidr"] + + if "running-state" in cper: + cper["valid"] |= self.arm_valid_bits["running"] + + if args.psci: + cper["valid"] |= self.arm_valid_bits["running"] + + # Handle PEI + if not args.type: + args.type = ["cache-error"] + + get_mult_choices( + pei, + name="valid", + values=args.pei_valid, + choices=self.pei_valid_bits, + suffixes=["-valid", "-info", "--information", "--addr"], + ) + get_mult_choices( + pei, + name="type", + values=args.type, + choices=self.pei_error_types, + suffixes=["-error", "-err"], + ) + get_mult_choices( + pei, + name="flags", + values=args.flags, + choices=self.pei_flags, + suffixes=["-error", "-cap"], + ) + get_mult_int(pei, "error-info", args.error_info) + get_mult_int(pei, "multiple-error", args.multiple_error) + get_mult_int(pei, "phy-addr", args.physical_address) + get_mult_int(pei, "virt-addr", args.virtual_address) + + # Handle context + get_mult_int(ctx, "type", args.ctx_type, allow_zero=True) + get_mult_int(ctx, "minimal-size", args.ctx_size, allow_zero=True) + get_mult_array(ctx, "register", args.ctx_array, allow_zero=True) + + get_mult_array(vendor, "bytes", args.vendor, max_val=255) + + # Store PEI + pei_data = bytearray() + default_flags = self.pei_flags["first"] + default_flags |= self.pei_flags["last"] + + error_info_num = 0 + + for i, p in pei.items(): # pylint: disable=W0612 + error_info_num += 1 + + # UEFI 2.10 doesn't define how to encode error information + # when multiple types are raised. So, provide a default only + # if a single type is there + if "error-info" not in p: + if p["type"] == bit(1): + p["error-info"] = 0x0091000F + if p["type"] == bit(2): + p["error-info"] = 0x0054007F + if p["type"] == bit(3): + p["error-info"] = 0x80D6460FFF + if p["type"] == bit(4): + p["error-info"] = 0x78DA03FF + + if "valid" not in p: + p["valid"] = 0 + if "multiple-error" in p: + p["valid"] |= self.pei_valid_bits["multiple-error"] + + if "flags" in p: + p["valid"] |= self.pei_valid_bits["flags"] + + if "error-info" in p: + p["valid"] |= self.pei_valid_bits["error-info"] + + if "phy-addr" in p: + p["valid"] |= self.pei_valid_bits["phy-addr"] + + if "virt-addr" in p: + p["valid"] |= self.pei_valid_bits["virt-addr"] + + # Version + data_add(pei_data, 0, 1) + + data_add(pei_data, ACPI_GHES_ARM_CPER_PEI_LENGTH, 1) + + data_add(pei_data, p["valid"], 2) + data_add(pei_data, p["type"], 1) + data_add(pei_data, p.get("multiple-error", 1), 2) + data_add(pei_data, p.get("flags", default_flags), 1) + data_add(pei_data, p.get("error-info", 0), 8) + data_add(pei_data, p.get("virt-addr", 0xDEADBEEF), 8) + data_add(pei_data, p.get("phy-addr", 0xABBA0BAD), 8) + + # Store Context + ctx_data = bytearray() + context_info_num = 0 + + if ctx: + for k in sorted(ctx.keys()): + context_info_num += 1 + + if "type" not in ctx: + ctx[k]["type"] = CONTEXT_AARCH64_EL1 + + if "register" not in ctx: + ctx[k]["register"] = [] + + reg_size = len(ctx[k]["register"]) + size = 0 + + if "minimal-size" in ctx: + size = ctx[k]["minimal-size"] + + size = max(size, reg_size) + + size = (size + 1) % 0xFFFE + + # Version + data_add(ctx_data, 0, 2) + + data_add(ctx_data, ctx[k]["type"], 2) + + data_add(ctx_data, 8 * size, 4) + + for r in ctx[k]["register"]: + data_add(ctx_data, r, 8) + + for i in range(reg_size, size): # pylint: disable=W0612 + data_add(ctx_data, 0, 8) + + # Vendor-specific bytes are not grouped + vendor_data = bytearray() + if vendor: + for k in sorted(vendor.keys()): + for b in vendor[k]["bytes"]: + data_add(vendor_data, b, 1) + + # Encode ARM Processor Error + data = bytearray() + + data_add(data, cper["valid"], 4) + + data_add(data, error_info_num, 2) + data_add(data, context_info_num, 2) + + # Calculate the length of the CPER data + cper_length = ACPI_GHES_ARM_CPER_LENGTH + cper_length += len(pei_data) + cper_length += len(vendor_data) + cper_length += len(ctx_data) + data_add(data, cper_length, 4) + + data_add(data, arg.get("affinity-level", 0), 1) + + # Reserved + data_add(data, 0, 3) + + data_add(data, arg.get("mpidr-el1", 0), 8) + data_add(data, arg.get("midr-el1", 0), 8) + data_add(data, cper["running-state"], 4) + data_add(data, arg.get("psci-state", 0), 4) + + # Add PEI + data.extend(pei_data) + data.extend(ctx_data) + data.extend(vendor_data) + + self.data = data + + def run(self, host, port): + """Execute QMP commands""" + + guid = to_guid(0xE19E3D16, 0xBC11, 0x11E4, + [0x9C, 0xAA, 0xC2, 0x05, + 0x1D, 0x5D, 0x46, 0xB0]) + + qmp_command(host, port, guid, self.data)scripts/ghes_inject.py new file +59
-0@@ -0,0 +1,59 @@ +#!/usr/bin/env python3 +# +# pylint: disable=C0301, C0114 +# SPDX-License-Identifier: GPL-2.0 +# +# Copyright (C) 2024 Mauro Carvalho Chehab <[email protected]> + +import argparse + +from arm_processor_error import ArmProcessorEinj + +EINJ_DESCRIPTION = """ +Handle ACPI GHESv2 error injection logic QEMU QMP interface.\n + +It allows using UEFI BIOS EINJ features to generate GHES records. + +It helps testing Linux CPER and GHES drivers and to test rasdaemon +error handling logic. + +Currently, it support ARM processor error injection for ARM processor +events, being compatible with UEFI 2.9A Errata. + +This small utility works together with those QEMU additions: +- https://gitlab.com/mchehab_kernel/qemu/-/tree/arm-error-inject-v2 +""" + +def main(): + """Main program""" + + # Main parser - handle generic args like QEMU QMP TCP socket options + parser = argparse.ArgumentParser(prog="einj.py", + formatter_class=argparse.RawDescriptionHelpFormatter, + usage="%(prog)s [options]", + description=EINJ_DESCRIPTION, + epilog="If a field is not defined, a default value will be applied by QEMU.") + + g_options = parser.add_argument_group("QEMU QMP socket options") + g_options.add_argument("-H", "--host", default="localhost", type=str, + help="host name") + g_options.add_argument("-P", "--port", default=4445, type=int, + help="TCP port number") + + arm_einj = ArmProcessorEinj() + + # Call subparsers + subparsers = parser.add_subparsers(dest='command') + + arm_einj.create_subparser(subparsers) + + args = parser.parse_args() + + # Handle subparser commands + if args.command == "arm": + arm_einj.parse_args(args) + arm_einj.run(args.host, args.port) + + +if __name__ == "__main__": + main()scripts/qmp_helper.py new file +249
-0@@ -0,0 +1,249 @@ +#!/usr/bin/env python3 +# +# pylint: disable=C0301, C0114, R0912, R0913, R0915, W0511 +# SPDX-License-Identifier: GPL-2.0 +# +# Copyright (C) 2024 Mauro Carvalho Chehab <[email protected]> + +import json +import socket +import sys + +from base64 import b64encode + +# +# Socket QMP send command +# +def qmp_command(host, port, guid, data): + """Send commands to QEMU though QMP TCP socket""" + + # Fill the commands to be sent + commands = [] + + # Needed to negotiate QMP and for QEMU to accept the command + commands.append('{ "execute": "qmp_capabilities" } ') + + base64_data = b64encode(bytes(data)).decode('ascii') + + cmd_arg = { + 'cper': { + 'notification-type': guid, + "raw-data": base64_data + } + } + + command = '{ "execute": "ghes-cper", ' + command += '"arguments": ' + json.dumps(cmd_arg) + " }" + + commands.append(command) + + s = socket.socket(socket.AF_INET, socket.SOCK_STREAM) + try: + s.connect((host, port)) + except ConnectionRefusedError: + sys.exit(f"Can't connect to QMP host {host}:{port}") + + data = s.recv(1024) + try: + obj = json.loads(data.decode("utf-8")) + except json.JSONDecodeError as e: + print(f"Invalid QMP answer: {e}") + s.close() + return + + if "QMP" not in obj: + print(f"Invalid QMP answer: {data.decode("utf-8")}") + s.close() + return + + for i, command in enumerate(commands): + s.sendall(command.encode("utf-8")) + data = s.recv(1024) + try: + obj = json.loads(data.decode("utf-8")) + except json.JSONDecodeError as e: + print(f"Invalid QMP answer: {e}") + s.close() + return + + if isinstance(obj.get("return"), dict): + if obj["return"]: + print(json.dumps(obj["return"])) + elif i > 0: + print("Error injected.") + elif isinstance(obj.get("error"), dict): + error = obj["error"] + print(f'{error["class"]}: {error["desc"]}') + else: + print(json.dumps(obj)) + + s.shutdown(socket.SHUT_WR) + while 1: + data = s.recv(1024) + if data == b"": + break + try: + obj = json.loads(data.decode("utf-8")) + except json.JSONDecodeError as e: + print(f"Invalid QMP answer: {e}") + s.close() + return + + if isinstance(obj.get("return"), dict): + print(json.dumps(obj["return"])) + if isinstance(obj.get("error"), dict): + error = obj["error"] + print(f'{error["class"]}: {error["desc"]}') + else: + print(json.dumps(obj)) + + s.close() + + +# +# Helper routines to handle multiple choice arguments +# +def get_choice(name, value, choices, suffixes=None): + """Produce a list from multiple choice argument""" + + new_values = 0 + + if not value: + return new_values + + for val in value.split(","): + val = val.lower() + + if suffixes: + for suffix in suffixes: + val = val.removesuffix(suffix) + + if val not in choices.keys(): + sys.exit(f"Error on '{name}': choice {val} is invalid.") + + val = choices[val] + + new_values |= val + + return new_values + + +def get_mult_array(mult, name, values, allow_zero=False, max_val=None): + """Add numbered hashes from integer lists""" + + if not allow_zero: + if not values: + return + else: + if values is None: + return + + if not values: + i = 0 + if i not in mult: + mult[i] = {} + + mult[i][name] = [] + return + + i = 0 + for value in values: + for val in value.split(","): + try: + val = int(val, 0) + except ValueError: + sys.exit(f"Error on '{name}': {val} is not an integer") + + if val < 0: + sys.exit(f"Error on '{name}': {val} is not unsigned") + + if max_val and val > max_val: + sys.exit(f"Error on '{name}': {val} is too little") + + if i not in mult: + mult[i] = {} + + if name not in mult[i]: + mult[i][name] = [] + + mult[i][name].append(val) + + i += 1 + + +def get_mult_choices(mult, name, values, choices, + suffixes=None, allow_zero=False): + """Add numbered hashes from multiple choice arguments""" + + if not allow_zero: + if not values: + return + else: + if values is None: + return + + i = 0 + for val in values: + new_values = get_choice(name, val, choices, suffixes) + + if i not in mult: + mult[i] = {} + + mult[i][name] = new_values + i += 1 + + +def get_mult_int(mult, name, values, allow_zero=False): + """Add numbered hashes from integer arguments""" + if not allow_zero: + if not values: + return + else: + if values is None: + return + + i = 0 + for val in values: + try: + val = int(val, 0) + except ValueError: + sys.exit(f"Error on '{name}': {val} is not an integer") + + if val < 0: + sys.exit(f"Error on '{name}': {val} is not unsigned") + + if i not in mult: + mult[i] = {} + + mult[i][name] = val + i += 1 + + +# +# Data encode helper functions +# +def bit(b): + """Simple macro to define a bit on a bitmask""" + return 1 << b + + +def data_add(data, value, num_bytes): + """Adds bytes from value inside a bitarray""" + + data.extend(value.to_bytes(num_bytes, byteorder="little")) + +def to_guid(time_low, time_mid, time_high, nodes): + """Create an GUID string""" + + assert(len(nodes) == 8) + + clock = nodes[0] << 8 | nodes[1] + + node = 0 + for i in range(2, len(nodes)): + node = node << 8 | nodes[i] + + s = f"{time_low:08x}-{time_mid:04x}-" + s += f"{time_high:04x}-{clock:04x}-{node:012x}" + + return s
Re: [PATCH v5 4/7] acpi/ghes: Support GPIO error source
In reply to Igor MammedovEm Tue, 6 Aug 2024 11:32:19 +0200
Igor Mammedov <[email protected]> escreveu:
Quoted 8 lines
hw/acpi/ghes.c static void build_ghes_v2(GArray *table_data, int source_id, BIOSLinker *linker) · line 334
Quoted 6 lines
hw/acpi/ghes.c +2
-0@@ -327,6 +330,9 @@ static void build_ghes_v2(GArray *table_data, int source_id, BIOSLinker *linker)*/ build_ghes_hw_error_notification (table_data,ACPI_GHES_NOTIFY_SEA );break ; +case ACPI_HEST_SRC_ID_GPIO : +build_ghes_hw_error_notification (table_data,ACPI_GHES_NOTIFY_GPIO );perhaps
ACPI_GHES_NOTIFY_EXTERNALfits better here?
Symbol already used to map the 12 possible notification types from ACPI spec. I did a:
sed s,ACPI_HEST_SRC_ID_GED_INT,ACPI_HEST_NOTIFY_EXTERNAL,
instead.
Thanks,
Mauro
Re: [PATCH v5 6/7] acpi/ghes: add support for generic error injection via QAPI
In reply to Igor MammedovEm Tue, 6 Aug 2024 16:31:13 +0200
Igor Mammedov <[email protected]> escreveu:
Quoted 6 lines
PS:
looking at the code,ACPI_GHES_MAX_RAW_DATA_LENGTHis 1K and it is the total size of a error block for a error source.However
acpi_hest_ghes.rst(3) says it should be 4K, am I mistaken?
Maybe Jonathan knows better, but I guess the 1K was just some arbitrary limit to prevent a too big CPER. The 4K limit described at acpi_hest_ghes.rst could be just some limit to cope with the current bios implementation, but I didn't check myself how this is implemented there.
I was unable to find any limit at the specs. Yet, if you look at:
https://uefi.org/specs/UEFI/2.10/Apx_N_Common_Platform_Error_Record.html#arm-processor-error-section
The processor Error Information Structure, starting at offset 40, can go up to 255*32, meaning an offset of 8200, which is bigger than 4K.
Going further, processor context can have up to 65535 (spec actually says 65536, but that sounds a typo, as the size is stored on an uint16_t), containing multiple register values there (the spec calls its length as "P").
So, the CPER record could, in theory, have:
8200 + (65535 * P) + sizeof(vendor-specicific-info)
The CPER length is stored in Section Length record, which is uint32_t.
So, I'd say that the GHES record can theoretically be a lot bigger than 4K.
Thanks,
Mauro
Re: [PATCH v5 6/7] acpi/ghes: add support for generic error injection via QAPI
Quoted 16 lines · On Wed, 7 Aug 2024 09:47:50 +0200 Mauro Carvalho Chehab…
Em Tue, 6 Aug 2024 16:31:13 +0200
Igor Mammedov <[email protected]> escreveu:Quoted 6 lines
PS:
looking at the code,ACPI_GHES_MAX_RAW_DATA_LENGTHis 1K and it is the total size of a error block for a error source.However
acpi_hest_ghes.rst(3) says it should be 4K, am I mistaken?Maybe Jonathan knows better, but I guess the 1K was just some arbitrary limit to prevent a too big CPER. The 4K limit described at
acpi_hest_ghes.rstcould be just some limit to cope with the current bios implementation, but I didn't check myself how this is implemented there.
Quoted 3 lines
I was unable to find any limit at the specs. Yet, if you look at:
https://uefi.org/specs/UEFI/2.10/Apx_N_Common_Platform_Error_Record.html#arm-processor-error-section
I think both limits are just made up. You can in theory log huge error records. Just not one does.
Quoted 10 lines
The processor Error Information Structure, starting at offset 40, can go up to 255*32, meaning an offset of 8200, which is bigger than 4K.
Going further, processor context can have up to 65535 (spec actually says 65536, but that sounds a typo, as the size is stored on an
uint16_t), containing multiple register values there (the spec calls its length as "P").
Quoted 8 lines
So, the CPER record could, in theory, have:
8200 + (65535 * P) + sizeof(vendor-specicific-info)The CPER length is stored in Section Length record, which is
uint32_t.So, I'd say that the GHES record can theoretically be a lot bigger than 4K.
Agreed - but I don't think we care for testing as long as it's
big enough for plausible records. Unless you really want
to fuzz the limits?
Jonathan
Quoted 3 lines
Thanks,
Mauro
Re: [PATCH v5 6/7] acpi/ghes: add support for generic error injection via QAPI
Em Wed, 7 Aug 2024 10:34:36 +0100
Jonathan Cameron <[email protected]> escreveu:
Quoted 19 lines
Quoted 16 lines · On Wed, 7 Aug 2024 09:47:50 +0200 Mauro Carvalho Chehab…
Em Tue, 6 Aug 2024 16:31:13 +0200
Igor Mammedov <[email protected]> escreveu:Quoted 6 lines
PS:
looking at the code,ACPI_GHES_MAX_RAW_DATA_LENGTHis 1K and it is the total size of a error block for a error source.However
acpi_hest_ghes.rst(3) says it should be 4K, am I mistaken?Maybe Jonathan knows better, but I guess the 1K was just some arbitrary limit to prevent a too big CPER. The 4K limit described at
acpi_hest_ghes.rstcould be just some limit to cope with the current bios implementation, but I didn't check myself how this is implemented there.
Quoted 6 lines
Quoted 3 lines
I was unable to find any limit at the specs. Yet, if you look at:
https://uefi.org/specs/UEFI/2.10/Apx_N_Common_Platform_Error_Record.html#arm-processor-error-section
I think both limits are just made up. You can in theory log huge error records. Just not one does.
If both are made up, I would sync them, either patching the documentation or the ghes driver.
Quoted 14 lines
Quoted 14 lines
The processor Error Information Structure, starting at offset 40, can go up to 255*32, meaning an offset of 8200, which is bigger than 4K.
Going further, processor context can have up to 65535 (spec actually says 65536, but that sounds a typo, as the size is stored on an
uint16_t), containing multiple register values there (the spec calls its length as "P").So, the CPER record could, in theory, have:
8200 + (65535 * P) + sizeof(vendor-specicific-info)
Quoted 8 lines
Quoted 5 lines
The CPER length is stored in Section Length record, which is
uint32_t.So, I'd say that the GHES record can theoretically be a lot bigger than 4K.
Agreed - but I don't think we care for testing as long as it's
big enough for plausible records. Unless you really want
to fuzz the limits?
Fuzz the limits could be interesting, but it is not on my current plans.
Yet, 1K could be a little bit short for ARM CPER.
See: N.26 ARMv8 AArch64 GPRs (Type 4) has 256 bytes for registers, plus 8 bytes for the header. So, a total size of 264 bytes, for a single context register dump. I would expect that, in real life, type 4 to always be reported on aarch64, on BIOS with context register support. Maybe other types could also be dumped altogether (like context registers for EL1, EL2 and/or EL3).
If just one type 4 context is encoded, it means that, 1K has space for 23 errors (of a max limit of 255).
Just looking at the maximum number, my feeling is that 1K might be too short to simulate some real life reports, but that depends on how firmware is actually grouping such events.
So, maybe this could be expanded to, let's say, 4K, thus aligning with the ReST documentation.
Regards,
Mauro
Re: [PATCH v5 6/7] acpi/ghes: add support for generic error injection via QAPI
In reply to Jonathan CameronQuoted 19 lines · On Wed, 7 Aug 2024 10:34:36 +0100 Jonathan Cameron…
Quoted 16 lines · On Wed, 7 Aug 2024 09:47:50 +0200 Mauro Carvalho Chehab…
Em Tue, 6 Aug 2024 16:31:13 +0200
Igor Mammedov <[email protected]> escreveu:Quoted 6 lines
PS:
looking at the code,ACPI_GHES_MAX_RAW_DATA_LENGTHis 1K and it is the total size of a error block for a error source.However
acpi_hest_ghes.rst(3) says it should be 4K, am I mistaken?Maybe Jonathan knows better, but I guess the 1K was just some arbitrary limit to prevent a too big CPER. The 4K limit described at
acpi_hest_ghes.rstcould be just some limit to cope with the current bios implementation, but I didn't check myself how this is implemented there.
Quoted 6 lines
Quoted 3 lines
I was unable to find any limit at the specs. Yet, if you look at:
https://uefi.org/specs/UEFI/2.10/Apx_N_Common_Platform_Error_Record.html#arm-processor-error-section
I think both limits are just made up. You can in theory log huge error records. Just not one does.
What I care about is what we actually allocate vs what we promised in docs. Given that it's harder to change actual size (we would need a compat handling here not to break old machine types), I would vote for syncing docs to match code.
A separate stand-alone patch for fixing it would do, or it could be a part of series.
Also I'd like another pair of eyes to look at it to confirm actual size we allocate, in case I'm not seeing it right.
Quoted 27 lines
Quoted 9 lines
The processor Error Information Structure, starting at offset 40, can go up to 255*32, meaning an offset of 8200, which is bigger than 4K.
Going further, processor context can have up to 65535 (spec actually says 65536, but that sounds a typo, as the size is stored on an
uint16_t), containing multiple register values there (the spec calls its length as "P").Quoted 8 lines
So, the CPER record could, in theory, have:
8200 + (65535 * P) + sizeof(vendor-specicific-info)The CPER length is stored in Section Length record, which is
uint32_t.So, I'd say that the GHES record can theoretically be a lot bigger than 4K.
Agreed - but I don't think we care for testing as long as it's
big enough for plausible records. Unless you really want
to fuzz the limits?Jonathan
Quoted 3 lines
Thanks,
Mauro
Re: [PATCH v5 6/7] acpi/ghes: add support for generic error injection via QAPI
In reply to Mauro Carvalho ChehabQuoted 68 lines · On Wed, 7 Aug 2024 15:23:57 +0200 Mauro Carvalho Chehab…
Em Wed, 7 Aug 2024 10:34:36 +0100
Jonathan Cameron <[email protected]> escreveu:Quoted 19 lines
Quoted 16 lines · On Wed, 7 Aug 2024 09:47:50 +0200 Mauro Carvalho Chehab…
Em Tue, 6 Aug 2024 16:31:13 +0200
Igor Mammedov <[email protected]> escreveu:Quoted 6 lines
PS:
looking at the code,ACPI_GHES_MAX_RAW_DATA_LENGTHis 1K and it is the total size of a error block for a error source.However
acpi_hest_ghes.rst(3) says it should be 4K, am I mistaken?Maybe Jonathan knows better, but I guess the 1K was just some arbitrary limit to prevent a too big CPER. The 4K limit described at
acpi_hest_ghes.rstcould be just some limit to cope with the current bios implementation, but I didn't check myself how this is implemented there.Quoted 6 lines
Quoted 3 lines
I was unable to find any limit at the specs. Yet, if you look at:
https://uefi.org/specs/UEFI/2.10/Apx_N_Common_Platform_Error_Record.html#arm-processor-error-section
I think both limits are just made up. You can in theory log huge error records. Just not one does.
If both are made up, I would sync them, either patching the documentation or the ghes driver.
Quoted 14 lines
Quoted 14 lines
The processor Error Information Structure, starting at offset 40, can go up to 255*32, meaning an offset of 8200, which is bigger than 4K.
Going further, processor context can have up to 65535 (spec actually says 65536, but that sounds a typo, as the size is stored on an
uint16_t), containing multiple register values there (the spec calls its length as "P").So, the CPER record could, in theory, have:
8200 + (65535 * P) + sizeof(vendor-specicific-info)Quoted 8 lines
Quoted 5 lines
The CPER length is stored in Section Length record, which is
uint32_t.So, I'd say that the GHES record can theoretically be a lot bigger than 4K.
Agreed - but I don't think we care for testing as long as it's
big enough for plausible records. Unless you really want
to fuzz the limits?Fuzz the limits could be interesting, but it is not on my current plans.
Yet, 1K could be a little bit short for ARM CPER.
See: N.26 ARMv8 AArch64 GPRs (Type 4) has 256 bytes for registers, plus 8 bytes for the header. So, a total size of 264 bytes, for a single context register dump. I would expect that, in real life, type 4 to always be reported on aarch64, on BIOS with context register support. Maybe other types could also be dumped altogether (like context registers for EL1, EL2 and/or EL3).
Quoted 7 lines
If just one type 4 context is encoded, it means that, 1K has space for 23 errors (of a max limit of 255).
Just looking at the maximum number, my feeling is that 1K might be too short to simulate some real life reports, but that depends on how firmware is actually grouping such events.
per my knowledge firmware is out of picture here, since all it does in HEST case is allocate continuous space for 'etc/hardware_errors' blob as QEMU told it.
Quoted 3 lines
So, maybe this could be expanded to, let's say, 4K, thus aligning with the ReST documentation.
maybe to get moving, 1st get your series in with docs fixed to today limit.
And then increase error_block size to desired value on top of that as it's really not relevant to what you are doing here.
Quoted 3 lines
Regards,
Mauro
Re: [PATCH v5 6/7] acpi/ghes: add support for generic error injection via QAPI
In reply to Igor MammedovQuoted 157 lines · On Tue, 6 Aug 2024 16:31:13 +0200 Igor Mammedov <[email protected]> wrote:
Quoted 24 lines · On Fri, 2 Aug 2024 23:44:01 +0200 Mauro Carvalho Chehab…
Provide a generic interface for error injection via GHESv2.
This patch is co-authored:
- original ghes logic to inject a simple ARM record by Shiju Jose;
- generic logic to handle block addresses by Jonathan Cameron;
- generic GHESv2 error inject by Mauro Carvalho Chehab;Co-authored-by Jonathan Cameron <[email protected]>Co-authored-by Shiju Jose <[email protected]>Co-authored-by Mauro Carvalho Chehab <[email protected]>Cc Jonathan Cameron <[email protected]>Cc Shiju Jose <[email protected]>Signed-off-by Mauro Carvalho Chehab <[email protected]>--- hw/acpi/ghes.c | 159 ++++++++++++++++++++++++++++++++++++++--- hw/acpi/ghes_cper.c | 2 +- include/hw/acpi/ghes.h | 3 + 3 files changed, 152 insertions(+), 12 deletions(-)hw/acpi/ghes.c +0
-0hw/acpi/ghes.c void acpi_ghes_add_fw_cfg(AcpiGhesState *ags, FWCfgState *s, · line 398
Quoted 4 lines
hw/acpi/ghes.c +1
-0@@ -395,23 +395,22 @@ void acpi_ghes_add_fw_cfg(AcpiGhesState *ags, FWCfgState *s, ags->present = true; } +static uint64_t ghes_get_state_start_address (void )
ghes_get_hardware_errors_address()might better reflect what address it will returnQuoted 18 lines
hw/acpi/ghes.c +9
-4+{ +AcpiGedState *acpi_ged_state = +ACPI_GED (object_resolve_path_type ("" ,TYPE_ACPI_GED ,NULL )); +AcpiGhesState *ags = &acpi_ged_state->ghes_state; + +return le64_to_cpu (ags->ghes_addr_le); +} +int acpi_ghes_record_errors (uint8_t source_id,uint64_t physical_address) {uint64_t error_block_addr, read_ack_register_addr, read_ack_register =0 ; -uint64_t start_addr; +uint64_t start_addr =ghes_get_state_start_address ();bool ret =-1 ; -AcpiGedState *acpi_ged_state; -AcpiGhesState *ags; -assert (source_id <ACPI_HEST_SRC_ID_RESERVED );hw/acpi/ghes.c void acpi_ghes_add_fw_cfg(AcpiGhesState *ags, FWCfgState *s, · line 415
Quoted 10 lines
hw/acpi/ghes.c +0
-7- acpi_ged_state =ACPI_GED (object_resolve_path_type ("" ,TYPE_ACPI_GED , -NULL )); -g_assert (acpi_ged_state); - ags = &acpi_ged_state->ghes_state; - - start_addr =le64_to_cpu (ags->ghes_addr_le); -if (physical_address) { start_addr += source_id *sizeof (uint64_t );above should be a separate patch
Quoted 26 lines
hw/acpi/ghes.c +21
-0@@ -448,9 +447,147 @@ int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address)return ret; } +/* +* Error register block data layout +* +* | +---------------------+ ges.ghes_addr_le +* | |error_block_address0 | +* | +---------------------+ +* | |error_block_address1 | +* | +---------------------+ --+-- +* | | ............. | GHES_ADDRESS_SIZE +* | +---------------------+ --+-- +* | |error_block_addressN | +* | +---------------------+ +* | | read_ack0 | +* | +---------------------+ --+-- +* | | read_ack1 | GHES_ADDRESS_SIZE +* | +---------------------+ --+-- +* | | ............. | +* | +---------------------+ +* | | read_ackN | +* | +---------------------+ --+-- +* | | CPER | | hw/acpi/ghes.c int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address) · line 480
Quoted 10 lines
hw/acpi/ghes.c +10
-0+* | | .... | GHES_MAX_RAW_DATA_LENGT +* | | CPER | | +* | +---------------------+ --+-- +* | | .......... | +* | +---------------------+ +* | | CPER | +* | | .... | +* | | CPER | +* | +---------------------+ +*/ no need to duplicate
docs/specs/acpi_hest_ghes.rst,
I'd just reffer to it and maybe add short comment as to why it's mentioned.Quoted 22 lines
hw/acpi/ghes.c +22
-0+/* Map from uint32_t notify to entry offset in GHES */ +static const uint8_t error_source_to_index[] = {0xff ,0xff ,0xff ,0xff , +0xff ,0xff ,0xff ,1 ,0 }; + +static bool ghes_get_addr (uint32_t notify,uint64_t *error_block_addr, +uint64_t *read_ack_addr) +{ +uint64_t base; + +if (notify >=ACPI_GHES_NOTIFY_RESERVED ) { +return false; + } + +/* Find and check the source id for this new CPER */ +if (error_source_to_index[notify] ==0xff ) { +return false; + } + + base =ghes_get_state_start_address (); + + *read_ack_addr = base + + ACPI_GHES_ERROR_SOURCE_COUNT * sizeof(uint64_t) +hw/acpi/ghes.c int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address) · line 513
Quoted 10 lines
hw/acpi/ghes.c +10
-0+ error_source_to_index[notify] *sizeof (uint64_t ); + +/* Could also be read back from the error_block_address register */ + *error_block_addr = base + +ACPI_GHES_ERROR_SOURCE_COUNT *sizeof (uint64_t ) + +ACPI_GHES_ERROR_SOURCE_COUNT *sizeof (uint64_t ) + + error_source_to_index[notify] *ACPI_GHES_MAX_RAW_DATA_LENGTH ; + +return true; +}I don't like all this pointer math, which is basically a reverse engineered QEMU actions on startup + guest provided etc/hardware_errors address.
For once, it assumes error_source_to_index[] matches order in which HEST error sources were described, which is fragile.
2nd: migration-wive it's disaster, since old/new HEST/hardware_errors tables in RAM migrated from older version might not match above assumptions of target QEMU.
I see 2 ways to rectify it:
1st: preferred/cleanest would be to tell QEMU (viafw_cfg) address of HEST table
in guest RAM, like we do with etc/hardware_errors, see
build_ghes_error_table()
...
tell firmware to writehardware_errorsGPA into
and then fetch from HEST table in RAM, the guest patched error/ack addresses for givensource_id
Quoted 7 lines
code-wise: relatively simple once one wraps their own head over
how this whole APEI thing works in QEMU
workflow is described indocs/specs/acpi_hest_ghes.rstlook to me as sufficient to grasp it.
(but my view is very biased given my prior knowledge,
aka: docs/comments/examples wrt acpi patching are good enough)
(if it's not clear how to do it, ask me for pointers)
Hi Igor, I think I follow what you mean but maybe this question will reveal otherwise. HEST is currently in ACPI_BUILD_TABLE_FILE.
Would you suggest splitting it to it's own file, or using table_offsets to get the offset in ACPI_BUILD_TABLE_FILE GPA?
Re: [PATCH v5 6/7] acpi/ghes: add support for generic error injection via QAPI
Quoted 168 lines · On Wed, 7 Aug 2024 15:25:47 +0100 Jonathan Cameron…
Quoted 157 lines · On Tue, 6 Aug 2024 16:31:13 +0200 Igor Mammedov <[email protected]> wrote:
Quoted 24 lines · On Fri, 2 Aug 2024 23:44:01 +0200 Mauro Carvalho Chehab…
Provide a generic interface for error injection via GHESv2.
This patch is co-authored:
- original ghes logic to inject a simple ARM record by Shiju Jose;
- generic logic to handle block addresses by Jonathan Cameron;
- generic GHESv2 error inject by Mauro Carvalho Chehab;Co-authored-by Jonathan Cameron <[email protected]>Co-authored-by Shiju Jose <[email protected]>Co-authored-by Mauro Carvalho Chehab <[email protected]>Cc Jonathan Cameron <[email protected]>Cc Shiju Jose <[email protected]>Signed-off-by Mauro Carvalho Chehab <[email protected]>--- hw/acpi/ghes.c | 159 ++++++++++++++++++++++++++++++++++++++--- hw/acpi/ghes_cper.c | 2 +- include/hw/acpi/ghes.h | 3 + 3 files changed, 152 insertions(+), 12 deletions(-)hw/acpi/ghes.c +0
-0hw/acpi/ghes.c void acpi_ghes_add_fw_cfg(AcpiGhesState *ags, FWCfgState *s, · line 398
Quoted 4 lines
hw/acpi/ghes.c +1
-0@@ -395,23 +395,22 @@ void acpi_ghes_add_fw_cfg(AcpiGhesState *ags, FWCfgState *s, ags->present = true; } +static uint64_t ghes_get_state_start_address (void )
ghes_get_hardware_errors_address()might better reflect what address it will returnQuoted 18 lines
hw/acpi/ghes.c +9
-4+{ +AcpiGedState *acpi_ged_state = +ACPI_GED (object_resolve_path_type ("" ,TYPE_ACPI_GED ,NULL )); +AcpiGhesState *ags = &acpi_ged_state->ghes_state; + +return le64_to_cpu (ags->ghes_addr_le); +} +int acpi_ghes_record_errors (uint8_t source_id,uint64_t physical_address) {uint64_t error_block_addr, read_ack_register_addr, read_ack_register =0 ; -uint64_t start_addr; +uint64_t start_addr =ghes_get_state_start_address ();bool ret =-1 ; -AcpiGedState *acpi_ged_state; -AcpiGhesState *ags; -assert (source_id <ACPI_HEST_SRC_ID_RESERVED );hw/acpi/ghes.c void acpi_ghes_add_fw_cfg(AcpiGhesState *ags, FWCfgState *s, · line 415
Quoted 10 lines
hw/acpi/ghes.c +0
-7- acpi_ged_state =ACPI_GED (object_resolve_path_type ("" ,TYPE_ACPI_GED , -NULL )); -g_assert (acpi_ged_state); - ags = &acpi_ged_state->ghes_state; - - start_addr =le64_to_cpu (ags->ghes_addr_le); -if (physical_address) { start_addr += source_id *sizeof (uint64_t );above should be a separate patch
Quoted 26 lines
hw/acpi/ghes.c +21
-0@@ -448,9 +447,147 @@ int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address)return ret; } +/* +* Error register block data layout +* +* | +---------------------+ ges.ghes_addr_le +* | |error_block_address0 | +* | +---------------------+ +* | |error_block_address1 | +* | +---------------------+ --+-- +* | | ............. | GHES_ADDRESS_SIZE +* | +---------------------+ --+-- +* | |error_block_addressN | +* | +---------------------+ +* | | read_ack0 | +* | +---------------------+ --+-- +* | | read_ack1 | GHES_ADDRESS_SIZE +* | +---------------------+ --+-- +* | | ............. | +* | +---------------------+ +* | | read_ackN | +* | +---------------------+ --+-- +* | | CPER | | hw/acpi/ghes.c int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address) · line 480
Quoted 10 lines
hw/acpi/ghes.c +10
-0+* | | .... | GHES_MAX_RAW_DATA_LENGT +* | | CPER | | +* | +---------------------+ --+-- +* | | .......... | +* | +---------------------+ +* | | CPER | +* | | .... | +* | | CPER | +* | +---------------------+ +*/ no need to duplicate
docs/specs/acpi_hest_ghes.rst,
I'd just reffer to it and maybe add short comment as to why it's mentioned.Quoted 22 lines
hw/acpi/ghes.c +22
-0+/* Map from uint32_t notify to entry offset in GHES */ +static const uint8_t error_source_to_index[] = {0xff ,0xff ,0xff ,0xff , +0xff ,0xff ,0xff ,1 ,0 }; + +static bool ghes_get_addr (uint32_t notify,uint64_t *error_block_addr, +uint64_t *read_ack_addr) +{ +uint64_t base; + +if (notify >=ACPI_GHES_NOTIFY_RESERVED ) { +return false; + } + +/* Find and check the source id for this new CPER */ +if (error_source_to_index[notify] ==0xff ) { +return false; + } + + base =ghes_get_state_start_address (); + + *read_ack_addr = base + + ACPI_GHES_ERROR_SOURCE_COUNT * sizeof(uint64_t) +hw/acpi/ghes.c int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address) · line 513
Quoted 10 lines
hw/acpi/ghes.c +10
-0+ error_source_to_index[notify] *sizeof (uint64_t ); + +/* Could also be read back from the error_block_address register */ + *error_block_addr = base + +ACPI_GHES_ERROR_SOURCE_COUNT *sizeof (uint64_t ) + +ACPI_GHES_ERROR_SOURCE_COUNT *sizeof (uint64_t ) + + error_source_to_index[notify] *ACPI_GHES_MAX_RAW_DATA_LENGTH ; + +return true; +}I don't like all this pointer math, which is basically a reverse engineered QEMU actions on startup + guest provided etc/hardware_errors address.
For once, it assumes error_source_to_index[] matches order in which HEST error sources were described, which is fragile.
2nd: migration-wive it's disaster, since old/new HEST/hardware_errors tables in RAM migrated from older version might not match above assumptions of target QEMU.
I see 2 ways to rectify it:
1st: preferred/cleanest would be to tell QEMU (viafw_cfg) address of HEST table
in guest RAM, like we do with etc/hardware_errors, see
build_ghes_error_table()
...
tell firmware to writehardware_errorsGPA into
and then fetch from HEST table in RAM, the guest patched error/ack addresses for givensource_idQuoted 7 lines
code-wise: relatively simple once one wraps their own head over
how this whole APEI thing works in QEMU
workflow is described indocs/specs/acpi_hest_ghes.rstlook to me as sufficient to grasp it.
(but my view is very biased given my prior knowledge,
aka: docs/comments/examples wrt acpi patching are good enough)
(if it's not clear how to do it, ask me for pointers)
Quoted 4 lines
Hi Igor, I think I follow what you mean but maybe this question will reveal otherwise. HEST is currently in
ACPI_BUILD_TABLE_FILE.
Would you suggest splitting it to it's own file, or usingtable_offsetsto get the offset inACPI_BUILD_TABLE_FILEGPA?
yep, offset taken right before HEST is to be created
doc comment for bios_linker_loader_write_pointer() explains how it works
we need something like:
bios_linker_loader_write_pointer(linker,
ACPI_HEST_TABLE_ADDR_FW_CFG_FILE, 0, sizeof(uint64_t),
ACPI_BUILD_TABLE_FILE, hest_offset_within_ACPI_BUILD_TABLE_FILE); to register new file see:
a08a64627 ACPI: Record the Generic Error Status Block address and to avoid copy past error maybe
136fc6aa2 ACPI: Avoid infinite recursion when dump-vmstat
for this needs to be limited to new machine types and keep
old ones without this new feature. (I'd use hw_compat_ machinery for that)
while at it we should rename
ACPI_GHES_DATA_ADDR_FW_CFG_FILE -> ACPI_GHES_ERRORS_ADDR_FW_CFG_FILE
Re: [PATCH v5 5/7] qapi/ghes-cper: add an interface to do generic CPER error injection
In reply to Mauro Carvalho ChehabQuoted 27 lines · Mauro Carvalho Chehab
Creates a QMP command to be used for generic ACPI APEI hardware error injection (HEST) via GHESv2.
The actual GHES code will be added at the followup patch.
Signed-off-by Mauro Carvalho Chehab <[email protected]>--- MAINTAINERS | 7 +++++ hw/acpi/Kconfig | 5 ++++ hw/acpi/ghes_cper.c | 45 ++++++++++++++++++++++++++++++++ hw/acpi/ghes_cper_stub.c | 18 +++++++++++++ hw/acpi/meson.build | 2 ++ hw/arm/Kconfig | 5 ++++ include/hw/acpi/ghes.h | 7 +++++ qapi/ghes-cper.json | 55 ++++++++++++++++++++++++++++++++++++++++ qapi/meson.build | 1 + qapi/qapi-schema.json | 1 + 10 files changed, 146 insertions(+) create mode 100644 hw/acpi/ghes_cper.c create mode 100644 hw/acpi/ghes_cper_stub.c create mode 100644 qapi/ghes-cper.jsonMAINTAINERS +0
-0
MAINTAINERS F: hw/acpi/ghes.c · line 2084
Quoted 10 lines
MAINTAINERS +7
-0@@ -2075,6 +2075,13 @@ F: hw/acpi/ghes.c F: include/hw/acpi/ghes.h F: docs/specs/acpi_hest_ghes.rst +ACPI/HEST/GHES/ARM processor CPER +R: Mauro Carvalho Chehab <[email protected]> +S: Maintained +F: hw/arm/ghes_cper.c +F: hw/acpi/ghes_cper_stub.c +F: qapi/ghes-cper.json +
Here's the reason for creating a new QAPI module instead of adding to existing module acpi.json: different maintainers.
Hypothetical question: if we didn't care for that, would this go into qapi/acpi.json?
If yes, then should we call it acpi-ghes-cper.json or acpi-ghes.json instead?
Quoted 3 lines
MAINTAINERS +0
-0ppc4xx L: [email protected] S: Orphan
[...]
Quoted 6 lines
qapi/ghes-cper.json new file +0
-0
qapi/ghes-cper.json line 10
Quoted 10 lines
qapi/ghes-cper.json new file +10
-0@@ -0,0 +1,55 @@ +# -*- Mode: Python -*- +# vim: filetype=python + +## +# = GHESv2 CPER Error Injection +# +# These are defined at +# ACPI 6.2: 18.3.2.8 Generic Hardware Error Source version 2 +# (GHESv2 - Type 10) +##
Feels a bit terse. These what?
The reference could be clearer: "defined in the ACPI Specification 6.2, section 18.3.2.8 Generic Hardware Error Source version 2". A link would be nice, if it's stable.
qapi/ghes-cper.json line 22
Quoted 12 lines
qapi/ghes-cper.json new file +12
-0+ +## +# @CommonPlatformErrorRecord: +# +# Common Platform Error Record - CPER - as defined at the UEFI +# specification. See +# https://uefi.org/specs/UEFI/2.10/Apx_N_Common_Platform_Error_Record.html#record-header +# for more details. +# +# @notification-type: pre-assigned GUID string indicating the record +# association with an error event notification type, as defined +# at https://uefi.org/specs/UEFI/2.10/Apx_N_Common_Platform_Error_Record.html#record-header
Please indent four spaces for consistency, like this:
# @notification-type: pre-assigned GUID string indicating the record
# association with an error event notification type, as defined at
# https://uefi.org/specs/UEFI/2.10/Apx_N_Common_Platform_Error_Record.html#record-header
qapi/ghes-cper.json line 25
Quoted 3 lines
qapi/ghes-cper.json new file +3
-0+# +# @raw-data: Contains a base64 encoded string with the payload of +# the CPER.
Suggest
# @raw-data: payload of the CPER encoded in base64
Have you considered naming this @payload instead?
Quoted 5 lines
qapi/ghes-cper.json new file +5
-0+# +# Since: 9.2 +## +{ 'struct': 'CommonPlatformErrorRecord', + 'data': {
qapi/ghes-cper.json line 40
Quoted 10 lines
qapi/ghes-cper.json new file +10
-0+ 'notification-type': 'str', + 'raw-data': 'str' + } +} + +## +# @ghes-cper: +# +# Inject ARM Processor error with data to be filled according with +# ACPI 6.2 GHESv2 spec.
according to
(Beware, I'm not a native speaker)
Quoted 39 lines
qapi/ghes-cper.json new file +15
-0+# +# @cper: a single CPER record to be sent to the guest OS. +# +# Features: +# +# @unstable: This command is experimental. +# +# Since: 9.2 +## +{ 'command': 'ghes-cper', + 'data': { + 'cper': 'CommonPlatformErrorRecord' + }, + 'features': [ 'unstable' ] +}qapi/meson.build +1
-0@@ -35,6 +35,7 @@ qapi_all_modules = [ 'dump', 'ebpf', 'error', + 'ghes-cper', 'introspect', 'job', 'machine-common',qapi/qapi-schema.json +1
-0@@ -75,6 +75,7 @@ { 'include': 'misc-target.json' } { 'include': 'audio.json' } { 'include': 'acpi.json' } +{ 'include': 'ghes-cper.json' } { 'include': 'pci.json' } { 'include': 'stats.json' } { 'include': 'virtio.json' }
Re: [PATCH v5 6/7] acpi/ghes: add support for generic error injection via QAPI
In reply to Igor MammedovEm Tue, 6 Aug 2024 16:31:13 +0200
Igor Mammedov <[email protected]> escreveu:
Quoted 28 lines
hw/acpi/ghes.c int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address) · line 513
Quoted 8 lines
hw/acpi/ghes.c +8
-0+/* Could also be read back from the error_block_address register */ + *error_block_addr = base + +ACPI_GHES_ERROR_SOURCE_COUNT *sizeof (uint64_t ) + +ACPI_GHES_ERROR_SOURCE_COUNT *sizeof (uint64_t ) + + error_source_to_index[notify] *ACPI_GHES_MAX_RAW_DATA_LENGTH ; + +return true; +}I don't like all this pointer math, which is basically a reverse engineered QEMU actions on startup + guest provided etc/hardware_errors address.
For once, it assumes error_source_to_index[] matches order in which HEST error sources were described, which is fragile.
2nd: migration-wive it's disaster, since old/new HEST/hardware_errors tables in RAM migrated from older version might not match above assumptions of target QEMU.
I see 2 ways to rectify it:
1st: preferred/cleanest would be to tell QEMU (viafw_cfg) address of HEST table
in guest RAM, like we do with etc/hardware_errors, see
build_ghes_error_table()
...
tell firmware to writehardware_errorsGPA into
and then fetch from HEST table in RAM, the guest patched error/ack addresses for givensource_id
Quoted 7 lines
code-wise: relatively simple once one wraps their own head over
how this whole APEI thing works in QEMU
workflow is described indocs/specs/acpi_hest_ghes.rstlook to me as sufficient to grasp it.
(but my view is very biased given my prior knowledge,
aka: docs/comments/examples wrt acpi patching are good enough)
(if it's not clear how to do it, ask me for pointers)
That sounds a better approach, however...
Quoted 20 lines
2nd: sort of hack based on
build_ghes_v2()Error Status Address/Read Ack Register
patching instructions
bios_linker_loader_add_pointer(linker,ACPI_BUILD_TABLE_FILE,
address_offset+GAS_ADDR_OFFSET,sizeof(uint64_t),ACPI_GHES_ERRORS_FW_CFG_FILE,source_id*sizeof(uint64_t));
^^^^^^^^^^^^^^^^^^^^^^^^^
duringbuild_ghes_v2()also store on a side mapping
source_id-> error address offset : read ack addressso when you are injecting error, you'd at least use offsets used at start time, to get rid of risk where injection code diverge from HEST:etc/hardware_errors layout at start time.
However to make migration safe, one would need to add a fat comment not to change order ghest error sources in HEST _and_ a dedicated unit test to make sure we catch it when that happens.
bios_tables_testshould be able to catch the change, but it won't say what's wrong, hence a test case that explicitly checks order and loudly & clear complains when we will break order assumptions.
Quoted 4 lines
downside:
* we are are limiting ways HEST could be composed/reshuffled in future
* consumption of extra CI resources
* and well, it relies on above duct tape holding all pieces together
I ended opting to do approach (2) on this changeset, as the current code is already using bios_linker_loader_add_pointer() for ghes, being deeply relying on the block address/ack and cper calculus.
To avoid troubles on this duct tape, I opted to move all offset math to a single function at ghes.c:
/*
* ID numbers used to fill HEST source ID field
*/
enum AcpiHestSourceId {
ACPI_HEST_SRC_ID_SEA,
ACPI_HEST_SRC_ID_GED,
/* Shall be the last one */
ACPI_HEST_SRC_ID_COUNT
} AcpiHestSourceId;
...
static bool acpi_hest_address_offset(enum AcpiGhesNotifyType notify,
uint64_t *error_block_offset,
uint64_t *ack_offset,
uint64_t *cper_offset,
enum AcpiHestSourceId *source_id)
{
enum AcpiHestSourceId source;
uint64_t offset;
switch (notify) {
case ACPI_GHES_NOTIFY_SEA: /* Only on ARMv8 */
source = ACPI_HEST_SRC_ID_SEA;
break;
case ACPI_GHES_NOTIFY_GPIO:
source = ACPI_HEST_SRC_ID_GED;
break;
default:
return true;
}
if (source_id) {
*source_id = source;
}
/*
* Please see docs/specs/acpi_hest_ghes.rst for the memory layout.
* In summary, memory starts with error addresses, then acks and
* finally CPER blocks.
*/
offset = source * sizeof(uint64_t);
if (error_block_offset) {
*error_block_offset = offset;
}
if (ack_offset) {
*ack_offset = offset + ACPI_HEST_SRC_ID_COUNT * sizeof(uint64_t);
}
if (cper_offset) {
*cper_offset = 2 * ACPI_HEST_SRC_ID_COUNT * sizeof(uint64_t) +
source * ACPI_GHES_MAX_RAW_DATA_LENGTH;
}
return false;
}I also removed the anonymous enum with SEA/GPIO source IDs, using only the ACPI notify type as arguments at the function calls.
As there's now a single point where the offsets from docs/specs/acpi_hest_ghes.rst are enforced, this should be error prone.
The code could later be changed to use approach (2), on a separate cleanup.
Thanks,
Mauro
Re: [PATCH v5 6/7] acpi/ghes: add support for generic error injection via QAPI
Quoted 61 lines · On Thu, 8 Aug 2024 14:11:14 +0200 Mauro Carvalho Chehab…
Em Tue, 6 Aug 2024 16:31:13 +0200
Igor Mammedov <[email protected]> escreveu:Quoted 28 lines
hw/acpi/ghes.c int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address) · line 513
Quoted 8 lines
hw/acpi/ghes.c +8
-0+/* Could also be read back from the error_block_address register */ + *error_block_addr = base + +ACPI_GHES_ERROR_SOURCE_COUNT *sizeof (uint64_t ) + +ACPI_GHES_ERROR_SOURCE_COUNT *sizeof (uint64_t ) + + error_source_to_index[notify] *ACPI_GHES_MAX_RAW_DATA_LENGTH ; + +return true; +}I don't like all this pointer math, which is basically a reverse engineered QEMU actions on startup + guest provided etc/hardware_errors address.
For once, it assumes error_source_to_index[] matches order in which HEST error sources were described, which is fragile.
2nd: migration-wive it's disaster, since old/new HEST/hardware_errors tables in RAM migrated from older version might not match above assumptions of target QEMU.
I see 2 ways to rectify it:
1st: preferred/cleanest would be to tell QEMU (viafw_cfg) address of HEST table
in guest RAM, like we do with etc/hardware_errors, see
build_ghes_error_table()
...
tell firmware to writehardware_errorsGPA into
and then fetch from HEST table in RAM, the guest patched error/ack addresses for givensource_idQuoted 7 lines
code-wise: relatively simple once one wraps their own head over
how this whole APEI thing works in QEMU
workflow is described indocs/specs/acpi_hest_ghes.rstlook to me as sufficient to grasp it.
(but my view is very biased given my prior knowledge,
aka: docs/comments/examples wrt acpi patching are good enough)
(if it's not clear how to do it, ask me for pointers)That sounds a better approach, however...
Quoted 20 lines
2nd: sort of hack based on
build_ghes_v2()Error Status Address/Read Ack Register
patching instructions
bios_linker_loader_add_pointer(linker,ACPI_BUILD_TABLE_FILE,
address_offset+GAS_ADDR_OFFSET,sizeof(uint64_t),ACPI_GHES_ERRORS_FW_CFG_FILE,source_id*sizeof(uint64_t));
^^^^^^^^^^^^^^^^^^^^^^^^^
duringbuild_ghes_v2()also store on a side mapping
source_id-> error address offset : read ack addressso when you are injecting error, you'd at least use offsets used at start time, to get rid of risk where injection code diverge from HEST:etc/hardware_errors layout at start time.
However to make migration safe, one would need to add a fat comment not to change order ghest error sources in HEST _and_ a dedicated unit test to make sure we catch it when that happens.
bios_tables_testshould be able to catch the change, but it won't say what's wrong, hence a test case that explicitly checks order and loudly & clear complains when we will break order assumptions.
Quoted 8 lines
Quoted 4 lines
downside:
* we are are limiting ways HEST could be composed/reshuffled in future
* consumption of extra CI resources
* and well, it relies on above duct tape holding all pieces togetherI ended opting to do approach (2) on this changeset, as the current code is already using
bios_linker_loader_add_pointer()for ghes, being deeply relying on the block address/ack and cper calculus.
I consider (2) as a fallback in case (1) can't be done with reasonable effort. At this point, (1) looks doable and I'm not convinced that duct tape is necessary and that we badly need to rush in this series.
Hence I'd strongly prefer (1).
See my other reply to Jonathan, setting write pointer is not hard. Parsing HEST doesn't have to be a full tables parser as long as it respects table types/length/revision then we can cheat by using documented offsets from ACPI spec as is, for fields we need to access.
Quoted 75 lines
To avoid troubles on this duct tape, I opted to move all offset math to a single function at
ghes.c:/* * ID numbers used to fill HEST source ID field */ enum AcpiHestSourceId { ACPI_HEST_SRC_ID_SEA, ACPI_HEST_SRC_ID_GED, /* Shall be the last one */ ACPI_HEST_SRC_ID_COUNT } AcpiHestSourceId; ... static bool acpi_hest_address_offset(enum AcpiGhesNotifyType notify, uint64_t *error_block_offset, uint64_t *ack_offset, uint64_t *cper_offset, enum AcpiHestSourceId *source_id) { enum AcpiHestSourceId source; uint64_t offset; switch (notify) { case ACPI_GHES_NOTIFY_SEA: /* Only on ARMv8 */ source = ACPI_HEST_SRC_ID_SEA; break; case ACPI_GHES_NOTIFY_GPIO: source = ACPI_HEST_SRC_ID_GED; break; default: return true; } if (source_id) { *source_id = source; } /* * Please see docs/specs/acpi_hest_ghes.rst for the memory layout. * In summary, memory starts with error addresses, then acks and * finally CPER blocks. */ offset = source * sizeof(uint64_t); if (error_block_offset) { *error_block_offset = offset; } if (ack_offset) { *ack_offset = offset + ACPI_HEST_SRC_ID_COUNT * sizeof(uint64_t); } if (cper_offset) { *cper_offset = 2 * ACPI_HEST_SRC_ID_COUNT * sizeof(uint64_t) + source * ACPI_GHES_MAX_RAW_DATA_LENGTH; } return false; }I also removed the anonymous enum with SEA/GPIO source IDs, using only the ACPI notify type as arguments at the function calls.
As there's now a single point where the offsets from
docs/specs/acpi_hest_ghes.rstare enforced, this should be error prone.The code could later be changed to use approach (2), on a separate cleanup.
Thanks,
Mauro
Re: [PATCH v5 5/7] qapi/ghes-cper: add an interface to do generic CPER error injection
In reply to Markus ArmbrusterEm Thu, 08 Aug 2024 10:50:33 +0200
Markus Armbruster <[email protected]> escreveu:
Quoted 21 lines
Quoted 5 lines · Mauro Carvalho Chehab
MAINTAINERS +0
-0MAINTAINERS F: hw/acpi/ghes.c · line 2084
Quoted 10 lines
MAINTAINERS +7
-0@@ -2075,6 +2075,13 @@ F: hw/acpi/ghes.c F: include/hw/acpi/ghes.h F: docs/specs/acpi_hest_ghes.rst +ACPI/HEST/GHES/ARM processor CPER +R: Mauro Carvalho Chehab <[email protected]> +S: Maintained +F: hw/arm/ghes_cper.c +F: hw/acpi/ghes_cper_stub.c +F: qapi/ghes-cper.json +Here's the reason for creating a new QAPI module instead of adding to existing module acpi.json: different maintainers.
Quoted 2 lines
Hypothetical question: if we didn't care for that, would this go into
qapi/acpi.json?
Independently of maintainers, GHES is part of ACPI APEI HEST, meaning to report hardware errors. Such hardware errors are typically handled by the host OS, so quest doesn't need to be aware of that[1].
So, IMO the best would be to keep APEI/HEST/GHES in a separate file.
[1] still, I can foresee some scenarios were passing some errors to the guest could make sense.
Quoted 3 lines
If yes, then should we call it acpi-ghes-cper.json or acpi-ghes.json instead?
Naming it as acpi-ghes,acpi-hest or acpi-ghes-cper would equally work from my side.
Quoted 26 lines
Quoted 4 lines
MAINTAINERS +0
-0ppc4xx L: [email protected] S: Orphan[...]
Quoted 6 lines
qapi/ghes-cper.json new file +0
-0qapi/ghes-cper.json line 10
Quoted 10 lines
qapi/ghes-cper.json new file +10
-0@@ -0,0 +1,55 @@ +# -*- Mode: Python -*- +# vim: filetype=python + +## +# = GHESv2 CPER Error Injection +# +# These are defined at +# ACPI 6.2: 18.3.2.8 Generic Hardware Error Source version 2 +# (GHESv2 - Type 10) +##Feels a bit terse. These what?
Quoted 3 lines
The reference could be clearer: "defined in the ACPI Specification 6.2, section 18.3.2.8 Generic Hardware Error Source version 2". A link would be nice, if it's stable.
I can add a link, but only newer ACPI versions are hosted in html format (e. g. only versions 6.4 and 6.5 are available as html at uefi.org).
Can I place something like:
Defined since ACPI Specification 6.2,
section 18.3.2.8 Generic Hardware Error Source version 2. See:
e. g. having the link pointing to ACPI 6.4 or 6.5, instead of 6.2?
Quoted 3 lines
# @raw-data: payload of the CPER encoded in base64
Have you considered naming this @payload instead?
Works for me.
Thanks,
Mauro
Re: [PATCH v5 5/7] qapi/ghes-cper: add an interface to do generic CPER error injection
Quoted 37 lines · On Thu, 8 Aug 2024 16:11:41 +0200 Mauro Carvalho Chehab…
Em Thu, 08 Aug 2024 10:50:33 +0200
Markus Armbruster <[email protected]> escreveu:Quoted 21 lines
Quoted 5 lines · Mauro Carvalho Chehab
MAINTAINERS +0
-0MAINTAINERS F: hw/acpi/ghes.c · line 2084
Quoted 10 lines
MAINTAINERS +7
-0@@ -2075,6 +2075,13 @@ F: hw/acpi/ghes.c F: include/hw/acpi/ghes.h F: docs/specs/acpi_hest_ghes.rst +ACPI/HEST/GHES/ARM processor CPER +R: Mauro Carvalho Chehab <[email protected]> +S: Maintained +F: hw/arm/ghes_cper.c +F: hw/acpi/ghes_cper_stub.c +F: qapi/ghes-cper.json +Here's the reason for creating a new QAPI module instead of adding to existing module acpi.json: different maintainers.
Quoted 2 lines
Hypothetical question: if we didn't care for that, would this go into
qapi/acpi.json?Independently of maintainers, GHES is part of ACPI APEI HEST, meaning to report hardware errors. Such hardware errors are typically handled by the host OS, so quest doesn't need to be aware of that[1].
So, IMO the best would be to keep APEI/HEST/GHES in a separate file.
[1] still, I can foresee some scenarios were passing some errors to the guest could make sense.
Quoted 1 line
Quoted 5 lines
Quoted 2 lines
If yes, then should we call it acpi-ghes-cper.json or acpi-ghes.json instead?
Naming it as acpi-ghes,acpi-hest or acpi-ghes-cper would equally work from my side.
if we going to keep it generic, acpi-hest would do
Quoted 27 lines
Quoted 27 lines
Quoted 5 lines
MAINTAINERS +0
-0ppc4xx L: [email protected] S: Orphan[...]
Quoted 6 lines
qapi/ghes-cper.json new file +0
-0qapi/ghes-cper.json line 10
Quoted 10 lines
qapi/ghes-cper.json new file +10
-0@@ -0,0 +1,55 @@ +# -*- Mode: Python -*- +# vim: filetype=python + +## +# = GHESv2 CPER Error Injection +# +# These are defined at +# ACPI 6.2: 18.3.2.8 Generic Hardware Error Source version 2 +# (GHESv2 - Type 10) +##Feels a bit terse. These what?
Quoted 6 lines
Quoted 3 lines
The reference could be clearer: "defined in the ACPI Specification 6.2, section 18.3.2.8 Generic Hardware Error Source version 2". A link would be nice, if it's stable.
I can add a link, but only newer ACPI versions are hosted in html format (e. g. only versions 6.4 and 6.5 are available as html at uefi.org).
some years earlier it could be said 'stable link' about acpi spec hosted elsewhere. Not the case anymore after umbrella change.
spec name, rev, chapter worked fine for acpi code (it's easy to find wherever spec is hosted). Probably the same would work for QAPI, I'm not QAPI maintainer though,
so preffered approach here is absolutely up to you.
Quoted 19 lines
Can I place something like:
Defined since ACPI Specification 6.2,
section 18.3.2.8 Generic Hardware Error Source version 2. See:e. g. having the link pointing to ACPI 6.4 or 6.5, instead of 6.2?
Quoted 3 lines
# @raw-data: payload of the CPER encoded in base64
Have you considered naming this @payload instead?
Works for me.
Thanks,
Mauro
Re: [PATCH v5 5/7] qapi/ghes-cper: add an interface to do generic CPER error injection
Quoted 40 lines · Igor Mammedov
Quoted 37 lines · On Thu, 8 Aug 2024 16:11:41 +0200 Mauro Carvalho Chehab…
Em Thu, 08 Aug 2024 10:50:33 +0200
Markus Armbruster <[email protected]> escreveu:Quoted 21 lines
Quoted 5 lines · Mauro Carvalho Chehab
MAINTAINERS +0
-0MAINTAINERS F: hw/acpi/ghes.c · line 2084
Quoted 10 lines
MAINTAINERS +7
-0@@ -2075,6 +2075,13 @@ F: hw/acpi/ghes.c F: include/hw/acpi/ghes.h F: docs/specs/acpi_hest_ghes.rst +ACPI/HEST/GHES/ARM processor CPER +R: Mauro Carvalho Chehab <[email protected]> +S: Maintained +F: hw/arm/ghes_cper.c +F: hw/acpi/ghes_cper_stub.c +F: qapi/ghes-cper.json +Here's the reason for creating a new QAPI module instead of adding to existing module acpi.json: different maintainers.
Quoted 2 lines
Hypothetical question: if we didn't care for that, would this go into
qapi/acpi.json?Independently of maintainers, GHES is part of ACPI APEI HEST, meaning to report hardware errors. Such hardware errors are typically handled by the host OS, so quest doesn't need to be aware of that[1].
So, IMO the best would be to keep APEI/HEST/GHES in a separate file.
[1] still, I can foresee some scenarios were passing some errors to the guest could make sense.
Quoted 1 line
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
If yes, then should we call it acpi-ghes-cper.json or acpi-ghes.json instead?
Naming it as acpi-ghes,acpi-hest or acpi-ghes-cper would equally work from my side.
if we going to keep it generic, acpi-hest would do
Works for me.
Quoted 32 lines
Quoted 25 lines
Quoted 25 lines
Quoted 3 lines
MAINTAINERS +0
-0ppc4xx L: [email protected] S: Orphan[...]
Quoted 6 lines
qapi/ghes-cper.json new file +0
-0qapi/ghes-cper.json line 10
Quoted 10 lines
qapi/ghes-cper.json new file +10
-0@@ -0,0 +1,55 @@ +# -*- Mode: Python -*- +# vim: filetype=python + +## +# = GHESv2 CPER Error Injection +# +# These are defined at +# ACPI 6.2: 18.3.2.8 Generic Hardware Error Source version 2 +# (GHESv2 - Type 10) +##Feels a bit terse. These what?
Quoted 6 lines
Quoted 3 lines
The reference could be clearer: "defined in the ACPI Specification 6.2, section 18.3.2.8 Generic Hardware Error Source version 2". A link would be nice, if it's stable.
I can add a link, but only newer ACPI versions are hosted in html format (e. g. only versions 6.4 and 6.5 are available as html at uefi.org).
Quoted 6 lines
some years earlier it could be said 'stable link' about acpi spec hosted elsewhere. Not the case anymore after umbrella change.
spec name, rev, chapter worked fine for acpi code (it's easy to find wherever spec is hosted). Probably the same would work for QAPI, I'm not QAPI maintainer though,
so preffered approach here is absolutely up to you.
A link is strictly optional. Stable links are nice, stale links are annoying. Mauro, you decide :)
Thanks!
[...]
Re: [PATCH v5 6/7] acpi/ghes: add support for generic error injection via QAPI
In reply to Igor MammedovEm Thu, 8 Aug 2024 10:11:07 +0200
Igor Mammedov <[email protected]> escreveu:
Quoted 183 lines
Quoted 168 lines · On Wed, 7 Aug 2024 15:25:47 +0100 Jonathan Cameron…
Quoted 157 lines · On Tue, 6 Aug 2024 16:31:13 +0200 Igor Mammedov <[email protected]> wrote:
Quoted 24 lines · On Fri, 2 Aug 2024 23:44:01 +0200 Mauro Carvalho Chehab…
Provide a generic interface for error injection via GHESv2.
This patch is co-authored:
- original ghes logic to inject a simple ARM record by Shiju Jose;
- generic logic to handle block addresses by Jonathan Cameron;
- generic GHESv2 error inject by Mauro Carvalho Chehab;Co-authored-by Jonathan Cameron <[email protected]>Co-authored-by Shiju Jose <[email protected]>Co-authored-by Mauro Carvalho Chehab <[email protected]>Cc Jonathan Cameron <[email protected]>Cc Shiju Jose <[email protected]>Signed-off-by Mauro Carvalho Chehab <[email protected]>--- hw/acpi/ghes.c | 159 ++++++++++++++++++++++++++++++++++++++--- hw/acpi/ghes_cper.c | 2 +- include/hw/acpi/ghes.h | 3 + 3 files changed, 152 insertions(+), 12 deletions(-)hw/acpi/ghes.c +0
-0hw/acpi/ghes.c void acpi_ghes_add_fw_cfg(AcpiGhesState *ags, FWCfgState *s, · line 398
Quoted 4 lines
hw/acpi/ghes.c +1
-0@@ -395,23 +395,22 @@ void acpi_ghes_add_fw_cfg(AcpiGhesState *ags, FWCfgState *s, ags->present = true; } +static uint64_t ghes_get_state_start_address (void )
ghes_get_hardware_errors_address()might better reflect what address it will returnQuoted 18 lines
hw/acpi/ghes.c +9
-4+{ +AcpiGedState *acpi_ged_state = +ACPI_GED (object_resolve_path_type ("" ,TYPE_ACPI_GED ,NULL )); +AcpiGhesState *ags = &acpi_ged_state->ghes_state; + +return le64_to_cpu (ags->ghes_addr_le); +} +int acpi_ghes_record_errors (uint8_t source_id,uint64_t physical_address) {uint64_t error_block_addr, read_ack_register_addr, read_ack_register =0 ; -uint64_t start_addr; +uint64_t start_addr =ghes_get_state_start_address ();bool ret =-1 ; -AcpiGedState *acpi_ged_state; -AcpiGhesState *ags; -assert (source_id <ACPI_HEST_SRC_ID_RESERVED );hw/acpi/ghes.c void acpi_ghes_add_fw_cfg(AcpiGhesState *ags, FWCfgState *s, · line 415
Quoted 10 lines
hw/acpi/ghes.c +0
-7- acpi_ged_state =ACPI_GED (object_resolve_path_type ("" ,TYPE_ACPI_GED , -NULL )); -g_assert (acpi_ged_state); - ags = &acpi_ged_state->ghes_state; - - start_addr =le64_to_cpu (ags->ghes_addr_le); -if (physical_address) { start_addr += source_id *sizeof (uint64_t );above should be a separate patch
Quoted 26 lines
hw/acpi/ghes.c +21
-0@@ -448,9 +447,147 @@ int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address)return ret; } +/* +* Error register block data layout +* +* | +---------------------+ ges.ghes_addr_le +* | |error_block_address0 | +* | +---------------------+ +* | |error_block_address1 | +* | +---------------------+ --+-- +* | | ............. | GHES_ADDRESS_SIZE +* | +---------------------+ --+-- +* | |error_block_addressN | +* | +---------------------+ +* | | read_ack0 | +* | +---------------------+ --+-- +* | | read_ack1 | GHES_ADDRESS_SIZE +* | +---------------------+ --+-- +* | | ............. | +* | +---------------------+ +* | | read_ackN | +* | +---------------------+ --+-- +* | | CPER | | hw/acpi/ghes.c int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address) · line 480
Quoted 10 lines
hw/acpi/ghes.c +10
-0+* | | .... | GHES_MAX_RAW_DATA_LENGT +* | | CPER | | +* | +---------------------+ --+-- +* | | .......... | +* | +---------------------+ +* | | CPER | +* | | .... | +* | | CPER | +* | +---------------------+ +*/ no need to duplicate
docs/specs/acpi_hest_ghes.rst,
I'd just reffer to it and maybe add short comment as to why it's mentioned.Quoted 22 lines
hw/acpi/ghes.c +22
-0+/* Map from uint32_t notify to entry offset in GHES */ +static const uint8_t error_source_to_index[] = {0xff ,0xff ,0xff ,0xff , +0xff ,0xff ,0xff ,1 ,0 }; + +static bool ghes_get_addr (uint32_t notify,uint64_t *error_block_addr, +uint64_t *read_ack_addr) +{ +uint64_t base; + +if (notify >=ACPI_GHES_NOTIFY_RESERVED ) { +return false; + } + +/* Find and check the source id for this new CPER */ +if (error_source_to_index[notify] ==0xff ) { +return false; + } + + base =ghes_get_state_start_address (); + + *read_ack_addr = base + + ACPI_GHES_ERROR_SOURCE_COUNT * sizeof(uint64_t) +hw/acpi/ghes.c int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address) · line 513
Quoted 10 lines
hw/acpi/ghes.c +10
-0+ error_source_to_index[notify] *sizeof (uint64_t ); + +/* Could also be read back from the error_block_address register */ + *error_block_addr = base + +ACPI_GHES_ERROR_SOURCE_COUNT *sizeof (uint64_t ) + +ACPI_GHES_ERROR_SOURCE_COUNT *sizeof (uint64_t ) + + error_source_to_index[notify] *ACPI_GHES_MAX_RAW_DATA_LENGTH ; + +return true; +}I don't like all this pointer math, which is basically a reverse engineered QEMU actions on startup + guest provided etc/hardware_errors address.
For once, it assumes error_source_to_index[] matches order in which HEST error sources were described, which is fragile.
2nd: migration-wive it's disaster, since old/new HEST/hardware_errors tables in RAM migrated from older version might not match above assumptions of target QEMU.
I see 2 ways to rectify it:
1st: preferred/cleanest would be to tell QEMU (viafw_cfg) address of HEST table
in guest RAM, like we do with etc/hardware_errors, see
build_ghes_error_table()
...
tell firmware to writehardware_errorsGPA into
and then fetch from HEST table in RAM, the guest patched error/ack addresses for givensource_idQuoted 7 lines
code-wise: relatively simple once one wraps their own head over
how this whole APEI thing works in QEMU
workflow is described indocs/specs/acpi_hest_ghes.rstlook to me as sufficient to grasp it.
(but my view is very biased given my prior knowledge,
aka: docs/comments/examples wrt acpi patching are good enough)
(if it's not clear how to do it, ask me for pointers)Quoted 4 lines
Hi Igor, I think I follow what you mean but maybe this question will reveal otherwise. HEST is currently in
ACPI_BUILD_TABLE_FILE.
Would you suggest splitting it to it's own file, or usingtable_offsetsto get the offset inACPI_BUILD_TABLE_FILEGPA?yep, offset taken right before HEST is to be created
doc comment forbios_linker_loader_write_pointer()explains how it workswe need something like:
bios_linker_loader_write_pointer(linker, ACPI_HEST_TABLE_ADDR_FW_CFG_FILE, 0, sizeof(uint64_t), ACPI_BUILD_TABLE_FILE, hest_offset_within_ACPI_BUILD_TABLE_FILE);
Quoted 6 lines
to register new file see:
a08a64627ACPI: Record the Generic Error Status Block address and to avoid copy past error maybe
136fc6aa2ACPI: Avoid infinite recursion when dump-vmstat
for this needs to be limited to new machine types and keep
old ones without this new feature. (I'd usehw_compat_machinery for that)
Not sure if I got it. The code, after this patch from my v6:
https://lore.kernel.org/qemu-devel/5710c364d7ef6cdab6b2f1e127ef191bdf84e8c2.1723119423.git.mchehab+huawei@kernel.org/T/#u
Already stores two of the three address offsets via bios_linker_loader_add_pointer(), e. g. it is similar to the code below (I simplified the code to make the example clearer):
<snip>
/* From hw/arm/virt-acpi-build.c */
static
void virt_acpi_build(VirtMachineState *vms, AcpiBuildTables *tables)
{
...
if (vms->ras) {
build_ghes_error_table(tables->hardware_errors, tables->linker);
acpi_add_table(table_offsets, tables_blob);
/* internally, call build_ghes_v2() for SEA and GED notification sources */
acpi_build_hest(tables_blob, tables->linker, vms->oem_id,
vms->oem_table_id);
}
...
}/* From hw/acpi/ghes.c */
static void build_ghes_v2(GArray *table_data,
enum AcpiGhesNotifyType notify, BIOSLinker *linker)
{
uint64_t address_offset, ack_offset, block_addr_offset, cper_offset;
enum AcpiHestSourceId source_id;
/*
* Get offsets for either SEA or GED notification - easy to extend
* to all mechanisms like MCE and SCI to better support x86
*/
assert(!acpi_hest_address_offset(notify, &block_addr_offset, &ack_offset,
&cper_offset, &source_id));
bios_linker_loader_add_pointer(linker, ACPI_BUILD_TABLE_FILE,
address_offset + GAS_ADDR_OFFSET,
sizeof(uint64_t),
ACPI_GHES_ERRORS_FW_CFG_FILE,
block_addr_offset);
bios_linker_loader_add_pointer(linker, ACPI_BUILD_TABLE_FILE,
address_offset + GAS_ADDR_OFFSET,
sizeof(uint64_t),
ACPI_GHES_ERRORS_FW_CFG_FILE,
ack_offset);
/* Current code ignores &cper_offset when creating HEST */
}void ghes_record_cper_errors(AcpiGhesCper *cper, Error **errp,
enum AcpiGhesNotifyType notify)
{
uint64_t cper_addr, read_ack_start_addr;
assert(!ghes_get_hardware_errors_address(notify, NULL, &read_ack_start_addr,
&cper_addr, NULL));
/*
* Use cpu_physical_memory_read/write() to
* - read/store at read_ack_start_addr
* - Write cper block GArray at cper_addr
*/
}
</snip>
We may also store cper_offset there via bios_linker_loader_add_pointer() and/or use bios_linker_loader_write_pointer(), but I can't see how the data stored there can be retrieved, nor any advantage of using it instead of the current code, as, in the end, we'll have 3 addresses that will be used:
- an address where a pointer to CPER record will be stored;
- an address where the ack will be stored;
- an address where the actual CPER record will be stored.
And those are calculated on a single function and are all stored at the ACPI table files.
What am I missing?
Thanks,
Mauro
Re: [PATCH v5 7/7] scripts/ghes_inject: add a script to generate GHES error inject
In reply to Mauro Carvalho ChehabQuoted 40 lines · Mauro Carvalho Chehab
Using the QMP GHESv2 API requires preparing a raw data array containing a CPER record.
Add a helper script with subcommands to prepare such data.
Currently, only ARM Processor error CPER record is supported.
Signed-off-by Mauro Carvalho Chehab <[email protected]>--- MAINTAINERS | 3 + scripts/arm_processor_error.py | 352 +++++++++++++++++++++++++++++++++ scripts/ghes_inject.py | 59 ++++++ scripts/qmp_helper.py | 249 +++++++++++++++++++++++ 4 files changed, 663 insertions(+) create mode 100644 scripts/arm_processor_error.py create mode 100755 scripts/ghes_inject.py create mode 100644 scripts/qmp_helper.pyMAINTAINERS +3
-0@@ -2081,6 +2081,9 @@ S: Maintained F: hw/arm/ghes_cper.c F: hw/acpi/ghes_cper_stub.c F: qapi/ghes-cper.json +F: scripts/ghes_inject.py +F: scripts/arm_processor_error.py +F: scripts/qmp_helper.py ppc4xx L: [email protected]scripts/arm_processor_error.py new file +0
-0
scripts/arm_processor_error.py line 3
Quoted 3 lines
scripts/arm_processor_error.py new file +3
-0@@ -0,0 +1,352 @@ +#!/usr/bin/env python3 +# +# pylint: disable=C0301, C0114, R0912, R0913, R0914, R0915, W0511
Out of curiosity, what tools are you using to delint your files and how are you invoking them?
I don't really maintain any strict regime for python files under qemu.git/scripts (yet), so I am mostly curious as to what regimes others are using currently. I don't see most QEMU contributors checking in pylint ignores etc directly into the files, so it caught my eye.
~js
Quoted 686 lines
scripts/arm_processor_error.py new file +73
-0+# SPDX-License-Identifier: GPL-2.0 +# +# Copyright (C) 2024 Mauro Carvalho Chehab <[email protected]> + +# TODO: current implementation has dummy defaults. +# +# For a better implementation, a QMP addition/call is needed to +# retrieve some data for ARM Processor Error injection: +# +# - machine emulation architecture, as ARM current default is +# for AArch64; +# - ARM registers: power_state, midr, mpidr. + +import argparse +import json + +from qmp_helper import (qmp_command, get_choice, get_mult_array, + get_mult_choices, get_mult_int, bit, + data_add, to_guid) + +# Arm processor EINJ logic +# +ACPI_GHES_ARM_CPER_LENGTH = 40 +ACPI_GHES_ARM_CPER_PEI_LENGTH = 32 + +# TODO: query it from emulation. Current default valid only for Aarch64 +CONTEXT_AARCH64_EL1 = 5 + +class ArmProcessorEinj: + """ + Implements ARM Processor Error injection via GHES + """ + + def __init__(self): + """Initialize the error injection class""" + + # Valid choice values + self.arm_valid_bits = { + "mpidr": bit(0), + "affinity": bit(1), + "running": bit(2), + "vendor": bit(3), + } + + self.pei_flags = { + "first": bit(0), + "last": bit(1), + "propagated": bit(2), + "overflow": bit(3), + } + + self.pei_error_types = { + "cache": bit(1), + "tlb": bit(2), + "bus": bit(3), + "micro-arch": bit(4), + } + + self.pei_valid_bits = { + "multiple-error": bit(0), + "flags": bit(1), + "error-info": bit(2), + "virt-addr": bit(3), + "phy-addr": bit(4), + } + + self.data = bytearray() + + def create_subparser(self, subparsers): + """Add a subparser to handle for the error fields""" + + parser = subparsers.add_parser("arm", + help="Generate an ARM processorCPER")
scripts/arm_processor_error.py new file +11
-0+ + arm_valid_bits = ",".join(self.arm_valid_bits.keys()) + flags = ",".join(self.pei_flags.keys()) + error_types = ",".join(self.pei_error_types.keys()) + pei_valid_bits = ",".join(self.arm_valid_bits.keys()) + + # UEFI N.16 ARM Validation bits + g_arm = parser.add_argument_group("ARM processor") + g_arm.add_argument("--arm", "--arm-valid", + help=f"ARM valid bits: {arm_valid_bits}") + g_arm.add_argument("-a", "--affinity", "--level","--affinity-level",
scripts/arm_processor_error.py new file +2
-0+ type=lambda x: int(x, 0), + help="Affinity level (when multiple levelsapply)")
scripts/arm_processor_error.py new file +8
-0+ g_arm.add_argument("-l", "--mpidr", type=lambda x: int(x, 0), + help="Multiprocessor Affinity Register") + g_arm.add_argument("-i", "--midr", type=lambda x: int(x, 0), + help="Main ID Register") + g_arm.add_argument("-r", "--running", + action=argparse.BooleanOptionalAction, + default=None, + help="Indicates if the processor is running ornot")
scripts/arm_processor_error.py new file +3
-0+ g_arm.add_argument("--psci", "--psci-state", + type=lambda x: int(x, 0), + help="Power State Coordination Interface -PSCI state")
scripts/arm_processor_error.py new file +5
-0+ + # TODO: Add vendor-specific support + + # UEFI N.17 bitmaps (type and flags) + g_pei = parser.add_argument_group("ARM Processor Error Info(PEI)")
scripts/arm_processor_error.py new file +5
-0+ g_pei.add_argument("-t", "--type", nargs="+", + help=f"one or more error types: {error_types}") + g_pei.add_argument("-f", "--flags", nargs="*", + help=f"zero or more error flags: {flags}") + g_pei.add_argument("-V", "--pei-valid", "--error-valid",nargs="*",
+ help=f"zero or more PEI valid bits:
{pei_valid_bits}")scripts/arm_processor_error.py new file +4
-0+ + # UEFI N.17 Integer values + g_pei.add_argument("-m", "--multiple-error", nargs="+", + help="Number of errors: 0: Single error, 1:Multiple errors, 2-65535: Error count if known")
scripts/arm_processor_error.py new file +2
-0+ g_pei.add_argument("-e", "--error-info", nargs="+", + help="Error information (UEFI 2.10 tables N.18 toN.20)")
scripts/arm_processor_error.py new file +9
-0+ g_pei.add_argument("-p", "--physical-address", nargs="+", + help="Physical address") + g_pei.add_argument("-v", "--virtual-address", nargs="+", + help="Virtual address") + + # UEFI N.21 Context + g_ctx = parser.add_argument_group("Processor Context") + g_ctx.add_argument("--ctx-type", "--context-type", nargs="*", + help="Type of the context (0=ARM32 GPR, 5=ARM64EL1, other values supported)")
scripts/arm_processor_error.py new file +226
-0+ g_ctx.add_argument("--ctx-size", "--context-size", nargs="*", + help="Minimal size of the context") + g_ctx.add_argument("--ctx-array", "--context-array", nargs="*", + help="Comma-separated arrays for each context") + + # Vendor-specific data + g_vendor = parser.add_argument_group("Vendor-specific data") + g_vendor.add_argument("--vendor", "--vendor-specific", nargs="+", + help="Vendor-specific byte arrays of data") + + def parse_args(self, args): + """Parse subcommand arguments""" + + cper = {} + pei = {} + ctx = {} + vendor = {} + + arg = vars(args) + + # Handle global parameters + if args.arm: + arm_valid_init = False + cper["valid"] = get_choice(name="valid", + value=args.arm, + choices=self.arm_valid_bits, + suffixes=["-error", "-err"]) + else: + cper["valid"] = 0 + arm_valid_init = True + + if "running" in arg: + if args.running: + cper["running-state"] = bit(0) + else: + cper["running-state"] = 0 + else: + cper["running-state"] = 0 + + if arm_valid_init: + if args.affinity: + cper["valid"] |= self.arm_valid_bits["affinity"] + + if args.mpidr: + cper["valid"] |= self.arm_valid_bits["mpidr"] + + if "running-state" in cper: + cper["valid"] |= self.arm_valid_bits["running"] + + if args.psci: + cper["valid"] |= self.arm_valid_bits["running"] + + # Handle PEI + if not args.type: + args.type = ["cache-error"] + + get_mult_choices( + pei, + name="valid", + values=args.pei_valid, + choices=self.pei_valid_bits, + suffixes=["-valid", "-info", "--information", "--addr"], + ) + get_mult_choices( + pei, + name="type", + values=args.type, + choices=self.pei_error_types, + suffixes=["-error", "-err"], + ) + get_mult_choices( + pei, + name="flags", + values=args.flags, + choices=self.pei_flags, + suffixes=["-error", "-cap"], + ) + get_mult_int(pei, "error-info", args.error_info) + get_mult_int(pei, "multiple-error", args.multiple_error) + get_mult_int(pei, "phy-addr", args.physical_address) + get_mult_int(pei, "virt-addr", args.virtual_address) + + # Handle context + get_mult_int(ctx, "type", args.ctx_type, allow_zero=True) + get_mult_int(ctx, "minimal-size", args.ctx_size, allow_zero=True) + get_mult_array(ctx, "register", args.ctx_array, allow_zero=True) + + get_mult_array(vendor, "bytes", args.vendor, max_val=255) + + # Store PEI + pei_data = bytearray() + default_flags = self.pei_flags["first"] + default_flags |= self.pei_flags["last"] + + error_info_num = 0 + + for i, p in pei.items(): # pylint: disable=W0612 + error_info_num += 1 + + # UEFI 2.10 doesn't define how to encode error information + # when multiple types are raised. So, provide a default only + # if a single type is there + if "error-info" not in p: + if p["type"] == bit(1): + p["error-info"] = 0x0091000F + if p["type"] == bit(2): + p["error-info"] = 0x0054007F + if p["type"] == bit(3): + p["error-info"] = 0x80D6460FFF + if p["type"] == bit(4): + p["error-info"] = 0x78DA03FF + + if "valid" not in p: + p["valid"] = 0 + if "multiple-error" in p: + p["valid"] |= self.pei_valid_bits["multiple-error"] + + if "flags" in p: + p["valid"] |= self.pei_valid_bits["flags"] + + if "error-info" in p: + p["valid"] |= self.pei_valid_bits["error-info"] + + if "phy-addr" in p: + p["valid"] |= self.pei_valid_bits["phy-addr"] + + if "virt-addr" in p: + p["valid"] |= self.pei_valid_bits["virt-addr"] + + # Version + data_add(pei_data, 0, 1) + + data_add(pei_data, ACPI_GHES_ARM_CPER_PEI_LENGTH, 1) + + data_add(pei_data, p["valid"], 2) + data_add(pei_data, p["type"], 1) + data_add(pei_data, p.get("multiple-error", 1), 2) + data_add(pei_data, p.get("flags", default_flags), 1) + data_add(pei_data, p.get("error-info", 0), 8) + data_add(pei_data, p.get("virt-addr", 0xDEADBEEF), 8) + data_add(pei_data, p.get("phy-addr", 0xABBA0BAD), 8) + + # Store Context + ctx_data = bytearray() + context_info_num = 0 + + if ctx: + for k in sorted(ctx.keys()): + context_info_num += 1 + + if "type" not in ctx: + ctx[k]["type"] = CONTEXT_AARCH64_EL1 + + if "register" not in ctx: + ctx[k]["register"] = [] + + reg_size = len(ctx[k]["register"]) + size = 0 + + if "minimal-size" in ctx: + size = ctx[k]["minimal-size"] + + size = max(size, reg_size) + + size = (size + 1) % 0xFFFE + + # Version + data_add(ctx_data, 0, 2) + + data_add(ctx_data, ctx[k]["type"], 2) + + data_add(ctx_data, 8 * size, 4) + + for r in ctx[k]["register"]: + data_add(ctx_data, r, 8) + + for i in range(reg_size, size): # pylint: disable=W0612 + data_add(ctx_data, 0, 8) + + # Vendor-specific bytes are not grouped + vendor_data = bytearray() + if vendor: + for k in sorted(vendor.keys()): + for b in vendor[k]["bytes"]: + data_add(vendor_data, b, 1) + + # Encode ARM Processor Error + data = bytearray() + + data_add(data, cper["valid"], 4) + + data_add(data, error_info_num, 2) + data_add(data, context_info_num, 2) + + # Calculate the length of the CPER data + cper_length = ACPI_GHES_ARM_CPER_LENGTH + cper_length += len(pei_data) + cper_length += len(vendor_data) + cper_length += len(ctx_data) + data_add(data, cper_length, 4) + + data_add(data, arg.get("affinity-level", 0), 1) + + # Reserved + data_add(data, 0, 3) + + data_add(data, arg.get("mpidr-el1", 0), 8) + data_add(data, arg.get("midr-el1", 0), 8) + data_add(data, cper["running-state"], 4) + data_add(data, arg.get("psci-state", 0), 4) + + # Add PEI + data.extend(pei_data) + data.extend(ctx_data) + data.extend(vendor_data) + + self.data = data + + def run(self, host, port): + """Execute QMP commands""" + + guid = to_guid(0xE19E3D16, 0xBC11, 0x11E4, + [0x9C, 0xAA, 0xC2, 0x05, + 0x1D, 0x5D, 0x46, 0xB0]) + + qmp_command(host, port, guid, self.data)scripts/ghes_inject.py new file +35
-0@@ -0,0 +1,59 @@ +#!/usr/bin/env python3 +# +# pylint: disable=C0301, C0114 +# SPDX-License-Identifier: GPL-2.0 +# +# Copyright (C) 2024 Mauro Carvalho Chehab <[email protected]> + +import argparse + +from arm_processor_error import ArmProcessorEinj + +EINJ_DESCRIPTION = """ +Handle ACPI GHESv2 error injection logic QEMU QMP interface.\n + +It allows using UEFI BIOS EINJ features to generate GHES records. + +It helps testing Linux CPER and GHES drivers and to test rasdaemon +error handling logic. + +Currently, it support ARM processor error injection for ARM processor +events, being compatible with UEFI 2.9A Errata. + +This small utility works together with those QEMU additions: +- https://gitlab.com/mchehab_kernel/qemu/-/tree/arm-error-inject-v2 +""" + +def main(): + """Main program""" + + # Main parser - handle generic args like QEMU QMP TCP socket options + parser = argparse.ArgumentParser(prog="einj.py", + formatter_class=argparse.RawDescriptionHelpFormatter, + usage="%(prog)s [options]", + description=EINJ_DESCRIPTION, + epilog="If a field is not defined, adefault value will be applied by QEMU.")
scripts/ghes_inject.py new file +24
-0+ + g_options = parser.add_argument_group("QEMU QMP socket options") + g_options.add_argument("-H", "--host", default="localhost", type=str, + help="host name") + g_options.add_argument("-P", "--port", default=4445, type=int, + help="TCP port number") + + arm_einj = ArmProcessorEinj() + + # Call subparsers + subparsers = parser.add_subparsers(dest='command') + + arm_einj.create_subparser(subparsers) + + args = parser.parse_args() + + # Handle subparser commands + if args.command == "arm": + arm_einj.parse_args(args) + arm_einj.run(args.host, args.port) + + +if __name__ == "__main__": + main()scripts/qmp_helper.py new file +249
-1@@ -0,0 +1,249 @@ +#!/usr/bin/env python3 +# +# pylint: disable=C0301, C0114, R0912, R0913, R0915, W0511 +# SPDX-License-Identifier: GPL-2.0 +# +# Copyright (C) 2024 Mauro Carvalho Chehab <[email protected]> + +import json +import socket +import sys + +from base64 import b64encode + +# +# Socket QMP send command +# +def qmp_command(host, port, guid, data): + """Send commands to QEMU though QMP TCP socket""" + + # Fill the commands to be sent + commands = [] + + # Needed to negotiate QMP and for QEMU to accept the command + commands.append('{ "execute": "qmp_capabilities" } ') + + base64_data = b64encode(bytes(data)).decode('ascii') + + cmd_arg = { + 'cper': { + 'notification-type': guid, + "raw-data": base64_data + } + } + + command = '{ "execute": "ghes-cper", ' + command += '"arguments": ' + json.dumps(cmd_arg) + " }" + + commands.append(command) + + s = socket.socket(socket.AF_INET, socket.SOCK_STREAM) + try: + s.connect((host, port)) + except ConnectionRefusedError: + sys.exit(f"Can't connect to QMP host {host}:{port}") + + data = s.recv(1024) + try: + obj = json.loads(data.decode("utf-8")) + except json.JSONDecodeError as e: + print(f"Invalid QMP answer: {e}") + s.close() + return + + if "QMP" not in obj: + print(f"Invalid QMP answer: {data.decode("utf-8")}") + s.close() + return + + for i, command in enumerate(commands): + s.sendall(command.encode("utf-8")) + data = s.recv(1024) + try: + obj = json.loads(data.decode("utf-8")) + except json.JSONDecodeError as e: + print(f"Invalid QMP answer: {e}") + s.close() + return + + if isinstance(obj.get("return"), dict): + if obj["return"]: + print(json.dumps(obj["return"])) + elif i > 0: + print("Error injected.") + elif isinstance(obj.get("error"), dict): + error = obj["error"] + print(f'{error["class"]}: {error["desc"]}') + else: + print(json.dumps(obj)) + + s.shutdown(socket.SHUT_WR) + while 1: + data = s.recv(1024) + if data == b"": + break + try: + obj = json.loads(data.decode("utf-8")) + except json.JSONDecodeError as e: + print(f"Invalid QMP answer: {e}") + s.close() + return + + if isinstance(obj.get("return"), dict): + print(json.dumps(obj["return"])) + if isinstance(obj.get("error"), dict): + error = obj["error"] + print(f'{error["class"]}: {error["desc"]}') + else: + print(json.dumps(obj)) + + s.close() + + +# +# Helper routines to handle multiple choice arguments +# +def get_choice(name, value, choices, suffixes=None): + """Produce a list from multiple choice argument""" + + new_values = 0 + + if not value: + return new_values + + for val in value.split(","): + val = val.lower() + + if suffixes: + for suffix in suffixes: + val = val.removesuffix(suffix) + + if val not in choices.keys(): + sys.exit(f"Error on '{name}': choice {val} is invalid.") + + val = choices[val] + + new_values |= val + + return new_values + + +def get_mult_array(mult, name, values, allow_zero=False, max_val=None): + """Add numbered hashes from integer lists""" + + if not allow_zero: + if not values: + return + else: + if values is None: + return + + if not values: + i = 0 + if i not in mult: + mult[i] = {} + + mult[i][name] = [] + return + + i = 0 + for value in values: + for val in value.split(","): + try: + val = int(val, 0) + except ValueError: + sys.exit(f"Error on '{name}': {val} is not an integer") + + if val < 0: + sys.exit(f"Error on '{name}': {val} is not unsigned") + + if max_val and val > max_val: + sys.exit(f"Error on '{name}': {val} is too little") + + if i not in mult: + mult[i] = {} + + if name not in mult[i]: + mult[i][name] = [] + + mult[i][name].append(val) + + i += 1 + + +def get_mult_choices(mult, name, values, choices, + suffixes=None, allow_zero=False): + """Add numbered hashes from multiple choice arguments""" + + if not allow_zero: + if not values: + return + else: + if values is None: + return + + i = 0 + for val in values: + new_values = get_choice(name, val, choices, suffixes) + + if i not in mult: + mult[i] = {} + + mult[i][name] = new_values + i += 1 + + +def get_mult_int(mult, name, values, allow_zero=False): + """Add numbered hashes from integer arguments""" + if not allow_zero: + if not values: + return + else: + if values is None: + return + + i = 0 + for val in values: + try: + val = int(val, 0) + except ValueError: + sys.exit(f"Error on '{name}': {val} is not an integer") + + if val < 0: + sys.exit(f"Error on '{name}': {val} is not unsigned") + + if i not in mult: + mult[i] = {} + + mult[i][name] = val + i += 1 + + +# +# Data encode helper functions +# +def bit(b): + """Simple macro to define a bit on a bitmask""" + return 1 << b + + +def data_add(data, value, num_bytes): + """Adds bytes from value inside a bitarray""" + + data.extend(value.to_bytes(num_bytes, byteorder="little")) + +def to_guid(time_low, time_mid, time_high, nodes): + """Create an GUID string""" + + assert(len(nodes) == 8) + + clock = nodes[0] << 8 | nodes[1] + + node = 0 + for i in range(2, len(nodes)): + node = node << 8 | nodes[i] + + s = f"{time_low:08x}-{time_mid:04x}-" + s += f"{time_high:04x}-{clock:04x}-{node:012x}" + + return s --2.45.2
Re: [PATCH v5 7/7] scripts/ghes_inject: add a script to generate GHES error inject
In reply to Mauro Carvalho Chehabscripts/qmp_helper.py
Quoted 475 lines · Mauro Carvalho Chehab
Using the QMP GHESv2 API requires preparing a raw data array containing a CPER record.
Add a helper script with subcommands to prepare such data.
Currently, only ARM Processor error CPER record is supported.
Signed-off-by Mauro Carvalho Chehab <[email protected]>--- MAINTAINERS | 3 + scripts/arm_processor_error.py | 352 +++++++++++++++++++++++++++++++++ scripts/ghes_inject.py | 59 ++++++ scripts/qmp_helper.py | 249 +++++++++++++++++++++++ 4 files changed, 663 insertions(+) create mode 100644 scripts/arm_processor_error.py create mode 100755 scripts/ghes_inject.py create mode 100644 scripts/qmp_helper.pyMAINTAINERS +3
-0@@ -2081,6 +2081,9 @@ S: Maintained F: hw/arm/ghes_cper.c F: hw/acpi/ghes_cper_stub.c F: qapi/ghes-cper.json +F: scripts/ghes_inject.py +F: scripts/arm_processor_error.py +F: scripts/qmp_helper.py ppc4xx L: [email protected]scripts/arm_processor_error.py new file +76
-0@@ -0,0 +1,352 @@ +#!/usr/bin/env python3 +# +# pylint: disable=C0301, C0114, R0912, R0913, R0914, R0915, W0511 +# SPDX-License-Identifier: GPL-2.0 +# +# Copyright (C) 2024 Mauro Carvalho Chehab <[email protected]> + +# TODO: current implementation has dummy defaults. +# +# For a better implementation, a QMP addition/call is needed to +# retrieve some data for ARM Processor Error injection: +# +# - machine emulation architecture, as ARM current default is +# for AArch64; +# - ARM registers: power_state, midr, mpidr. + +import argparse +import json + +from qmp_helper import (qmp_command, get_choice, get_mult_array, + get_mult_choices, get_mult_int, bit, + data_add, to_guid) + +# Arm processor EINJ logic +# +ACPI_GHES_ARM_CPER_LENGTH = 40 +ACPI_GHES_ARM_CPER_PEI_LENGTH = 32 + +# TODO: query it from emulation. Current default valid only for Aarch64 +CONTEXT_AARCH64_EL1 = 5 + +class ArmProcessorEinj: + """ + Implements ARM Processor Error injection via GHES + """ + + def __init__(self): + """Initialize the error injection class""" + + # Valid choice values + self.arm_valid_bits = { + "mpidr": bit(0), + "affinity": bit(1), + "running": bit(2), + "vendor": bit(3), + } + + self.pei_flags = { + "first": bit(0), + "last": bit(1), + "propagated": bit(2), + "overflow": bit(3), + } + + self.pei_error_types = { + "cache": bit(1), + "tlb": bit(2), + "bus": bit(3), + "micro-arch": bit(4), + } + + self.pei_valid_bits = { + "multiple-error": bit(0), + "flags": bit(1), + "error-info": bit(2), + "virt-addr": bit(3), + "phy-addr": bit(4), + } + + self.data = bytearray() + + def create_subparser(self, subparsers): + """Add a subparser to handle for the error fields""" + + parser = subparsers.add_parser("arm", + help="Generate an ARM processorCPER")
scripts/arm_processor_error.py new file +11
-0+ + arm_valid_bits = ",".join(self.arm_valid_bits.keys()) + flags = ",".join(self.pei_flags.keys()) + error_types = ",".join(self.pei_error_types.keys()) + pei_valid_bits = ",".join(self.arm_valid_bits.keys()) + + # UEFI N.16 ARM Validation bits + g_arm = parser.add_argument_group("ARM processor") + g_arm.add_argument("--arm", "--arm-valid", + help=f"ARM valid bits: {arm_valid_bits}") + g_arm.add_argument("-a", "--affinity", "--level","--affinity-level",
scripts/arm_processor_error.py new file +2
-0+ type=lambda x: int(x, 0), + help="Affinity level (when multiple levelsapply)")
scripts/arm_processor_error.py new file +8
-0+ g_arm.add_argument("-l", "--mpidr", type=lambda x: int(x, 0), + help="Multiprocessor Affinity Register") + g_arm.add_argument("-i", "--midr", type=lambda x: int(x, 0), + help="Main ID Register") + g_arm.add_argument("-r", "--running", + action=argparse.BooleanOptionalAction, + default=None, + help="Indicates if the processor is running ornot")
scripts/arm_processor_error.py new file +3
-0+ g_arm.add_argument("--psci", "--psci-state", + type=lambda x: int(x, 0), + help="Power State Coordination Interface -PSCI state")
scripts/arm_processor_error.py new file +5
-0+ + # TODO: Add vendor-specific support + + # UEFI N.17 bitmaps (type and flags) + g_pei = parser.add_argument_group("ARM Processor Error Info(PEI)")
scripts/arm_processor_error.py new file +5
-0+ g_pei.add_argument("-t", "--type", nargs="+", + help=f"one or more error types: {error_types}") + g_pei.add_argument("-f", "--flags", nargs="*", + help=f"zero or more error flags: {flags}") + g_pei.add_argument("-V", "--pei-valid", "--error-valid",nargs="*",
+ help=f"zero or more PEI valid bits:
{pei_valid_bits}")scripts/arm_processor_error.py new file +4
-0+ + # UEFI N.17 Integer values + g_pei.add_argument("-m", "--multiple-error", nargs="+", + help="Number of errors: 0: Single error, 1:Multiple errors, 2-65535: Error count if known")
scripts/arm_processor_error.py new file +2
-0+ g_pei.add_argument("-e", "--error-info", nargs="+", + help="Error information (UEFI 2.10 tables N.18 toN.20)")
scripts/arm_processor_error.py new file +9
-0+ g_pei.add_argument("-p", "--physical-address", nargs="+", + help="Physical address") + g_pei.add_argument("-v", "--virtual-address", nargs="+", + help="Virtual address") + + # UEFI N.21 Context + g_ctx = parser.add_argument_group("Processor Context") + g_ctx.add_argument("--ctx-type", "--context-type", nargs="*", + help="Type of the context (0=ARM32 GPR, 5=ARM64EL1, other values supported)")
scripts/arm_processor_error.py new file +226
-0+ g_ctx.add_argument("--ctx-size", "--context-size", nargs="*", + help="Minimal size of the context") + g_ctx.add_argument("--ctx-array", "--context-array", nargs="*", + help="Comma-separated arrays for each context") + + # Vendor-specific data + g_vendor = parser.add_argument_group("Vendor-specific data") + g_vendor.add_argument("--vendor", "--vendor-specific", nargs="+", + help="Vendor-specific byte arrays of data") + + def parse_args(self, args): + """Parse subcommand arguments""" + + cper = {} + pei = {} + ctx = {} + vendor = {} + + arg = vars(args) + + # Handle global parameters + if args.arm: + arm_valid_init = False + cper["valid"] = get_choice(name="valid", + value=args.arm, + choices=self.arm_valid_bits, + suffixes=["-error", "-err"]) + else: + cper["valid"] = 0 + arm_valid_init = True + + if "running" in arg: + if args.running: + cper["running-state"] = bit(0) + else: + cper["running-state"] = 0 + else: + cper["running-state"] = 0 + + if arm_valid_init: + if args.affinity: + cper["valid"] |= self.arm_valid_bits["affinity"] + + if args.mpidr: + cper["valid"] |= self.arm_valid_bits["mpidr"] + + if "running-state" in cper: + cper["valid"] |= self.arm_valid_bits["running"] + + if args.psci: + cper["valid"] |= self.arm_valid_bits["running"] + + # Handle PEI + if not args.type: + args.type = ["cache-error"] + + get_mult_choices( + pei, + name="valid", + values=args.pei_valid, + choices=self.pei_valid_bits, + suffixes=["-valid", "-info", "--information", "--addr"], + ) + get_mult_choices( + pei, + name="type", + values=args.type, + choices=self.pei_error_types, + suffixes=["-error", "-err"], + ) + get_mult_choices( + pei, + name="flags", + values=args.flags, + choices=self.pei_flags, + suffixes=["-error", "-cap"], + ) + get_mult_int(pei, "error-info", args.error_info) + get_mult_int(pei, "multiple-error", args.multiple_error) + get_mult_int(pei, "phy-addr", args.physical_address) + get_mult_int(pei, "virt-addr", args.virtual_address) + + # Handle context + get_mult_int(ctx, "type", args.ctx_type, allow_zero=True) + get_mult_int(ctx, "minimal-size", args.ctx_size, allow_zero=True) + get_mult_array(ctx, "register", args.ctx_array, allow_zero=True) + + get_mult_array(vendor, "bytes", args.vendor, max_val=255) + + # Store PEI + pei_data = bytearray() + default_flags = self.pei_flags["first"] + default_flags |= self.pei_flags["last"] + + error_info_num = 0 + + for i, p in pei.items(): # pylint: disable=W0612 + error_info_num += 1 + + # UEFI 2.10 doesn't define how to encode error information + # when multiple types are raised. So, provide a default only + # if a single type is there + if "error-info" not in p: + if p["type"] == bit(1): + p["error-info"] = 0x0091000F + if p["type"] == bit(2): + p["error-info"] = 0x0054007F + if p["type"] == bit(3): + p["error-info"] = 0x80D6460FFF + if p["type"] == bit(4): + p["error-info"] = 0x78DA03FF + + if "valid" not in p: + p["valid"] = 0 + if "multiple-error" in p: + p["valid"] |= self.pei_valid_bits["multiple-error"] + + if "flags" in p: + p["valid"] |= self.pei_valid_bits["flags"] + + if "error-info" in p: + p["valid"] |= self.pei_valid_bits["error-info"] + + if "phy-addr" in p: + p["valid"] |= self.pei_valid_bits["phy-addr"] + + if "virt-addr" in p: + p["valid"] |= self.pei_valid_bits["virt-addr"] + + # Version + data_add(pei_data, 0, 1) + + data_add(pei_data, ACPI_GHES_ARM_CPER_PEI_LENGTH, 1) + + data_add(pei_data, p["valid"], 2) + data_add(pei_data, p["type"], 1) + data_add(pei_data, p.get("multiple-error", 1), 2) + data_add(pei_data, p.get("flags", default_flags), 1) + data_add(pei_data, p.get("error-info", 0), 8) + data_add(pei_data, p.get("virt-addr", 0xDEADBEEF), 8) + data_add(pei_data, p.get("phy-addr", 0xABBA0BAD), 8) + + # Store Context + ctx_data = bytearray() + context_info_num = 0 + + if ctx: + for k in sorted(ctx.keys()): + context_info_num += 1 + + if "type" not in ctx: + ctx[k]["type"] = CONTEXT_AARCH64_EL1 + + if "register" not in ctx: + ctx[k]["register"] = [] + + reg_size = len(ctx[k]["register"]) + size = 0 + + if "minimal-size" in ctx: + size = ctx[k]["minimal-size"] + + size = max(size, reg_size) + + size = (size + 1) % 0xFFFE + + # Version + data_add(ctx_data, 0, 2) + + data_add(ctx_data, ctx[k]["type"], 2) + + data_add(ctx_data, 8 * size, 4) + + for r in ctx[k]["register"]: + data_add(ctx_data, r, 8) + + for i in range(reg_size, size): # pylint: disable=W0612 + data_add(ctx_data, 0, 8) + + # Vendor-specific bytes are not grouped + vendor_data = bytearray() + if vendor: + for k in sorted(vendor.keys()): + for b in vendor[k]["bytes"]: + data_add(vendor_data, b, 1) + + # Encode ARM Processor Error + data = bytearray() + + data_add(data, cper["valid"], 4) + + data_add(data, error_info_num, 2) + data_add(data, context_info_num, 2) + + # Calculate the length of the CPER data + cper_length = ACPI_GHES_ARM_CPER_LENGTH + cper_length += len(pei_data) + cper_length += len(vendor_data) + cper_length += len(ctx_data) + data_add(data, cper_length, 4) + + data_add(data, arg.get("affinity-level", 0), 1) + + # Reserved + data_add(data, 0, 3) + + data_add(data, arg.get("mpidr-el1", 0), 8) + data_add(data, arg.get("midr-el1", 0), 8) + data_add(data, cper["running-state"], 4) + data_add(data, arg.get("psci-state", 0), 4) + + # Add PEI + data.extend(pei_data) + data.extend(ctx_data) + data.extend(vendor_data) + + self.data = data + + def run(self, host, port): + """Execute QMP commands""" + + guid = to_guid(0xE19E3D16, 0xBC11, 0x11E4, + [0x9C, 0xAA, 0xC2, 0x05, + 0x1D, 0x5D, 0x46, 0xB0]) + + qmp_command(host, port, guid, self.data)scripts/ghes_inject.py new file +35
-0@@ -0,0 +1,59 @@ +#!/usr/bin/env python3 +# +# pylint: disable=C0301, C0114 +# SPDX-License-Identifier: GPL-2.0 +# +# Copyright (C) 2024 Mauro Carvalho Chehab <[email protected]> + +import argparse + +from arm_processor_error import ArmProcessorEinj + +EINJ_DESCRIPTION = """ +Handle ACPI GHESv2 error injection logic QEMU QMP interface.\n + +It allows using UEFI BIOS EINJ features to generate GHES records. + +It helps testing Linux CPER and GHES drivers and to test rasdaemon +error handling logic. + +Currently, it support ARM processor error injection for ARM processor +events, being compatible with UEFI 2.9A Errata. + +This small utility works together with those QEMU additions: +- https://gitlab.com/mchehab_kernel/qemu/-/tree/arm-error-inject-v2 +""" + +def main(): + """Main program""" + + # Main parser - handle generic args like QEMU QMP TCP socket options + parser = argparse.ArgumentParser(prog="einj.py", + formatter_class=argparse.RawDescriptionHelpFormatter, + usage="%(prog)s [options]", + description=EINJ_DESCRIPTION, + epilog="If a field is not defined, adefault value will be applied by QEMU.")
scripts/ghes_inject.py new file +24
-0+ + g_options = parser.add_argument_group("QEMU QMP socket options") + g_options.add_argument("-H", "--host", default="localhost", type=str, + help="host name") + g_options.add_argument("-P", "--port", default=4445, type=int, + help="TCP port number") + + arm_einj = ArmProcessorEinj() + + # Call subparsers + subparsers = parser.add_subparsers(dest='command') + + arm_einj.create_subparser(subparsers) + + args = parser.parse_args() + + # Handle subparser commands + if args.command == "arm": + arm_einj.parse_args(args) + arm_einj.run(args.host, args.port) + + +if __name__ == "__main__": + main()scripts/qmp_helper.py new file +0
-0
I'm going to admit I only glanced at this very briefly, but -- is there a chance you could use qemu.git/python/qemu/qmp instead of writing your own helpers here?
If *NOT*, is there something that I need to add to our QMP library to facilitate your script?
Quoted 36 lines
scripts/qmp_helper.py new file +34
-0@@ -0,0 +1,249 @@ +#!/usr/bin/env python3 +# +# pylint: disable=C0301, C0114, R0912, R0913, R0915, W0511 +# SPDX-License-Identifier: GPL-2.0 +# +# Copyright (C) 2024 Mauro Carvalho Chehab <[email protected]> + +import json +import socket +import sys + +from base64 import b64encode + +# +# Socket QMP send command +# +def qmp_command(host, port, guid, data): + """Send commands to QEMU though QMP TCP socket""" + + # Fill the commands to be sent + commands = [] + + # Needed to negotiate QMP and for QEMU to accept the command + commands.append('{ "execute": "qmp_capabilities" } ') + + base64_data = b64encode(bytes(data)).decode('ascii') + + cmd_arg = { + 'cper': { + 'notification-type': guid, + "raw-data": base64_data + } + } +
scripts/qmp_helper.py line 44
Quoted 10 lines
scripts/qmp_helper.py new file +10
-0+ command = '{ "execute": "ghes-cper", ' + command += '"arguments": ' + json.dumps(cmd_arg) + " }" + + commands.append(command) + + s = socket.socket(socket.AF_INET, socket.SOCK_STREAM) + try: + s.connect((host, port)) + except ConnectionRefusedError: + sys.exit(f"Can't connect to QMP host {host}:{port}")
You should be able to use e.g.
legacy.py's QEMUMonitorProtocol class for synchronous connections, e.g.
from qemu.qmp.legacy import QEMUMonitorProtocol
qmp = QEMUMonitorProtocol((host, port))qmp.connect(negotiate=True)
If you want to run the script w/o setting up a virtual environment or installing the package, take a look at the hacks in scripts/qmp/ for how I support e.g. qom-get directly from the source tree.
Quoted 6 lines
scripts/qmp_helper.py new file +5
-0+ + data = s.recv(1024) + try: + obj = json.loads(data.decode("utf-8")) + except json.JSONDecodeError as e:
scripts/qmp_helper.py line 59
Quoted 10 lines
scripts/qmp_helper.py new file +10
-0+ print(f"Invalid QMP answer: {e}") + s.close() + return + + if "QMP" not in obj: + print(f"Invalid QMP answer: {data.decode("utf-8")}") + s.close() + return + + for i, command in enumerate(commands):
Then here you'd use qmp.cmd (raises exception on QMPError) or qmp.cmd_raw or qmp.cmd_obj (returns the QMP response as the return value even if it was an error.)
More details:
https://qemu.readthedocs.io/projects/python-qemu-qmp/en/latest/qemu.qmp.legacy.html
There's also an async version, but it doesn't look like you require that complexity, so you can ignore it.
~~js
+ s.sendall(command.encode("utf-8"))
Quoted 193 lines
scripts/qmp_helper.py new file +189
-1+ data = s.recv(1024) + try: + obj = json.loads(data.decode("utf-8")) + except json.JSONDecodeError as e: + print(f"Invalid QMP answer: {e}") + s.close() + return + + if isinstance(obj.get("return"), dict): + if obj["return"]: + print(json.dumps(obj["return"])) + elif i > 0: + print("Error injected.") + elif isinstance(obj.get("error"), dict): + error = obj["error"] + print(f'{error["class"]}: {error["desc"]}') + else: + print(json.dumps(obj)) + + s.shutdown(socket.SHUT_WR) + while 1: + data = s.recv(1024) + if data == b"": + break + try: + obj = json.loads(data.decode("utf-8")) + except json.JSONDecodeError as e: + print(f"Invalid QMP answer: {e}") + s.close() + return + + if isinstance(obj.get("return"), dict): + print(json.dumps(obj["return"])) + if isinstance(obj.get("error"), dict): + error = obj["error"] + print(f'{error["class"]}: {error["desc"]}') + else: + print(json.dumps(obj)) + + s.close() + + +# +# Helper routines to handle multiple choice arguments +# +def get_choice(name, value, choices, suffixes=None): + """Produce a list from multiple choice argument""" + + new_values = 0 + + if not value: + return new_values + + for val in value.split(","): + val = val.lower() + + if suffixes: + for suffix in suffixes: + val = val.removesuffix(suffix) + + if val not in choices.keys(): + sys.exit(f"Error on '{name}': choice {val} is invalid.") + + val = choices[val] + + new_values |= val + + return new_values + + +def get_mult_array(mult, name, values, allow_zero=False, max_val=None): + """Add numbered hashes from integer lists""" + + if not allow_zero: + if not values: + return + else: + if values is None: + return + + if not values: + i = 0 + if i not in mult: + mult[i] = {} + + mult[i][name] = [] + return + + i = 0 + for value in values: + for val in value.split(","): + try: + val = int(val, 0) + except ValueError: + sys.exit(f"Error on '{name}': {val} is not an integer") + + if val < 0: + sys.exit(f"Error on '{name}': {val} is not unsigned") + + if max_val and val > max_val: + sys.exit(f"Error on '{name}': {val} is too little") + + if i not in mult: + mult[i] = {} + + if name not in mult[i]: + mult[i][name] = [] + + mult[i][name].append(val) + + i += 1 + + +def get_mult_choices(mult, name, values, choices, + suffixes=None, allow_zero=False): + """Add numbered hashes from multiple choice arguments""" + + if not allow_zero: + if not values: + return + else: + if values is None: + return + + i = 0 + for val in values: + new_values = get_choice(name, val, choices, suffixes) + + if i not in mult: + mult[i] = {} + + mult[i][name] = new_values + i += 1 + + +def get_mult_int(mult, name, values, allow_zero=False): + """Add numbered hashes from integer arguments""" + if not allow_zero: + if not values: + return + else: + if values is None: + return + + i = 0 + for val in values: + try: + val = int(val, 0) + except ValueError: + sys.exit(f"Error on '{name}': {val} is not an integer") + + if val < 0: + sys.exit(f"Error on '{name}': {val} is not unsigned") + + if i not in mult: + mult[i] = {} + + mult[i][name] = val + i += 1 + + +# +# Data encode helper functions +# +def bit(b): + """Simple macro to define a bit on a bitmask""" + return 1 << b + + +def data_add(data, value, num_bytes): + """Adds bytes from value inside a bitarray""" + + data.extend(value.to_bytes(num_bytes, byteorder="little")) + +def to_guid(time_low, time_mid, time_high, nodes): + """Create an GUID string""" + + assert(len(nodes) == 8) + + clock = nodes[0] << 8 | nodes[1] + + node = 0 + for i in range(2, len(nodes)): + node = node << 8 | nodes[i] + + s = f"{time_low:08x}-{time_mid:04x}-" + s += f"{time_high:04x}-{clock:04x}-{node:012x}" + + return s --2.45.2
Re: [PATCH v5 7/7] scripts/ghes_inject: add a script to generate GHES error inject
In reply to John SnowEm Thu, 8 Aug 2024 16:58:38 -0400
John Snow <[email protected]> escreveu:
Quoted 10 lines
scripts/arm_processor_error.py line 3
Quoted 4 lines · Mauro Carvalho Chehab
scripts/arm_processor_error.py new file +3
-0+#!/usr/bin/env python3 +# +# pylint: disable=C0301, C0114, R0912, R0913, R0914, R0915, W0511Out of curiosity, what tools are you using to delint your files
Primarily I use pylint, almost always with disable line(s), as those lint tools have some warnings that sound too silly (like too many/too low functions/branches/arguments...). From time to time, I review the disable lines, to keep the code as clean as desired.
Sometimes I also use pep8 (now named as pycodestyle) and black, specially when I want some autoformat hints (I manually commit the hunks that make sense), but I prefer pylint as the primary checking tool. I'm not too found of the black's coding style, though[1].
[1] For instance, black would do this change:
- g_arm.add_argument("--arm", "--arm-valid",
- help=f"ARM valid bits: {arm_valid_bits}")
+ g_arm.add_argument(
+ "--arm", "--arm-valid", help=f"ARM valid bits: {arm_valid_bits}"
+ )
IMO, the original coding style I wrote is a lot better than black's suggestion - and it is closer to the C style I use at the Linux Kernel ;-)
Quoted 2 lines
and how are
you invoking them?
I don't play much with such tools, though. I usually just invoke them with the python file names(s) without passing any parameters nor creating any configuration file.
Quoted 4 lines
I don't really maintain any strict regime for python files under qemu.git/scripts (yet), so I am mostly curious as to what regimes others are using currently. I don't see most QEMU contributors checking in pylint ignores etc directly into the files, so it caught my eye.
Having some verification sounds interesting, as it may help preventing some hidden bugs (like re-defining a variable that it was already used globally), if such check is not too picky and if stupid warnings can be bypassed.
Regards,
Mauro
Re: [PATCH v5 7/7] scripts/ghes_inject: add a script to generate GHES error inject
In reply to John SnowEm Thu, 8 Aug 2024 17:21:33 -0400
John Snow <[email protected]> escreveu:
Quoted 15 lines
scripts/qmp_helper.py
Quoted 6 lines · Mauro Carvalho Chehab
scripts/qmp_helper.py new file +0
-0I'm going to admit I only glanced at this very briefly, but -- is there a chance you could use qemu.git/python/qemu/qmp instead of writing your own helpers here?
Quoted 2 lines
If *NOT*, is there something that I need to add to our QMP library to facilitate your script?
I started writing this script to be hosted outside qemu tree, when we had a very different API.
I noticed later about the QMP, and even tried to write a patch for it, but I gave up due to asyncio complexity...
Please notice that, on this file, I actually placed three classes:
- qmp
- util
- cper_guid
I could probably make the first one to be an override of QEMUMonitorProtocol (besides normal open/close/cmd communication, it also contains some methods that are specific to error inject use case:
- to generate a CPER record;
- to search for data via qom-get.
The other two classes are just common code used by ghes_inject commands. My idea is to have multiple commands to do different kinds of GHES error injection, each command on a different file/class.
Quoted 7 lines
scripts/qmp_helper.py line 44
Quoted 6 lines
scripts/qmp_helper.py new file +5
-0+ s = socket.socket(socket.AF_INET, socket.SOCK_STREAM) + try: + s.connect((host, port)) + except ConnectionRefusedError: + sys.exit(f"Can't connect to QMP host {host}:{port}")
Quoted 8 lines
You should be able to use e.g.
legacy.py's QEMUMonitorProtocol class for synchronous connections, e.g.
from qemu.qmp.legacy import QEMUMonitorProtocol
qmp =
QEMUMonitorProtocol((host, port))qmp.connect(negotiate=True)
That sounds interesting! I give it a try.
Quoted 3 lines
If you want to run the script w/o setting up a virtual environment or installing the package, take a look at the hacks in
scripts/qmp/for how I support e.g. qom-get directly from the source tree.
Yeah, I saw that already. Doing:
sys.path.append(path.join(qemu_dir, 'python'))
the same way qom-get does should do the trick.
Quoted 12 lines
Quoted 12 lines
scripts/qmp_helper.py new file +12
-0+ + data = s.recv(1024) + try: + obj = json.loads(data.decode("utf-8")) + except json.JSONDecodeError as e: + print(f"Invalid QMP answer: {e}") + s.close() + return + + if "QMP" not in obj: + print(f"Invalid QMP answer: {data.decode("utf-8")}") + s.close()
Quoted 8 lines
scripts/qmp_helper.py line 59
Quoted 4 lines
scripts/qmp_helper.py new file +3
-0+ return + + for i, command in enumerate(commands):Then here you'd use qmp.cmd (raises exception on QMPError) or qmp.cmd_raw or qmp.cmd_obj (returns the QMP response as the return value even if it was an error.)
Good to know, I'll try and see what fits best.
Quoted 2 lines
More details:
https://qemu.readthedocs.io/projects/python-qemu-qmp/en/latest/qemu.qmp.legacy.html
I'll take a look. The name "legacy" is a little scary, as it might imply that this has been deprecated. If there's no plans to deprecate, then it would be great to use it and simplify the code a little bit.
Quoted 2 lines
There's also an async version, but it doesn't look like you require that complexity, so you can ignore it.
Yes, that's the case: a serialized sync send/response logic works perfectly for this script. No need to be burden with asyncio complexity.
Thanks,
Mauro
Re: [PATCH v5 7/7] scripts/ghes_inject: add a script to generate GHES error inject
Quoted 18 lines · Mauro Carvalho Chehab
Em Thu, 8 Aug 2024 17:21:33 -0400
John Snow <[email protected]> escreveu:Quoted 15 lines
scripts/qmp_helper.py
Quoted 6 lines · Mauro Carvalho Chehab
scripts/qmp_helper.py new file +0
-0I'm going to admit I only glanced at this very briefly, but -- is there a chance you could use qemu.git/python/qemu/qmp instead of writing your own helpers here?
Quoted 9 lines
Quoted 2 lines
If *NOT*, is there something that I need to add to our QMP library to facilitate your script?
I started writing this script to be hosted outside qemu tree, when we had a very different API.
I noticed later about the QMP, and even tried to write a patch for it, but I gave up due to asyncio complexity...
Sorry :)
Quoted 12 lines
Please notice that, on this file, I actually placed three classes:
- qmp
- util
-cper_guidI could probably make the first one to be an override of QEMUMonitorProtocol
(besides normal open/close/cmd communication, it also contains some methods that are specific to error inject use case:
Quoted 7 lines
- to generate a CPER record;
- to search for data via qom-get.The other two classes are just common code used by
ghes_injectcommands. My idea is to have multiple commands to do different kinds of GHES error injection, each command on a different file/class.
Gotcha! Thanks for the feedback. I would *prefer* that code checked in to qemu.git use the QMP module where possible so that I don't have to maintain multiple copies of QMP wrangling code. I think what you want to do should be easily possible with the existing library; and anything that isn't, I'm more than happy to meet your needs. Reach out absolutely any time.
Quoted 49 lines
Quoted 8 lines
scripts/qmp_helper.py line 44
Quoted 7 lines
scripts/qmp_helper.py new file +5
-0+ s = socket.socket(socket.AF_INET, socket.SOCK_STREAM) + try: + s.connect((host, port)) + except ConnectionRefusedError: + sys.exit(f"Can't connect to QMP host {host}:{port}")Quoted 8 lines
You should be able to use e.g.
legacy.py's QEMUMonitorProtocol class for synchronous connections, e.g.
from qemu.qmp.legacy import QEMUMonitorProtocol
qmp =
QEMUMonitorProtocol((host, port))qmp.connect(negotiate=True)That sounds interesting! I give it a try.
Quoted 2 lines
If you want to run the script w/o setting up a virtual environment or installing the package, take a look at the hacks in
scripts/qmp/for howI
Quoted 1 line
support e.g. qom-get directly from the source tree.
Yeah, I saw that already. Doing:
sys.path.append(path.join(qemu_dir, 'python'))the same way qom-get does should do the trick.
Quoted 11 lines
Quoted 11 lines
scripts/qmp_helper.py new file +11
-0+ + data = s.recv(1024) + try: + obj = json.loads(data.decode("utf-8")) + except json.JSONDecodeError as e: + print(f"Invalid QMP answer: {e}") + s.close() + return + + if "QMP" not in obj: + print(f"Invalid QMP answer: {data.decode("utf-8")}")Quoted 8 lines
scripts/qmp_helper.py line 59
Quoted 5 lines
scripts/qmp_helper.py new file +4
-0+ s.close() + return + + for i, command in enumerate(commands):Then here you'd use qmp.cmd (raises exception on QMPError) or qmp.cmd_raw or qmp.cmd_obj (returns the QMP response as the return value even if it
Quoted 5 lines
was
Quoted 1 line
an error.)
Good to know, I'll try and see what fits best.
I might *suggest* you try to use the exception-raising interface and catch exceptions to interrogate expected errors as it aligns better with the "idiomatic python API" - I have no plans to support an external API that *returns* error objects except via the exception class. This approach will be easier to port when I drop the legacy interface in the future, see below.
But, that said, whichever is easiest. We use all three interfaces in many places in the QEMU tree. I have no grounds to require you to use a specific one ;)
Quoted 9 lines
Quoted 3 lines
More details:
https://qemu.readthedocs.io/projects/python-qemu-qmp/en/latest/qemu.qmp.legacy.html
I'll take a look. The name "legacy" is a little scary, as it might imply that this has been deprecated. If there's no plans to deprecate, then it would be great to use it and simplify the code a little bit.
I named it legacy to be scary on purpose :)
The truth is that the "legacy" module was designed to be a 1:1 drop-in replacement for an older version of the synchronous QMP library that powered our internal iotests. We still use this "legacy" module in thousands of places in the QEMU tree. I do have plans to replace it with a "proper" synchronous frontend class, eventually, someday, etc. It's been a while and I still haven't done it, though. Oops...
When I do eventually replace it, I will convert all users inside of qemu.git personally, and the design of the "non-legacy" API will be chosen pretty explicitly to make that task really easy for myself and reviewers. This would include your script inside the qemu.git tree. It should be pretty safe to use the legacy module *in qemu.git*, but for external, out-of-tree scripts, it may indeed disappear someday - but converting to the new API, when I merge it, should be very, very trivial. How much of a headache that is for you depends on how you package/distribute the script and how awful it will be to update the code and dependencies when it happens.
FYI: I have promised in the readme for the standalone version of qemu.qmp that legacy.py will not be removed prior to v0.1.0. All versions before then will still have it, guaranteed.
(Neither here nor there: One of the holdups in this replacement is figuring out how to structure the API for event listening, which was the main motivator of the *async* version of the class. We have many users who don't want full async handling, but still want to listen for and catch events. I need a proper sit and think for what the API I want to commit to supporting and maintaining for this should look like. Not your problem, anyway!)
Quoted 11 lines
Quoted 3 lines
There's also an async version, but it doesn't look like you require that complexity, so you can ignore it.
Yes, that's the case: a serialized sync send/response logic works perfectly for this script. No need to be burden with asyncio complexity.
Thanks,
Mauro
Re: [PATCH v5 7/7] scripts/ghes_inject: add a script to generate GHES error inject
In reply to Mauro Carvalho ChehabEm Fri, 9 Aug 2024 00:41:37 +0200
Mauro Carvalho Chehab <[email protected]> escreveu:
Quoted 10 lines
Quoted 8 lines
You should be able to use e.g.
legacy.py's QEMUMonitorProtocol class for synchronous connections, e.g.
from qemu.qmp.legacy import QEMUMonitorProtocol
qmp =
QEMUMonitorProtocol((host, port))qmp.connect(negotiate=True)That sounds interesting! I give it a try.
I applied the enclosed patch at the end of my patch series, but somehow it is not working. For whatever reason, connect() is raising a StateError apparently due to Runstate.CONNECTING.
I tried both as declaring (see enclosed patch):
class qmp(QEMUMonitorProtocol)
and using:
- super().__init__(self.host, self.port)
+ self.qmp_monitor = QEMUMonitorProtocol(self.host, self.port)
On both cases, it keeps waiting forever for a connection.
Regards,
Mauro
---
scripts/qmp_helper.py +53 -71
@@ -9,9 +9,23 @@ import socket import sys +from os import path + +try: + qemu_dir = path.abspath(path.dirname(path.dirname(__file__))) + sys.path.append(path.join(qemu_dir, 'python')) + + from qemu.qmp.legacy import QEMUMonitorProtocol + from qemu.qmp.protocol import StateError + +except ModuleNotFoundError as exc: + print(f"Module '{exc.name}' not found.") + print("Try export PYTHONPATH=top-qemu-dir/python or run from top-qemu-dir") + sys.exit(1) + from base64 import b64encode -class qmp: +class qmp(QEMUMonitorProtocol): """ Opens a connection and send/receive QMP commands. """
@@ -21,22 +35,20 @@ def send_cmd(self, command, may_open=False,return_error=True): if may_open: self._connect() - elif not self.socket: - return None + elif not self.connected: + return False if isinstance(command, dict): data = json.dumps(command).encode("utf-8") else: data = command.encode("utf-8") - self.socket.sendall(data) - data = self.socket.recv(1024) try: - obj = json.loads(data.decode("utf-8")) - except json.JSONDecodeError as e: - print(f"Invalid QMP answer: {e}") - self._close() - return None + obj = self.cmd_obj(command) + except Exception as e: + print("Failed to inject error: {e}.") + + print(obj) if "return" in obj: if isinstance(obj.get("return"), dict):
@@ -46,86 +58,47 @@ def send_cmd(self, command, may_open=False,return_error=True): else: return obj["return"] - elif isinstance(obj.get("error"), dict): - error = obj["error"] - if return_error: - print(f'{error["class"]}: {error["desc"]}') - else: - print(json.dumps(obj)) - return None def _close(self): """Shutdown and close the socket, if opened""" - if not self.socket: + if not self.connected: return - self.socket.shutdown(socket.SHUT_WR) - while 1: - data = self.socket.recv(1024) - if data == b"": - break - try: - obj = json.loads(data.decode("utf-8")) - except json.JSONDecodeError as e: - print(f"Invalid QMP answer: {e}") - self.socket.close() - self.socket = None - return - - if isinstance(obj.get("return"), dict): - print(json.dumps(obj["return"])) - if isinstance(obj.get("error"), dict): - error = obj["error"] - print(f'{error["class"]}: {error["desc"]}') - else: - print(json.dumps(obj)) - - self.socket.close() - self.socket = None + self.close() + self.connected = False def _connect(self): """Connect to a QMP TCP/IP port, if not connected yet""" - if self.socket: + if self.connected: return True - self.socket = socket.socket(socket.AF_INET, socket.SOCK_STREAM) - try: - self.socket.connect((self.host, self.port)) - except ConnectionRefusedError: - sys.exit(f"Can't connect to QMP host {self.host}:{self.port}") - - data = self.socket.recv(1024) - try: - obj = json.loads(data.decode("utf-8")) - except json.JSONDecodeError as e: - print(f"Invalid QMP answer: {e}") - self._close() - return False - - if "QMP" not in obj: - print(f"Invalid QMP answer: {data.decode('utf-8')}") - self._close() - return False + is_connecting = True + while is_connecting: + try: + ret = self.connect(negotiate=True) + self.accept() + is_connecting = False + except ConnectionError: + sys.exit(f"Can't connect to QMP host {self.host}:{self.port}") + return False + except StateError as e: + print(f"StateError: {e}") - result = self.send_cmd('{ "execute": "qmp_capabilities" }') - if not result: - self._close() - return False + self.connected = True return True def __init__(self, host, port, debug=False): """Initialize variables used by the QMP send logic""" - self.socket = None + self.connected = False self.host = host self.port = port self.debug = debug - def __del__(self): - self._close() + super().__init__(self.host, self.port) # # Socket QMP send command
@@ -168,8 +141,12 @@ def send_cper(self, guid, data): self._connect() - if self.send_cmd(command): - print("Error injected.") + try: + self.cmd_obj(command) + except Exception as e: + print("Failed to inject error: {e}.") + + print("Error injected.") def search_qom(self, path, prop, regex): """
@@ -180,8 +157,9 @@ def search_qom(self, path, prop, regex): ... """ - found = [] + self._connect() + found = [] i = 0 while 1: dev = f"{path}[{i}]"
@@ -192,7 +170,11 @@ def search_qom(self, path, prop, regex): 'property': prop } } - ret = self.send_cmd(cmd, may_open=True, return_error=False) + try: + ret = self.cmd_obj(cmd) + except Exception as e: + print("Failed to inject error: {e}.") + if not ret: break
Thanks,
Mauro
Re: [PATCH v5 7/7] scripts/ghes_inject: add a script to generate GHES error inject
Em Fri, 9 Aug 2024 08:26:09 +0200
Mauro Carvalho Chehab <[email protected]> escreveu:
Quoted 27 lines
Em Fri, 9 Aug 2024 00:41:37 +0200
Mauro Carvalho Chehab <[email protected]> escreveu:Quoted 10 lines
Quoted 8 lines
You should be able to use e.g.
legacy.py's QEMUMonitorProtocol class for synchronous connections, e.g.
from qemu.qmp.legacy import QEMUMonitorProtocol
qmp =
QEMUMonitorProtocol((host, port))qmp.connect(negotiate=True)That sounds interesting! I give it a try.
I applied the enclosed patch at the end of my patch series, but somehow it is not working. For whatever reason,
connect()is raising a StateError apparently due to Runstate.CONNECTING.I tried both as declaring (see enclosed patch):
class qmp(QEMUMonitorProtocol)
and using:
(quoted diff) +1
-1- super().__init__(self.host, self.port) + self.qmp_monitor = QEMUMonitorProtocol(self.host, self.port)
Quoted 1 line
On both cases, it keeps waiting forever for a connection.
Nevermind, placing host/post on a tuple made it work.
The enclosed patch converts the script to use QEMUMonitorProtocol.
I'll fold it with the script for the next spin of this series.
Regards,
Mauro
---
[PATCH] scripts/qmp_helper.py: use QEMUMonitorProtocol class
Instead of reinventing the wheel, let's use QEMUMonitorProtocol.
scripts/arm_processor_error.py +9 -16
@@ -169,14 +169,11 @@ def send_cper(self, args): if args.mpidr: cper["mpidr-el1"] = arg["mpidr"] elif cpus: - get_mpidr = { - "execute": "qom-get", - "arguments": { - 'path': cpus[0], - 'property': "x-mpidr" - } + cmd_arg = { + 'path': cpus[0], + 'property': "x-mpidr" } - ret = qmp_cmd.send_cmd(get_mpidr, may_open=True) + ret = qmp_cmd.send_cmd("qom-get", cmd_arg, may_open=True) if isinstance(ret, int): cper["mpidr-el1"] = ret else:
@@ -291,8 +288,7 @@ def send_cper(self, args): context_info_num = 0 if ctx: - ret = qmp_cmd.send_cmd('{ "execute": "query-target" }', - may_open=True) + ret = qmp_cmd.send_cmd("query-target", may_open=True) default_ctx = self.CONTEXT_MISC_REG
@@ -363,14 +359,11 @@ def send_cper(self, args): if "midr-el1" not in arg: if cpus: - get_mpidr = { - "execute": "qom-get", - "arguments": { - 'path': cpus[0], - 'property': "midr" - } + cmd_arg = { + 'path': cpus[0], + 'property': "midr" } - ret = qmp_cmd.send_cmd(get_mpidr, may_open=True) + ret = qmp_cmd.send_cmd("qom-get", cmd_arg, may_open=True) if isinstance(ret, int): arg["midr-el1"] = ret
scripts/qmp_helper.py +38 -71
181 lines not on this page · raw message
Re: [PATCH v5 7/7] scripts/ghes_inject: add a script to generate GHES error inject
In reply to John SnowEm Thu, 8 Aug 2024 19:33:32 -0400
John Snow <[email protected]> escreveu:
Quoted 14 lines
Quoted 7 lines
Quoted 2 lines
Then here you'd use qmp.cmd (raises exception on QMPError) or qmp.cmd_raw or qmp.cmd_obj (returns the QMP response as the return value even if it
was
Quoted 1 line
an error.)
Good to know, I'll try and see what fits best.
I might *suggest* you try to use the exception-raising interface and catch exceptions to interrogate expected errors as it aligns better with the "idiomatic python API" - I have no plans to support an external API that *returns* error objects except via the exception class. This approach will be easier to port when I drop the legacy interface in the future, see below.
Quoted 3 lines
But, that said, whichever is easiest. We use all three interfaces in many places in the QEMU tree. I have no grounds to require you to use a specific one ;)
While a python-style exception handling is cool, I ended opting to use cmd_obj(), as the script needs to catch the end of /machine/unattached/device[] array, and using cmd_obj() made the conversion easier.
One of the things I missed at the documentation is a description of the possible exceptions that cmd() could raise.
It is probably worth documenting it and placing them on a QMP-specific error class, but a change like that would probably be incompatible with the existing applications. Probably something to be considered on your TODO list to move this from legacy ;-)
Anyway, I already folded the changes at the branch I'll be using as basis for the next submission (be careful to use it, as I'm always rebasing it):
https://gitlab.com/mchehab_kernel/qemu/-/commit/62feb8f6037ab762a9848eb601a041fbbbe2a77a#b665bcbc1e5ae3a488f1c0f20f8c29ae640bfa63_0_17
Thanks,
Mauro
Re: [PATCH v5 5/7] qapi/ghes-cper: add an interface to do generic CPER error injection
In reply to Markus ArmbrusterEm Thu, 08 Aug 2024 16:45:51 +0200
Markus Armbruster <[email protected]> escreveu:
Quoted 45 lines
Quoted 43 lines · Igor Mammedov
Quoted 40 lines · On Thu, 8 Aug 2024 16:11:41 +0200 Mauro Carvalho Chehab…
Em Thu, 08 Aug 2024 10:50:33 +0200
Markus Armbruster <[email protected]> escreveu:Quoted 21 lines
Quoted 5 lines · Mauro Carvalho Chehab
MAINTAINERS +0
-0MAINTAINERS F: hw/acpi/ghes.c · line 2084
Quoted 10 lines
MAINTAINERS +7
-0@@ -2075,6 +2075,13 @@ F: hw/acpi/ghes.c F: include/hw/acpi/ghes.h F: docs/specs/acpi_hest_ghes.rst +ACPI/HEST/GHES/ARM processor CPER +R: Mauro Carvalho Chehab <[email protected]> +S: Maintained +F: hw/arm/ghes_cper.c +F: hw/acpi/ghes_cper_stub.c +F: qapi/ghes-cper.json +Here's the reason for creating a new QAPI module instead of adding to existing module acpi.json: different maintainers.
Quoted 2 lines
Hypothetical question: if we didn't care for that, would this go into
qapi/acpi.json?Independently of maintainers, GHES is part of ACPI APEI HEST, meaning to report hardware errors. Such hardware errors are typically handled by the host OS, so quest doesn't need to be aware of that[1].
So, IMO the best would be to keep APEI/HEST/GHES in a separate file.
[1] still, I can foresee some scenarios were passing some errors to the guest could make sense.
Quoted 3 lines
If yes, then should we call it acpi-ghes-cper.json or acpi-ghes.json instead?
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
Naming it as acpi-ghes,acpi-hest or acpi-ghes-cper would equally work from my side.
if we going to keep it generic, acpi-hest would do
Works for me.
Ok, I'll do the rename. With regards to the files implementing support for it:
hw/acpi/ghes_cper.c
hw/acpi/ghes_cper_stub.c
I guess there's no need to rename them, right? IMO such names are better than acpi/hest.c, specially since the actual implementation for HEST is inside acpi/ghes.c.
Quoted 36 lines
Quoted 36 lines
Quoted 26 lines
Quoted 26 lines
Quoted 4 lines
MAINTAINERS +0
-0ppc4xx L: [email protected] S: Orphan[...]
Quoted 6 lines
qapi/ghes-cper.json new file +0
-0qapi/ghes-cper.json line 10
Quoted 10 lines
qapi/ghes-cper.json new file +10
-0@@ -0,0 +1,55 @@ +# -*- Mode: Python -*- +# vim: filetype=python + +## +# = GHESv2 CPER Error Injection +# +# These are defined at +# ACPI 6.2: 18.3.2.8 Generic Hardware Error Source version 2 +# (GHESv2 - Type 10) +##Feels a bit terse. These what?
Quoted 6 lines
Quoted 3 lines
The reference could be clearer: "defined in the ACPI Specification 6.2, section 18.3.2.8 Generic Hardware Error Source version 2". A link would be nice, if it's stable.
I can add a link, but only newer ACPI versions are hosted in html format (e. g. only versions 6.4 and 6.5 are available as html at uefi.org).
some years earlier it could be said 'stable link' about acpi spec hosted elsewhere. Not the case anymore after umbrella change.
Quoted 6 lines
Quoted 3 lines
spec name, rev, chapter worked fine for acpi code (it's easy to find wherever spec is hosted). Probably the same would work for QAPI, I'm not QAPI maintainer though,
so preffered approach here is absolutely up to you.A link is strictly optional. Stable links are nice, stale links are annoying. Mauro, you decide :)
Well, I guess I'll add a link then, keeping it in text mode as well.
Changing umbrella is something that doesn't happen too often. Hopefully those will stay for a long time, if not forever, under uefi.org.
If not, we can always drop the link.
Thanks,
Mauro
Re: [PATCH v5 7/7] scripts/ghes_inject: add a script to generate GHES error inject
In reply to Mauro Carvalho ChehabQuoted 32 lines · Mauro Carvalho Chehab
Em Thu, 8 Aug 2024 19:33:32 -0400
John Snow <[email protected]> escreveu:Quoted 1 line
Quoted 1 line
Quoted 1 line
Then here you'd use qmp.cmd (raises exception on QMPError) or
qmp.cmd_raw
Quoted 1 line
Quoted 1 line
Quoted 1 line
or qmp.cmd_obj (returns the QMP response as the return value even if
it
Quoted 7 lines
Quoted 5 lines
was
Quoted 1 line
an error.)
Good to know, I'll try and see what fits best.
I might *suggest* you try to use the exception-raising interface and
catch
Quoted 3 lines
exceptions to interrogate expected errors as it aligns better with the "idiomatic python API" - I have no plans to support an external API that *returns* error objects except via the exception class. This approach
will
Quoted 1 line
be easier to port when I drop the legacy interface in the future, see
below.
Quoted 3 lines
But, that said, whichever is easiest. We use all three interfaces in many places in the QEMU tree. I have no grounds to require you to use a
specific
Quoted 1 line
one ;)
While a python-style exception handling is cool, I ended opting to use
cmd_obj(), as the script needs to catch the end of /machine/unattached/device[]
array, and usingcmd_obj()made the conversion easier.
Quoted 8 lines
One of the things I missed at the documentation is a description of the possible exceptions that
cmd()could raise.It is probably worth documenting it and placing them on a QMP-specific error class, but a change like that would probably be incompatible with the existing applications. Probably something to be considered on your TODO list to move this from legacy ;-)
Good feedback, thanks! I definitely didn't spend much time polishing the "legacy" interface. I clearly thought it'd be more temporary than it became ;)
I owe the package some updates for 3.13, I'll improve the documentation and also consider adding some "you forgot to make the address a tuple" protection so that part is less of a trap. (Without the tuple, I think it likely used the address as a socket path and the port as a bool to enter server mode. mypy would catch this, but it's a design goal to not require or expect script writers to need such things.)
Thank you! :)
Quoted 3 lines
Anyway, I already folded the changes at the branch I'll be using as basis for the next submission (be careful to use it, as I'm always rebasing it):
Great, I'll review the entire script more thoroughly on v2, if that's OK with you.
Just got back from a long PTO and an illness and I'm still ramping back up and handling backlog.
Quoted 7 lines
Thanks,
Mauro
~~js
Quoted 1 line
Re: [PATCH v5 6/7] acpi/ghes: add support for generic error injection via QAPI
In reply to Mauro Carvalho ChehabQuoted 269 lines · On Thu, 8 Aug 2024 20:19:03 +0200 Mauro Carvalho Chehab…
Em Thu, 8 Aug 2024 10:11:07 +0200
Igor Mammedov <[email protected]> escreveu:Quoted 183 lines
Quoted 168 lines · On Wed, 7 Aug 2024 15:25:47 +0100 Jonathan Cameron…
Quoted 157 lines · On Tue, 6 Aug 2024 16:31:13 +0200 Igor Mammedov <[email protected]> wrote:
Quoted 24 lines · On Fri, 2 Aug 2024 23:44:01 +0200 Mauro Carvalho Chehab…
Provide a generic interface for error injection via GHESv2.
This patch is co-authored:
- original ghes logic to inject a simple ARM record by Shiju Jose;
- generic logic to handle block addresses by Jonathan Cameron;
- generic GHESv2 error inject by Mauro Carvalho Chehab;Co-authored-by Jonathan Cameron <[email protected]>Co-authored-by Shiju Jose <[email protected]>Co-authored-by Mauro Carvalho Chehab <[email protected]>Cc Jonathan Cameron <[email protected]>Cc Shiju Jose <[email protected]>Signed-off-by Mauro Carvalho Chehab <[email protected]>--- hw/acpi/ghes.c | 159 ++++++++++++++++++++++++++++++++++++++--- hw/acpi/ghes_cper.c | 2 +- include/hw/acpi/ghes.h | 3 + 3 files changed, 152 insertions(+), 12 deletions(-)hw/acpi/ghes.c +0
-0hw/acpi/ghes.c void acpi_ghes_add_fw_cfg(AcpiGhesState *ags, FWCfgState *s, · line 398
Quoted 4 lines
hw/acpi/ghes.c +1
-0@@ -395,23 +395,22 @@ void acpi_ghes_add_fw_cfg(AcpiGhesState *ags, FWCfgState *s, ags->present = true; } +static uint64_t ghes_get_state_start_address (void )
ghes_get_hardware_errors_address()might better reflect what address it will returnQuoted 18 lines
hw/acpi/ghes.c +9
-4+{ +AcpiGedState *acpi_ged_state = +ACPI_GED (object_resolve_path_type ("" ,TYPE_ACPI_GED ,NULL )); +AcpiGhesState *ags = &acpi_ged_state->ghes_state; + +return le64_to_cpu (ags->ghes_addr_le); +} +int acpi_ghes_record_errors (uint8_t source_id,uint64_t physical_address) {uint64_t error_block_addr, read_ack_register_addr, read_ack_register =0 ; -uint64_t start_addr; +uint64_t start_addr =ghes_get_state_start_address ();bool ret =-1 ; -AcpiGedState *acpi_ged_state; -AcpiGhesState *ags; -assert (source_id <ACPI_HEST_SRC_ID_RESERVED );hw/acpi/ghes.c void acpi_ghes_add_fw_cfg(AcpiGhesState *ags, FWCfgState *s, · line 415
Quoted 10 lines
hw/acpi/ghes.c +0
-7- acpi_ged_state =ACPI_GED (object_resolve_path_type ("" ,TYPE_ACPI_GED , -NULL )); -g_assert (acpi_ged_state); - ags = &acpi_ged_state->ghes_state; - - start_addr =le64_to_cpu (ags->ghes_addr_le); -if (physical_address) { start_addr += source_id *sizeof (uint64_t );above should be a separate patch
Quoted 26 lines
hw/acpi/ghes.c +21
-0@@ -448,9 +447,147 @@ int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address)return ret; } +/* +* Error register block data layout +* +* | +---------------------+ ges.ghes_addr_le +* | |error_block_address0 | +* | +---------------------+ +* | |error_block_address1 | +* | +---------------------+ --+-- +* | | ............. | GHES_ADDRESS_SIZE +* | +---------------------+ --+-- +* | |error_block_addressN | +* | +---------------------+ +* | | read_ack0 | +* | +---------------------+ --+-- +* | | read_ack1 | GHES_ADDRESS_SIZE +* | +---------------------+ --+-- +* | | ............. | +* | +---------------------+ +* | | read_ackN | +* | +---------------------+ --+-- +* | | CPER | | hw/acpi/ghes.c int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address) · line 480
Quoted 10 lines
hw/acpi/ghes.c +10
-0+* | | .... | GHES_MAX_RAW_DATA_LENGT +* | | CPER | | +* | +---------------------+ --+-- +* | | .......... | +* | +---------------------+ +* | | CPER | +* | | .... | +* | | CPER | +* | +---------------------+ +*/ no need to duplicate
docs/specs/acpi_hest_ghes.rst,
I'd just reffer to it and maybe add short comment as to why it's mentioned.Quoted 22 lines
hw/acpi/ghes.c +22
-0+/* Map from uint32_t notify to entry offset in GHES */ +static const uint8_t error_source_to_index[] = {0xff ,0xff ,0xff ,0xff , +0xff ,0xff ,0xff ,1 ,0 }; + +static bool ghes_get_addr (uint32_t notify,uint64_t *error_block_addr, +uint64_t *read_ack_addr) +{ +uint64_t base; + +if (notify >=ACPI_GHES_NOTIFY_RESERVED ) { +return false; + } + +/* Find and check the source id for this new CPER */ +if (error_source_to_index[notify] ==0xff ) { +return false; + } + + base =ghes_get_state_start_address (); + + *read_ack_addr = base + + ACPI_GHES_ERROR_SOURCE_COUNT * sizeof(uint64_t) +hw/acpi/ghes.c int acpi_ghes_record_errors(uint8_t source_id, uint64_t physical_address) · line 513
Quoted 10 lines
hw/acpi/ghes.c +10
-0+ error_source_to_index[notify] *sizeof (uint64_t ); + +/* Could also be read back from the error_block_address register */ + *error_block_addr = base + +ACPI_GHES_ERROR_SOURCE_COUNT *sizeof (uint64_t ) + +ACPI_GHES_ERROR_SOURCE_COUNT *sizeof (uint64_t ) + + error_source_to_index[notify] *ACPI_GHES_MAX_RAW_DATA_LENGTH ; + +return true; +}I don't like all this pointer math, which is basically a reverse engineered QEMU actions on startup + guest provided etc/hardware_errors address.
For once, it assumes error_source_to_index[] matches order in which HEST error sources were described, which is fragile.
2nd: migration-wive it's disaster, since old/new HEST/hardware_errors tables in RAM migrated from older version might not match above assumptions of target QEMU.
I see 2 ways to rectify it:
1st: preferred/cleanest would be to tell QEMU (viafw_cfg) address of HEST table
in guest RAM, like we do with etc/hardware_errors, see
build_ghes_error_table()
...
tell firmware to writehardware_errorsGPA into
and then fetch from HEST table in RAM, the guest patched error/ack addresses for givensource_idQuoted 7 lines
code-wise: relatively simple once one wraps their own head over
how this whole APEI thing works in QEMU
workflow is described indocs/specs/acpi_hest_ghes.rstlook to me as sufficient to grasp it.
(but my view is very biased given my prior knowledge,
aka: docs/comments/examples wrt acpi patching are good enough)
(if it's not clear how to do it, ask me for pointers)Quoted 4 lines
Hi Igor, I think I follow what you mean but maybe this question will reveal otherwise. HEST is currently in
ACPI_BUILD_TABLE_FILE.
Would you suggest splitting it to it's own file, or usingtable_offsetsto get the offset inACPI_BUILD_TABLE_FILEGPA?yep, offset taken right before HEST is to be created
doc comment forbios_linker_loader_write_pointer()explains how it workswe need something like:
bios_linker_loader_write_pointer(linker, ACPI_HEST_TABLE_ADDR_FW_CFG_FILE, 0, sizeof(uint64_t), ACPI_BUILD_TABLE_FILE, hest_offset_within_ACPI_BUILD_TABLE_FILE);Quoted 6 lines
to register new file see:
a08a64627ACPI: Record the Generic Error Status Block address and to avoid copy past error maybe
136fc6aa2ACPI: Avoid infinite recursion when dump-vmstat
for this needs to be limited to new machine types and keep
old ones without this new feature. (I'd usehw_compat_machinery for that)Not sure if I got it. The code, after this patch from my v6:
https://lore.kernel.org/qemu-devel/5710c364d7ef6cdab6b2f1e127ef191bdf84e8c2.1723119423.git.mchehab+huawei@kernel.org/T/#uAlready stores two of the three address offsets via
bios_linker_loader_add_pointer(), e. g. it is similar to the code below (I simplified the code to make the example clearer):<snip>
/* Fromhw/arm/virt-acpi-build.c*/
static
voidvirt_acpi_build(VirtMachineState *vms, AcpiBuildTables *tables){ ... if (vms->ras) { build_ghes_error_table(tables->hardware_errors, tables->linker); acpi_add_table(table_offsets, tables_blob); /* internally, call build_ghes_v2() for SEA and GED notification sources */ acpi_build_hest(tables_blob, tables->linker, vms->oem_id, vms->oem_table_id); } ... }/* From
hw/acpi/ghes.c*/
static void build_ghes_v2(GArray*table_data,
enum AcpiGhesNotifyType notify, BIOSLinker *linker){ uint64_t address_offset, ack_offset, block_addr_offset, cper_offset; enum AcpiHestSourceId source_id; /* * Get offsets for either SEA or GED notification - easy to extend * to all mechanisms like MCE and SCI to better support x86 */ assert(!acpi_hest_address_offset(notify, &block_addr_offset, &ack_offset, &cper_offset, &source_id)); bios_linker_loader_add_pointer(linker, ACPI_BUILD_TABLE_FILE, address_offset + GAS_ADDR_OFFSET, sizeof(uint64_t), ACPI_GHES_ERRORS_FW_CFG_FILE, block_addr_offset); bios_linker_loader_add_pointer(linker, ACPI_BUILD_TABLE_FILE, address_offset + GAS_ADDR_OFFSET, sizeof(uint64_t), ACPI_GHES_ERRORS_FW_CFG_FILE, ack_offset); /* Current code ignores &cper_offset when creating HEST */ }void ghes_record_cper_errors(AcpiGhesCper *cper, Error **errp,
enum AcpiGhesNotifyType notify)
{
uint64_tcper_addr,read_ack_start_addr;assert(!ghes_get_hardware_errors_address(notify, NULL,
&read_ack_start_addr,
&cper_addr, NULL));/*
* Use cpu_physical_memory_read/write() to
* - read/store atread_ack_start_addr
* - Write cper block GArray atcper_addr
*/
}
</snip>We may also store
cper_offsetthere viabios_linker_loader_add_pointer()and/or usebios_linker_loader_write_pointer(), but I can't see how the data stored there can be retrieved, nor any advantage of using it instead of the current code, as, in the end, we'll have 3 addresses that will be used:
Quoted 8 lines
- an address where a pointer to CPER record will be stored;
- an address where the ack will be stored;
- an address where the actual CPER record will be stored.And those are calculated on a single function and are all stored at the ACPI table files.
What am I missing?
That's basically (2) approach and it works to some degree, unfortunately it's fragile when we start talking about migration and changing layout in the future.
Lets take as example increasing size of 1) 'Generic Error Status Block', we are considering. Old QEMU will, tell firmware to allocate 1K buffer for it and calculated offsets to [1] (that you've stored/calculated) will include this assumption.
Then in newer we QEMU increase size of [1] and all hardcoded offsets will account for new size, but if we migrate guest from old QEMU to this newer one all HEST tables layout within guest will match old QEMU assumptions, and as result newer QEMU with larger block size will write CPERs at wrong address considering we are still running guest from old QEMU. That's just one example.
To make it work there a number of ways, but the ultimate goal is to pick one that's the least fragile and won't snowball in maintenance nightmare as number of GHES sources increases over time.
This series tries to solve problem of mapping GHES source to a corresponding 'Generic Error Status Block' and related registers. However we are missing access to this mapping since it only exists in guest patched HEST (i.e in guest RAM only).
The robust way to make it work would be for QEMU to get a pointer to whole HEST table and then enumerate GHES sources and related error/ack registers directly from guest RAM (sidestepping layout change issues this way).
what I'm proposing is to use bios_linker_loader_write_pointer() (only once) so that firmware could tell QEMU address of HEST table, in which one can find a GHES source and always correct error/ack pointers (regardless of table[s] layout changes).
Quoted 3 lines
Thanks,
Mauro
Re: [PATCH v5 6/7] acpi/ghes: add support for generic error injection via QAPI
Em Mon, 12 Aug 2024 11:39:00 +0200
Igor Mammedov <[email protected]> escreveu:
Quoted 44 lines
Quoted 6 lines
We may also store
cper_offsetthere viabios_linker_loader_add_pointer()and/or usebios_linker_loader_write_pointer(), but I can't see how the data stored there can be retrieved, nor any advantage of using it instead of the current code, as, in the end, we'll have 3 addresses that will be used:Quoted 8 lines
- an address where a pointer to CPER record will be stored;
- an address where the ack will be stored;
- an address where the actual CPER record will be stored.And those are calculated on a single function and are all stored at the ACPI table files.
What am I missing?
That's basically (2) approach and it works to some degree, unfortunately it's fragile when we start talking about migration and changing layout in the future.
Lets take as example increasing size of 1) 'Generic Error Status Block', we are considering. Old QEMU will, tell firmware to allocate 1K buffer for it and calculated offsets to [1] (that you've stored/calculated) will include this assumption.
Then in newer we QEMU increase size of [1] and all hardcoded offsets will account for new size, but if we migrate guest from old QEMU to this newer one all HEST tables layout within guest will match old QEMU assumptions, and as result newer QEMU with larger block size will write CPERs at wrong address considering we are still running guest from old QEMU. That's just one example.To make it work there a number of ways, but the ultimate goal is to pick one that's the least fragile and won't snowball in maintenance nightmare as number of GHES sources increases over time.
This series tries to solve problem of mapping GHES source to a corresponding 'Generic Error Status Block' and related registers. However we are missing access to this mapping since it only exists in guest patched HEST (i.e in guest RAM only).
The robust way to make it work would be for QEMU to get a pointer to whole HEST table and then enumerate GHES sources and related error/ack registers directly from guest RAM (sidestepping layout change issues this way).
Quoted 4 lines
what I'm proposing is to use
bios_linker_loader_write_pointer()(only once) so that firmware could tell QEMU address of HEST table, in which one can find a GHES source and always correct error/ack pointers (regardless of table[s] layout changes).
Ok, got it. Such change was not easy, but I finally figured out how to make it actually work.
I'll address tomorrow your comment on patch 5/10 about using raw data also for the other parts of CPER (generic error status and generic error data).
If you want to do a sneak peak, I'm keeping the latest development version here:
https://gitlab.com/mchehab_kernel/qemu/-/commits/qemu_submission?ref_type=heads
In particular, the patch changing from /etc/hardware_errors offset to a HEST offset is at:
https://gitlab.com/mchehab_kernel/qemu/-/commit/9197d22de09df97ce3d6725cb21bd2114c2eb43c
It contains several cleanups to make the logic clearer and more robust.
Thanks,
Mauro