Linux ACPI
 help / color / mirror / Atom feed
From: "Fabio M. De Francesco" <fabio.m.de.francesco@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
	Len Brown <lenb@kernel.org>,
	Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
	Oliver O'Halloran <oohall@gmail.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, linux-pci@vger.kernel.org,
	Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH 0/2] Make ELOG log and trace consistently with GHES
Date: Tue, 23 Jul 2024 15:43:45 +0200	[thread overview]
Message-ID: <2737053.vuYhMxLoTh@fdefranc-mobl3> (raw)
In-Reply-To: <20240527144356.246220-1-fabio.m.de.francesco@linux.intel.com>

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(-)
> 
> 





      parent reply	other threads:[~2024-07-23 13:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-27 14:43 [PATCH 0/2] Make ELOG log and trace consistently with GHES Fabio M. De Francesco
2024-05-27 14:43 ` [PATCH 1/2] ACPI: extlog: Trace CPER Non-standard Section Body Fabio M. De Francesco
2024-08-06 19:21   ` Dan Williams
2024-08-06 21:07   ` Bjorn Helgaas
2024-05-27 14:43 ` [PATCH 2/2] ACPI: extlog: Trace CPER PCI Express Error Section Fabio M. De Francesco
2024-08-06 19:56   ` Dan Williams
2024-10-23 13:35     ` Fabio M. De Francesco
2024-12-11  1:51       ` Dan Williams
2024-08-06 21:31   ` Bjorn Helgaas
2024-08-07 20:28     ` Dan Williams
2024-08-07 20:31       ` Dan Williams
2024-07-23 13:43 ` Fabio M. De Francesco [this message]

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=2737053.vuYhMxLoTh@fdefranc-mobl3 \
    --to=fabio.m.de.francesco@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=dan.j.williams@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@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 \
    /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