drivers/vfio/platform/reset

VFIO platform reset handlers for Calxeda XGMAC, AMD Seattle XGBE, and Broadcom FlexRM

Helper modules that safely reset three specific server devices before VFIO hands them to a virtual machine: the 10-gigabit Ethernet on Calxeda Highbank ARM microservers (early 2010s), the XGBE 10-gigabit Ethernet on AMD Seattle "Opteron A1100" ARM servers (mid-2010s), and Broadcom iProc FlexRM mailboxes on some Broadcom networking SoCs.

remove conf=0.93 deploy=low replacement=none subsystem=vfio category=virtualization
93%

recommendation

Already on the path to removal. As of September 2025 the kernel's Kconfig explicitly marks all three reset handlers as deprecated, VFIO maintainer Alex Williamson has posted patches stating the hardware is unsupported and untested, and QEMU 10.2 has already deleted the matching vfio-calxeda-xgmac, vfio-amd-xgbe, and vfio-platform front-ends on the grounds that Calxeda boxes are e-waste and AMD Seattle is end-of-life. With the userspace counterpart gone and upstream consensus to drop them, these modules have no realistic users left.

repository signals

5 files
302 source lines
4 commits, 5y
+13 / −15 lines added / removed, 5y
3 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 4 total · active in 3/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 0 commits · +0 −0 2021-06: 0 commits · +0 −0 2021-07: 0 commits · +0 −0 2021-08: 2 commits · +2 −12 2021-09: 0 commits · +0 −0 2021-10: 0 commits · +0 −0 2021-11: 0 commits · +0 −0 2021-12: 0 commits · +0 −0 2022-01: 0 commits · +0 −0 2022-02: 0 commits · +0 −0 2022-03: 0 commits · +0 −0 2022-04: 0 commits · +0 −0 2022-05: 0 commits · +0 −0 2022-06: 0 commits · +0 −0 2022-07: 0 commits · +0 −0 2022-08: 0 commits · +0 −0 2022-09: 0 commits · +0 −0 2022-10: 0 commits · +0 −0 2022-11: 0 commits · +0 −0 2022-12: 0 commits · +0 −0 2023-01: 0 commits · +0 −0 2023-02: 0 commits · +0 −0 2023-03: 0 commits · +0 −0 2023-04: 0 commits · +0 −0 2023-05: 0 commits · +0 −0 2023-06: 1 commit · +2 −0 2023-07: 0 commits · +0 −0 2023-08: 0 commits · +0 −0 2023-09: 0 commits · +0 −0 2023-10: 0 commits · +0 −0 2023-11: 0 commits · +0 −0 2023-12: 0 commits · +0 −0 2024-01: 0 commits · +0 −0 2024-02: 0 commits · +0 −0 2024-03: 0 commits · +0 −0 2024-04: 0 commits · +0 −0 2024-05: 0 commits · +0 −0 2024-06: 0 commits · +0 −0 2024-07: 0 commits · +0 −0 2024-08: 0 commits · +0 −0 2024-09: 0 commits · +0 −0 2024-10: 0 commits · +0 −0 2024-11: 0 commits · +0 −0 2024-12: 0 commits · +0 −0 2025-01: 0 commits · +0 −0 2025-02: 0 commits · +0 −0 2025-03: 0 commits · +0 −0 2025-04: 0 commits · +0 −0 2025-05: 0 commits · +0 −0 2025-06: 0 commits · +0 −0 2025-07: 0 commits · +0 −0 2025-08: 1 commit · +9 −3 2025-09: 0 commits · +0 −0 2025-10: 0 commits · +0 −0 2025-11: 0 commits · +0 −0 2025-12: 0 commits · +0 −0 2026-01: 0 commits · +0 −0 2026-02: 0 commits · +0 −0 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. lore.kernel.org

    Upstream removal thread for these reset modules; the maintainer says they do not support current hardware, are untested, and are being marked for removal.

  2. spinics.net

    Discussion around the vfio-platform removal effort shows only niche surviving vfio-platform users, not renewed support for these specific reset handlers.

  3. qemu.org

    QEMU 10.2 removed vfio-calxeda-xgmac, vfio-amd-xgbe, and vfio-platform, stating Calxeda hardware is effectively e-waste and AMD Seattle is no longer supported.

  4. cateee.net

    Broadcom FlexRM mailbox support still exists in current kernels, indicating the underlying IP can still exist, but this does not imply active vfio reset-handler deployments.

codex reasoning notes (technical)

Local shell inspection shows this directory contains three loadable vfio reset-handler modules (`module_vfio_reset_handler`) and Kconfig already labels all three as DEPRECATED. `git -c safe.directory=... log/show` on the local tree found commit 801ca4ce0bce ('vfio/platform: Mark reset drivers for removal', committed 2025-09-19) and exposed the canonical lore URL cited above. Web search found the KVM thread reply on spinics and QEMU's removed-features page. Together they show active upstream removal intent, obsolete Calxeda/Seattle targets, and only at most residual niche vfio-platform usage, so this should be escalated from deprecate to remove.