From: Breno Leitao <leitao@debian.org>
To: akpm@linux-foundation.org, bhe@redhat.com
Cc: linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-acpi@vger.kernel.org, dyoung@redhat.com,
tony.luck@intel.com, xueshuai@linux.alibaba.com,
vgoyal@redhat.com, zhiquan1.li@intel.com, olja@meta.com,
Breno Leitao <leitao@debian.org>,
kernel-team@meta.com
Subject: [PATCH v2 2/2] docs: add ABI documentation for /sys/kernel/hwerr_recovery_stats/
Date: Mon, 02 Feb 2026 06:27:40 -0800 [thread overview]
Message-ID: <20260202-vmcoreinfo_sysfs-v2-2-8f3b5308b894@debian.org> (raw)
In-Reply-To: <20260202-vmcoreinfo_sysfs-v2-0-8f3b5308b894@debian.org>
Document the new hwerr_recovery_stats sysfs directory that exposes
hardware error recovery statistics.
Update hw-recoverable-errors.rst to reference the new sysfs interface
for runtime monitoring.
Signed-off-by: Breno Leitao <leitao@debian.org>
---
.../ABI/testing/sysfs-kernel-hwerr_recovery_stats | 47 ++++++++++++++++++++++
Documentation/driver-api/hw-recoverable-errors.rst | 3 +-
2 files changed, 49 insertions(+), 1 deletion(-)
diff --git a/Documentation/ABI/testing/sysfs-kernel-hwerr_recovery_stats b/Documentation/ABI/testing/sysfs-kernel-hwerr_recovery_stats
new file mode 100644
index 0000000000000..4cb9f5a89fba9
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-kernel-hwerr_recovery_stats
@@ -0,0 +1,47 @@
+What: /sys/kernel/hwerr_recovery_stats/
+Date: February 2026
+KernelVersion: 6.20
+Contact: Breno Leitao <leitao@debian.org>
+Description:
+ Directory containing hardware error recovery statistics.
+ These statistics track recoverable hardware errors that the
+ kernel has handled since boot.
+
+ Each file contains a single integer representing the count
+ of recovered errors for that subsystem.
+
+What: /sys/kernel/hwerr_recovery_stats/cpu
+Date: February 2026
+KernelVersion: 6.20
+Contact: Breno Leitao <leitao@debian.org>
+Description:
+ Count of CPU-related recovered errors (MCE, ARM processor
+ errors).
+
+What: /sys/kernel/hwerr_recovery_stats/memory
+Date: February 2026
+KernelVersion: 6.20
+Contact: Breno Leitao <leitao@debian.org>
+Description:
+ Count of memory-related recovered errors.
+
+What: /sys/kernel/hwerr_recovery_stats/pci
+Date: February 2026
+KernelVersion: 6.20
+Contact: Breno Leitao <leitao@debian.org>
+Description:
+ Count of PCI/PCIe AER non-fatal recovered errors.
+
+What: /sys/kernel/hwerr_recovery_stats/cxl
+Date: February 2026
+KernelVersion: 6.20
+Contact: Breno Leitao <leitao@debian.org>
+Description:
+ Count of CXL (Compute Express Link) recovered errors.
+
+What: /sys/kernel/hwerr_recovery_stats/others
+Date: February 2026
+KernelVersion: 6.20
+Contact: Breno Leitao <leitao@debian.org>
+Description:
+ Count of other hardware recovered errors.
diff --git a/Documentation/driver-api/hw-recoverable-errors.rst b/Documentation/driver-api/hw-recoverable-errors.rst
index fc526c3454bd7..4aefcd103be22 100644
--- a/Documentation/driver-api/hw-recoverable-errors.rst
+++ b/Documentation/driver-api/hw-recoverable-errors.rst
@@ -36,7 +36,8 @@ Data Exposure and Consumption
types like CPU, memory, PCI, CXL, and others.
- It is exposed via vmcoreinfo crash dump notes and can be read using tools
like `crash`, `drgn`, or other kernel crash analysis utilities.
-- There is no other way to read these data other than from crash dumps.
+- It is also exposed via sysfs at ``/sys/kernel/hwerr_recovery_stats/`` for runtime
+ monitoring without requiring a crash dump.
- These errors are divided by area, which includes CPU, Memory, PCI, CXL and
others.
--
2.47.3
next prev parent reply other threads:[~2026-02-02 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 14:27 [PATCH v2 0/2] vmcoreinfo: Expose hardware error recovery statistics via sysfs Breno Leitao
2026-02-02 14:27 ` [PATCH v2 1/2] vmcoreinfo: expose " Breno Leitao
2026-02-11 2:01 ` Baoquan He
2026-02-02 14:27 ` Breno Leitao [this message]
2026-02-10 9:11 ` [PATCH v2 0/2] vmcoreinfo: Expose " Breno Leitao
2026-02-10 18:46 ` Andrew Morton
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=20260202-vmcoreinfo_sysfs-v2-2-8f3b5308b894@debian.org \
--to=leitao@debian.org \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=kernel-team@meta.com \
--cc=kexec@lists.infradead.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olja@meta.com \
--cc=tony.luck@intel.com \
--cc=vgoyal@redhat.com \
--cc=xueshuai@linux.alibaba.com \
--cc=zhiquan1.li@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