From: Lukas Wunner <lukas@wunner.de>
To: Bjorn Helgaas <helgaas@kernel.org>,
Raag Jadav <raag.jadav@intel.com>,
linux-pci@vger.kernel.org
Cc: Sourabh Jain <sourabhjain@linux.ibm.com>,
Oliver OHalloran <oohall@gmail.com>,
linuxppc-dev@lists.ozlabs.org,
Aravind Iddamsetty <aravind.iddamsetty@intel.com>,
Srinivasa Adatrao <srinivasa.adatrao@intel.com>,
Sathyanarayanan Kuppuswamy
<sathyanarayanan.kuppuswamy@linux.intel.com>,
Terry Bowman <terry.bowman@amd.com>,
Keith Busch <kbusch@kernel.org>,
Maciej Grochowski <Maciej.Grochowski@sony.com>,
Yazen Ghannam <yazen.ghannam@amd.com>,
Darshit Shah <darnshah@amazon.de>,
Jason Perlow <jperlow@gmail.com>,
Riana Tauro <riana.tauro@intel.com>,
Yury Murashka <yurypm@arista.com>,
"Matthew W Carlis" <mattc@purestorage.com>
Subject: [PATCH v2 0/7] Error reporting for AER-incapable devices
Date: Wed, 18 Nov 2026 11:40:00 +0100 [thread overview]
Message-ID: <cover.1794997749.git.lukas@wunner.de> (raw)
Bjorn suggests "the PCI core should do pci_enable_pcie_error_reporting()
independent of whether the device has an AER Capability":
https://lore.kernel.org/r/20260826212619.GA1566339@bhelgaas/
This is done in patch [7/7]. The preceding patches contain prep work.
For context, PCIe r7.1 sec 6.2.1 defines two error reporting paradigms:
AER and baseline capability. The latter relies (solely) on the error
enable/status bits in the Device Control and Device Status registers,
which exist on every PCIe device. The kernel has supported the AER
paradigm for 20 years. With the present series, it gains support for
the baseline capability paradigm.
Patches [1/7] and [2/7] reinstate DPC on AER-incapable Downstream Ports.
The kernel used to support this until 2018. It is hereby fixed because
it eases introduction of baseline capability error reporting in the
subsequent patches.
Changes v1 -> v2:
* Patch [1/7]:
* On AER-capable devices, infer severity from AER Extended Capability
instead of Device Status register because the latter also logs masked
errors (Sathya).
* Fix storytelling in commit message because 4e5fad429bd1 changed
behavior, not 708b20003624 (Sathya).
* Patch [3/7]:
* New patch to clear error status bits more selectively (sashiko).
* Patch [4/7]:
* Clear Fatal Errors as well on recovery failure (Sathya, sashiko).
* Patch [6/7]:
* Amend kernel-doc of pci_aer_unmask_internal_errors() (Sathya).
* Patch [7/7]:
* Convert AER severity to Device Status bit with new severity2devsta[]
array, instead of renumbering AER severity (sashiko).
* On entry of aer_get_device_error_info(), clear info->mask and
info->first_error (Sathya, sashiko).
* Emit "(no details available)" message for AER-incapable devices
as well as for devices whose AER registers are deliberately not
read on Fatal Errors (Sathya).
* Amend commit message to inform that System Errors may be raised
by AER-incapable devices if they have no AER- or DPC-capable
port in their ancestry (Sathya).
Link to v1:
https://lore.kernel.org/r/cover.1790531238.git.lukas@wunner.de/
Lukas Wunner (6):
PCI/DPC: Avoid access to non-existent AER capability
PCI/DPC: Reinstate support for AER-incapable ports
PCI/ERR: Clear error status bits more selectively
PCI/AER: Drop AER native check from handles_cxl_errors()
PCI/AER: Move AER capability check out of pcie_aer_is_native()
PCI/AER: Enable baseline capability error reporting
Yury Murashka (1):
PCI/ERR: Avoid stale error status bits on recovery failure
.../ABI/testing/sysfs-bus-pci-devices-aer | 26 +++++--
Documentation/PCI/pcieaer-howto.rst | 9 +--
drivers/pci/pcie/aer.c | 76 +++++++++++++------
drivers/pci/pcie/aer_cxl_rch.c | 3 +-
drivers/pci/pcie/dpc.c | 46 +++++++----
drivers/pci/pcie/err.c | 14 +++-
6 files changed, 120 insertions(+), 54 deletions(-)
base-commit: 6d69eeae8966bc3bea0facbd550f45ef9de41cc4
--
2.53.0
next reply other threads:[~2026-11-18 10:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 10:40 Lukas Wunner [this message]
2026-11-18 10:40 ` [PATCH v2 1/7] PCI/DPC: Avoid access to non-existent AER capability Lukas Wunner
2026-11-18 11:04 ` sashiko-bot
2026-11-18 10:40 ` [PATCH v2 2/7] PCI/DPC: Reinstate support for AER-incapable ports Lukas Wunner
2026-11-18 11:03 ` sashiko-bot
2026-11-18 10:40 ` [PATCH v2 3/7] PCI/ERR: Clear error status bits more selectively Lukas Wunner
2026-11-18 10:40 ` [PATCH v2 4/7] PCI/ERR: Avoid stale error status bits on recovery failure Lukas Wunner
2026-11-18 10:40 ` [PATCH v2 5/7] PCI/AER: Drop AER native check from handles_cxl_errors() Lukas Wunner
2026-11-18 11:02 ` sashiko-bot
2026-11-18 10:40 ` [PATCH v2 6/7] PCI/AER: Move AER capability check out of pcie_aer_is_native() Lukas Wunner
2026-11-18 10:40 ` [PATCH v2 7/7] PCI/AER: Enable baseline capability error reporting Lukas Wunner
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=cover.1794997749.git.lukas@wunner.de \
--to=lukas@wunner.de \
--cc=Maciej.Grochowski@sony.com \
--cc=aravind.iddamsetty@intel.com \
--cc=darnshah@amazon.de \
--cc=helgaas@kernel.org \
--cc=jperlow@gmail.com \
--cc=kbusch@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mattc@purestorage.com \
--cc=oohall@gmail.com \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@intel.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=sourabhjain@linux.ibm.com \
--cc=srinivasa.adatrao@intel.com \
--cc=terry.bowman@amd.com \
--cc=yazen.ghannam@amd.com \
--cc=yurypm@arista.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