36 lines · plain
1.. SPDX-License-Identifier: GPL-2.02 3Acceptance criteria for vfio-pci device specific driver variants4================================================================5 6Overview7--------8The vfio-pci driver exists as a device agnostic driver using the9system IOMMU and relying on the robustness of platform fault10handling to provide isolated device access to userspace. While the11vfio-pci driver does include some device specific support, further12extensions for yet more advanced device specific features are not13sustainable. The vfio-pci driver has therefore split out14vfio-pci-core as a library that may be reused to implement features15requiring device specific knowledge, ex. saving and loading device16state for the purposes of supporting migration.17 18In support of such features, it's expected that some device specific19variants may interact with parent devices (ex. SR-IOV PF in support of20a user assigned VF) or other extensions that may not be otherwise21accessible via the vfio-pci base driver. Authors of such drivers22should be diligent not to create exploitable interfaces via these23interactions or allow unchecked userspace data to have an effect24beyond the scope of the assigned device.25 26New driver submissions are therefore requested to have approval via27sign-off/ack/review/etc for any interactions with parent drivers.28Additionally, drivers should make an attempt to provide sufficient29documentation for reviewers to understand the device specific30extensions, for example in the case of migration data, how is the31device state composed and consumed, which portions are not otherwise32available to the user via vfio-pci, what safeguards exist to validate33the data, etc. To that extent, authors should additionally expect to34require reviews from at least one of the listed reviewers, in addition35to the overall vfio maintainer.36