| Message ID | 20240527144356.246220-1-fabio.m.de.francesco@linux.intel.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | Make ELOG log and trace consistently with GHES | expand |
On Monday, May 27, 2024 4:43:39 PM GMT+2 Fabio M. De Francesco wrote: > When Firmware First is enabled, BIOS handles errors first and then it > makes them available to the kernel via the Common Platform Error Record > (CPER) sections (UEFI 2.10 Appendix N). Linux parses the CPER sections > via one of two similar paths, either ELOG or GHES. > > Currently, ELOG and GHES show some inconsistencies in how they print to > the kernel log as well as in how they report to userspace via trace > events. > > Make the two mentioned paths act similarly for what relates to logging > and tracing. Gentle ping. Thanks, Fabio > --- Changes for v1 --- > > - Drop the RFC prefix and restart from PATCH v1 > - Drop patch 3/3 because a discussion on it has not yet been > settled > - Drop namespacing in export of pci_print_aer while() (Dan) > - Don't use '#ifdef' in *.c files (Dan) > - Drop a reference on pdev after operation is complete (Dan) > - Don't log an error message if pdev is NULL (Dan) > > --- Changes for RFC v2 --- > > - 0/3: rework the subject line and the letter. > - 1/3: no changes. > - 2/3: trace CPER PCIe Section only if CONFIG_ACPI_APEI_PCIEAER > is defined; the kernel test robot reported the use of two > undefined symbols because the test for the config option was > missing; rewrite the subject line and part of commit message. > - 3/3: no changes. > > Fabio M. De Francesco (2): > ACPI: extlog: Trace CPER Non-standard Section Body > ACPI: extlog: Trace CPER PCI Express Error Section > > drivers/acpi/acpi_extlog.c | 35 +++++++++++++++++++++++++++++++++++ > drivers/pci/pcie/aer.c | 2 +- > include/linux/aer.h | 9 ++++++--- > 3 files changed, 42 insertions(+), 4 deletions(-) > >
When Firmware First is enabled, BIOS handles errors first and then it makes them available to the kernel via the Common Platform Error Record (CPER) sections (UEFI 2.10 Appendix N). Linux parses the CPER sections via one of two similar paths, either ELOG or GHES. Currently, ELOG and GHES show some inconsistencies in how they print to the kernel log as well as in how they report to userspace via trace events. Make the two mentioned paths act similarly for what relates to logging and tracing. --- Changes for v1 --- - Drop the RFC prefix and restart from PATCH v1 - Drop patch 3/3 because a discussion on it has not yet been settled - Drop namespacing in export of pci_print_aer while() (Dan) - Don't use '#ifdef' in *.c files (Dan) - Drop a reference on pdev after operation is complete (Dan) - Don't log an error message if pdev is NULL (Dan) --- Changes for RFC v2 --- - 0/3: rework the subject line and the letter. - 1/3: no changes. - 2/3: trace CPER PCIe Section only if CONFIG_ACPI_APEI_PCIEAER is defined; the kernel test robot reported the use of two undefined symbols because the test for the config option was missing; rewrite the subject line and part of commit message. - 3/3: no changes. Fabio M. De Francesco (2): ACPI: extlog: Trace CPER Non-standard Section Body ACPI: extlog: Trace CPER PCI Express Error Section drivers/acpi/acpi_extlog.c | 35 +++++++++++++++++++++++++++++++++++ drivers/pci/pcie/aer.c | 2 +- include/linux/aer.h | 9 ++++++--- 3 files changed, 42 insertions(+), 4 deletions(-)