1. 19 Jul, 2016 9 commits
  2. 23 Jun, 2016 1 commit
    • Peng Fan's avatar
      vfio: platform: support No-IOMMU mode · 9698cbf0
      Peng Fan authored
      The vfio No-IOMMU mode was supported by this
      'commit 03a76b60 ("vfio: Include No-IOMMU mode")',
      but it only support vfio-pci.
      Using vfio_iommu_group_get/put, but not iommu_group_get/put,
      the platform devices can be exposed to userspace with
      CONFIG_VFIO_NOIOMMU and the "enable_unsafe_noiommu_mode"
      option enabled.
      From 'commit 03a76b60 ("vfio: Include No-IOMMU mode")',
      "This should make it very clear that this mode is not safe.
      Additionally, CAP_SYS_RAWIO privileges are necessary to work
      with groups and containers using this mode.  Groups making
      use of this support are named /dev/vfio/noiommu-$GROUP and
      can only make use of the special VFIO_NOIOMMU_IOMMU for the
      container.  Use of this mode, specifically binding a device
      without a native IOMMU group to a VFIO bus driver will taint
      the kernel and should therefore not be considered supported."
      Signed-off-by: default avatarPeng Fan <van.freenix@gmail.com>
      Cc: Eric Auger <eric.auger@linaro.org>
      Cc: Baptiste Reynal <b.reynal@virtualopensystems.com>
      Cc: Alex Williamson <alex.williamson@redhat.com>
      Reviewed-by: default avatarEric Auger <eric.auger@redhat.com>
      Signed-off-by: default avatarAlex Williamson <alex.williamson@redhat.com>
  3. 28 Feb, 2016 1 commit
  4. 21 Dec, 2015 1 commit
  5. 20 Nov, 2015 1 commit
  6. 19 Nov, 2015 1 commit
  7. 03 Nov, 2015 10 commits
  8. 27 Oct, 2015 1 commit
  9. 22 Jun, 2015 4 commits
  10. 17 Jun, 2015 1 commit
  11. 17 Mar, 2015 1 commit
    • Alex Williamson's avatar
      vfio: Split virqfd into a separate module for vfio bus drivers · 71be3423
      Alex Williamson authored
      An unintended consequence of commit 42ac9bd1 ("vfio: initialize
      the virqfd workqueue in VFIO generic code") is that the vfio module
      is renamed to vfio_core so that it can include both vfio and virqfd.
      That's a user visible change that may break module loading scritps
      and it imposes eventfd support as a dependency on the core vfio code,
      which it's really not.  virqfd is intended to be provided as a service
      to vfio bus drivers, so instead of wrapping it into vfio.ko, we can
      make it a stand-alone module toggled by vfio bus drivers.  This has
      the additional benefit of removing initialization and exit from the
      core vfio code.
      Signed-off-by: default avatarAlex Williamson <alex.williamson@redhat.com>
  12. 16 Mar, 2015 9 commits