drivers/vfio

VFIO device passthrough framework

VFIO is the in-kernel framework that lets host software hand a physical PCI or platform device — such as a GPU, NIC, or accelerator — directly to a virtual machine or a userspace program with IOMMU-enforced isolation. It is the foundation that QEMU/KVM and other hypervisors use for device passthrough and SR-IOV virtual function assignment on current server and workstation hardware.

keep conf=0.95 deploy=high replacement=none subsystem=vfio category=virtualization
95%

recommendation

It should stay because VFIO is the standard Linux framework for safely handing real PCI devices (GPUs, NICs, accelerators) directly to virtual machines and userspace drivers, and it is actively developed. Recent patch traffic in 2026 adds new PCIe features and fixes, and current QEMU releases rely on it for VM device passthrough and live migration, so it underpins a large share of modern virtualization and cloud deployments.

repository signals

88 files
33,169 source lines
621 commits, 5y
+28,693 / −12,648 lines added / removed, 5y
130 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 621 total · active in 58/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 6 commits · +18 −44 2021-06: 6 commits · +94 −74 2021-07: 8 commits · +15 −22 2021-08: 23 commits · +1,120 −1,381 2021-09: 17 commits · +409 −527 2021-10: 6 commits · +329 −296 2021-11: 2 commits · +17 −16 2021-12: 3 commits · +12 −9 2022-01: 1 commit · +2 −0 2022-02: 9 commits · +1,405 −84 2022-03: 5 commits · +1,489 −24 2022-04: 12 commits · +150 −545 2022-05: 29 commits · +874 −831 2022-06: 16 commits · +148 −66 2022-07: 11 commits · +202 −240 2022-08: 21 commits · +1,026 −570 2022-09: 52 commits · +3,434 −1,579 2022-10: 7 commits · +75 −35 2022-11: 28 commits · +1,945 −1,262 2022-12: 21 commits · +1,271 −423 2023-01: 24 commits · +514 −279 2023-02: 4 commits · +116 −24 2023-03: 12 commits · +59 −129 2023-04: 0 commits · +0 −0 2023-05: 16 commits · +602 −157 2023-06: 7 commits · +56 −31 2023-07: 29 commits · +1,094 −267 2023-08: 13 commits · +2,201 −90 2023-09: 12 commits · +382 −116 2023-10: 6 commits · +21 −429 2023-11: 12 commits · +465 −246 2023-12: 4 commits · +629 −28 2024-01: 3 commits · +5 −4 2024-02: 14 commits · +1,127 −127 2024-03: 13 commits · +322 −313 2024-04: 7 commits · +1,048 −39 2024-05: 5 commits · +171 −244 2024-06: 5 commits · +92 −69 2024-07: 6 commits · +8 −27 2024-08: 3 commits · +49 −30 2024-09: 3 commits · +2 −10 2024-10: 3 commits · +4 −12 2024-11: 9 commits · +2,291 −486 2024-12: 8 commits · +59 −46 2025-01: 10 commits · +223 −86 2025-02: 6 commits · +81 −54 2025-03: 6 commits · +124 −30 2025-04: 2 commits · +2 −49 2025-05: 13 commits · +404 −364 2025-06: 5 commits · +14 −13 2025-07: 6 commits · +73 −16 2025-08: 11 commits · +155 −31 2025-09: 7 commits · +37 −7 2025-10: 6 commits · +231 −108 2025-11: 29 commits · +1,701 −521 2025-12: 6 commits · +31 −14 2026-01: 8 commits · +168 −16 2026-02: 4 commits · +95 −105 2026-03: 1 commit · +2 −3 2026-04: 0 commits · +0 −0

sources

  1. lore.kernel.org

    April 25, 2026 patch series adds new vfio/pci PCIe TPH support, showing active feature development rather than retirement.

  2. lore.kernel.org

    April 24, 2026 vfio/pci bug-fix patch shows ongoing maintenance activity.

  3. docs.kernel.org

    Kernel documentation describes VFIO as the in-kernel framework and API used by VFIO bus drivers such as vfio-pci.

  4. qemu.org

    Current QEMU documentation covers live migration for VFIO devices, indicating present-day virtualization deployments.

codex reasoning notes (technical)

`drivers/vfio` is an active driver/framework directory, not an obsolete leaf driver: the prompt already shows 252 substantive commits in 5y with a latest touch on 2025-11-28. I obtained the two lore URLs via `lore_path_mentions(path="drivers/vfio/", match="prefix", since="5y")`, which returned fresh Apr 2026 VFIO feature and fix patches. I obtained the kernel-docs and QEMU URLs via web search on `kernel.org`/`qemu.org`. VFIO is a generic passthrough framework used with current PCI/accelerator devices and current VMM stacks, so it is still relevant for new 2025 deployments; there is no natural replacement for the directory as a whole beyond VFIO itself evolving.