~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/Documentation/driver-api/vfio-pci-device-specific-driver-acceptance.rst

Version: ~ [ linux-6.11-rc3 ] ~ [ linux-6.10.4 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.45 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.104 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.164 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.223 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.281 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.319 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.336 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.337 ] ~ [ linux-4.4.302 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.9 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

  1 .. SPDX-License-Identifier: GPL-2.0
  2 
  3 Acceptance criteria for vfio-pci device specific driver variants
  4 ================================================================
  5 
  6 Overview
  7 --------
  8 The vfio-pci driver exists as a device agnostic driver using the
  9 system IOMMU and relying on the robustness of platform fault
 10 handling to provide isolated device access to userspace.  While the
 11 vfio-pci driver does include some device specific support, further
 12 extensions for yet more advanced device specific features are not
 13 sustainable.  The vfio-pci driver has therefore split out
 14 vfio-pci-core as a library that may be reused to implement features
 15 requiring device specific knowledge, ex. saving and loading device
 16 state for the purposes of supporting migration.
 17 
 18 In support of such features, it's expected that some device specific
 19 variants may interact with parent devices (ex. SR-IOV PF in support of
 20 a user assigned VF) or other extensions that may not be otherwise
 21 accessible via the vfio-pci base driver.  Authors of such drivers
 22 should be diligent not to create exploitable interfaces via these
 23 interactions or allow unchecked userspace data to have an effect
 24 beyond the scope of the assigned device.
 25 
 26 New driver submissions are therefore requested to have approval via
 27 sign-off/ack/review/etc for any interactions with parent drivers.
 28 Additionally, drivers should make an attempt to provide sufficient
 29 documentation for reviewers to understand the device specific
 30 extensions, for example in the case of migration data, how is the
 31 device state composed and consumed, which portions are not otherwise
 32 available to the user via vfio-pci, what safeguards exist to validate
 33 the data, etc.  To that extent, authors should additionally expect to
 34 require reviews from at least one of the listed reviewers, in addition
 35 to the overall vfio maintainer.

~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

sflogo.php