From: "Fabio M. De Francesco" <fabio.m.de.francesco@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
"Fabio M . De Francesco" <fabio.m.de.francesco@linux.intel.com>
Subject: [RFC PATCH 0/3] ACPI: extlog: Log and trace similarly to GHES
Date: Tue, 7 May 2024 21:02:19 +0200 [thread overview]
Message-ID: <20240507190724.323269-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 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 competing path act similarly.
This is an RFC mainly because of patch 3/3 which enables kernel logging
even in precence of userspace monitoring events. I'm not sure if this
behavior is wanted.
Fabio M. De Francesco (3):
ACPI: extlog: Trace CPER Non-standard Section Body
ACPI: extlog: Trace PCI Express Error Section
ACPI: extlog: Make print_extlog_rcd() log unconditionally
drivers/acpi/acpi_extlog.c | 44 +++++++++++++++++++++++++++++++++-----
drivers/ras/debugfs.c | 6 ------
include/linux/ras.h | 2 --
3 files changed, 39 insertions(+), 13 deletions(-)
--
2.45.0
next reply other threads:[~2024-05-07 19:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 19:02 Fabio M. De Francesco [this message]
2024-05-07 19:02 ` [RFC PATCH 1/3] ACPI: extlog: Trace CPER Non-standard Section Body Fabio M. De Francesco
2024-05-07 19:02 ` [RFC PATCH 2/3] ACPI: extlog: Trace PCI Express Error Section Fabio M. De Francesco
2024-05-07 19:02 ` [RFC PATCH 3/3] ACPI: extlog: Make print_extlog_rcd() log unconditionally 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=20240507190724.323269-1-fabio.m.de.francesco@linux.intel.com \
--to=fabio.m.de.francesco@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).