From: "Fabio M. De Francesco" <fabio.m.de.francesco@linux.intel.com>
To: "Rafael J . Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Dave Jiang <dave.jiang@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
Oliver O'Halloran <oohall@gmail.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Tony Luck <tony.luck@intel.com>, Borislav Petkov <bp@alien8.de>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-cxl@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-pci@vger.kernel.org, linux-edac@vger.kernel.org
Cc: "Fabio M. De Francesco" <fabio.m.de.francesco@linux.intel.com>
Subject: [PATCH 0/4 v2] Make ELOG log and trace consistently with GHES
Date: Tue, 29 Apr 2025 19:21:05 +0200 [thread overview]
Message-ID: <20250429172109.3199192-1-fabio.m.de.francesco@linux.intel.com> (raw)
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 v2 ---
- Add a patch to pass log levels to pci_print_aer() (Dan)
- Add a patch to trace CPER CXL Protocol Errors
- Rework commit messages (Dan)
- Use log_non_standard_event() (Bjorn)
--- 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 (4):
ACPI: extlog: Trace CPER Non-standard Section Body
PCI/AER: Modify pci_print_aer() to take log level
ACPI: extlog: Trace CPER PCI Express Error Section
ACPI: extlog: Trace CPER CXL Protocol Errors
drivers/acpi/acpi_extlog.c | 96 ++++++++++++++++++++++++++++++++++++++
drivers/cxl/core/pci.c | 2 +-
drivers/cxl/core/ras.c | 6 +++
drivers/pci/pcie/aer.c | 18 +++----
drivers/ras/ras.c | 1 +
include/cxl/event.h | 2 +
include/linux/aer.h | 13 +++++-
7 files changed, 126 insertions(+), 12 deletions(-)
--
2.48.1
next reply other threads:[~2025-04-29 17:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 17:21 Fabio M. De Francesco [this message]
2025-04-29 17:21 ` [PATCH 1/4 v2] ACPI: extlog: Trace CPER Non-standard Section Body Fabio M. De Francesco
2025-05-20 11:08 ` Jonathan Cameron
2025-04-29 17:21 ` [PATCH 2/4 v2] PCI/AER: Modify pci_print_aer() to take log level Fabio M. De Francesco
2025-05-20 11:10 ` Jonathan Cameron
2025-04-29 17:21 ` [PATCH 3/4 v2] ACPI: extlog: Trace CPER PCI Express Error Section Fabio M. De Francesco
2025-04-29 18:02 ` Yazen Ghannam
2025-06-02 16:59 ` Fabio M. De Francesco
2025-04-29 17:21 ` [PATCH 4/4 v2] ACPI: extlog: Trace CPER CXL Protocol Errors Fabio M. De Francesco
2025-04-29 18:20 ` Yazen Ghannam
2025-06-02 18:06 ` Fabio M. De Francesco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250429172109.3199192-1-fabio.m.de.francesco@linux.intel.com \
--to=fabio.m.de.francesco@linux.intel.com \
--cc=alison.schofield@intel.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=oohall@gmail.com \
--cc=rafael@kernel.org \
--cc=tony.luck@intel.com \
--cc=vishal.l.verma@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).