mbox series

[RFC,v2,0/3] Make ELOG log and trace consistently with GHES

Message ID 20240510112740.667445-1-fabio.m.de.francesco@linux.intel.com
Headers show
Series Make ELOG log and trace consistently with GHES | expand

Message

Fabio M. De Francesco May 10, 2024, 11:21 a.m. UTC 
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 two similar paths, ELOG and 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.

This short series wants to make these two paths act similarly for what
relates to logging and tracing.

--- Changes in 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 (3):
  ACPI: extlog: Trace CPER Non-standard Section Body
  ACPI: extlog: Trace CPER PCI Express Error Section
  ACPI: extlog: Make print_extlog_rcd() log unconditionally

 drivers/acpi/acpi_extlog.c | 47 ++++++++++++++++++++++++++++++++++----
 drivers/ras/debugfs.c      |  6 -----
 include/linux/ras.h        |  2 --
 3 files changed, 42 insertions(+), 13 deletions(-)