drivers/acpi/apei

ACPI APEI Firmware-First Platform Error Reporting (GHES, EINJ)

ACPI's Platform Error Interface, including GHES (error source consumer) and EINJ (error injection), lets firmware on modern x86 and ARM servers forward hardware faults — memory errors, PCIe and CXL link issues, CPU machine checks — to Linux for logging and recovery. It underpins reliability features on current enterprise hardware including NVIDIA DGX and CXL servers.

keep conf=0.91 deploy=medium replacement=none subsystem=acpi category=firmware
91%

recommendation

It should stay because APEI is the standard mechanism modern servers use to deliver hardware error reports (memory, PCIe, CXL) from firmware to the OS, and it is actively maintained: fixes and new features were still landing in 2026, including a dedicated NVIDIA CPER handler for DGX/HGX systems. It is core RAS infrastructure with no replacement on the horizon.

repository signals

12 files
6,294 source lines
109 commits, 5y
+1,962 / −692 lines added / removed, 5y
53 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 109 total · active in 42/61 months
2021 2022 2023 2024 2025 2026 2021-04: 1 commit · +0 −1 2021-05: 1 commit · +1 −1 2021-06: 1 commit · +64 −17 2021-07: 0 commits · +0 −0 2021-08: 0 commits · +0 −0 2021-09: 0 commits · +0 −0 2021-10: 4 commits · +14 −11 2021-11: 0 commits · +0 −0 2021-12: 0 commits · +0 −0 2022-01: 0 commits · +0 −0 2022-02: 2 commits · +9 −12 2022-03: 3 commits · +10 −6 2022-04: 2 commits · +76 −7 2022-05: 0 commits · +0 −0 2022-06: 3 commits · +26 −9 2022-07: 0 commits · +0 −0 2022-08: 1 commit · +3 −0 2022-09: 2 commits · +3 −10 2022-10: 7 commits · +132 −62 2022-11: 2 commits · +1 −1 2022-12: 3 commits · +26 −32 2023-01: 1 commit · +4 −0 2023-02: 0 commits · +0 −0 2023-03: 2 commits · +13 −1 2023-04: 0 commits · +0 −0 2023-05: 3 commits · +3 −8 2023-06: 1 commit · +1 −1 2023-07: 1 commit · +37 −4 2023-08: 0 commits · +0 −0 2023-09: 1 commit · +22 −1 2023-10: 0 commits · +0 −0 2023-11: 3 commits · +59 −29 2023-12: 2 commits · +112 −6 2024-01: 1 commit · +0 −26 2024-02: 2 commits · +51 −63 2024-03: 4 commits · +258 −26 2024-04: 1 commit · +110 −0 2024-05: 2 commits · +1 −27 2024-06: 0 commits · +0 −0 2024-07: 0 commits · +0 −0 2024-08: 0 commits · +0 −0 2024-09: 3 commits · +3 −4 2024-10: 1 commit · +2 −2 2024-11: 1 commit · +2 −2 2024-12: 1 commit · +7 −7 2025-01: 2 commits · +59 −5 2025-02: 0 commits · +0 −0 2025-03: 2 commits · +60 −21 2025-04: 0 commits · +0 −0 2025-05: 5 commits · +18 −21 2025-06: 10 commits · +324 −83 2025-07: 4 commits · +68 −38 2025-08: 5 commits · +21 −23 2025-09: 3 commits · +45 −16 2025-10: 1 commit · +36 −0 2025-11: 2 commits · +41 −29 2025-12: 1 commit · +1 −1 2026-01: 9 commits · +230 −70 2026-02: 3 commits · +9 −9 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. lore.kernel.org

    APEI core code is still receiving upstream fixes in 2026 ('ACPI: APEI: check return value of task_work_add to prevent memory leaks').

  2. lore.kernel.org

    APEI/GHES is seeing new feature work in 2026, including a v3 series for a device-managed GHES notifier and NVIDIA CPER handler.

  3. docs.kernel.org

    Current kernel documentation still documents APEI/EINJ and references modern ACPI 6.5 CXL error injection support, showing the subsystem remains relevant to current server RAS flows.

  4. docs.nvidia.com

    NVIDIA maintains current DGX H100/H200 firmware documentation in 2026, supporting the inference that server platforms using firmware-mediated RAS paths remain in active deployment.

codex reasoning notes (technical)

`keep` because lore activity is strong and recent: lore_file_timeline on `drivers/acpi/apei/ghes.c` showed heavy churn through 2026-04-17, and lore_regex on linux-acpi subjects surfaced multiple 2026 APEI/GHES/EINJ fix/feature threads, not a removal series. docs.kernel.org was obtained via web search and shows ongoing APEI/EINJ documentation with ACPI 6.5/CXL support. NVIDIA DGX firmware docs were obtained via web search; combined with current-tree Kconfig text read via shell (GHES NVIDIA handler for DGX/HGX), that supports continued use on new server platforms. This is platform firmware/RAS infrastructure rather than a legacy single-device driver, so there is no natural replacement driver.