Virtio-PCI vDPA bridge for modern virtio-pci devices
A bridge that lets modern virtio-pci devices, whether real PCI hardware or software-emulated, plug into the kernel's vDPA framework so they can be handed through to virtual machines via vhost-vDPA. It is a building block of current Linux virtualization stacks used with QEMU/KVM rather than a driver for any one specific chip.
recommendation
It should stay because it is an actively maintained piece of the modern virtualization stack, with substantive feature work landing as recently as October 2025 (new map operations and kick-vq callbacks) and ongoing relevance in current QEMU vhost-vDPA deployments. Nothing in-tree replaces the same role, and virtio-pci remains the recommended device model for new VMs.
repository signals
sources
- git.kernel.org
The directory contains a real kernel PCI driver, and the file header describes it as a vDPA bridge driver for modern virtio-pci devices.
- git.kernel.org
The driver/subsystem was still receiving substantive upstream feature work on 2025-10-01 ('vdpa: introduce map ops').
- git.kernel.org
The driver received functional work in 2025 ('implement kick_vq_with_data callback'), indicating ongoing maintenance rather than retirement.
- qemu.org
Current QEMU documentation describes active vDPA support and notes vDPA devices may be physical hardware or software-emulated, showing present-day deployment relevance.
- qemu.org
Current QEMU documentation presents VirtIO devices as the recommended device models for virtual machines, supporting continued new deployments of modern virtio-pci based environments.
codex reasoning notes (technical)
Keep. Local shell inspection (`sed`) showed `vp_vdpa.c` is a real PCI-backed vDPA bridge for modern virtio-pci, not legacy hardware. Local `git log` showed substantive touches through 2025-10-01 plus later treewide cleanups, with no sign of stagnation; canonical kernel.org commit URLs were formed from SHAs obtained via shell. Direct lore access was unavailable in this environment (`lore-http` MCP absent, `lei` not installed), so upstream-activity evidence is approximated from local git history rather than lore threads. Web search found current QEMU vhost-vdpa and VirtIO docs, which indicate this is tied to ongoing virtualization/vDPA deployments rather than obsolete silicon. Because the driver is generic and dynamically bound (`id_table = NULL`), it is niche compared with mainstream virtio, but it remains relevant in new virtualized deployments; no natural in-tree replacement supersedes the same use case.