linux-stable.git/drivers/vfio/platform, branch v4.1

vfio: Split virqfd into a separate module for vfio bus drivers

2015-03-17T14:33:38+00:00

An unintended consequence of commit 42ac9bd18d4f ("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: Alex Williamson

vfio/platform: implement IRQ masking/unmasking via an eventfd

2015-03-16T20:08:55+00:00

With this patch the VFIO user will be able to set an eventfd that can be
used in order to mask and unmask IRQs of platform devices.

Signed-off-by: Antonios Motakis 
Signed-off-by: Baptiste Reynal 
Reviewed-by: Eric Auger 
Tested-by: Eric Auger 
Signed-off-by: Alex Williamson

vfio/platform: support for level sensitive interrupts

2015-03-16T20:08:50+00:00

Level sensitive interrupts are exposed as maskable and automasked
interrupts and are masked and disabled automatically when they fire.

Signed-off-by: Antonios Motakis 
[Baptiste Reynal: Move masked interrupt initialization from "vfio/platform:
trigger an interrupt via eventfd"]
Signed-off-by: Baptiste Reynal 
Reviewed-by: Eric Auger 
Tested-by: Eric Auger 
Signed-off-by: Alex Williamson

vfio/platform: trigger an interrupt via eventfd

2015-03-16T20:08:50+00:00

This patch allows to set an eventfd for a platform device's interrupt,
and also to trigger the interrupt eventfd from userspace for testing.
Level sensitive interrupts are marked as maskable and are handled in
a later patch. Edge triggered interrupts are not advertised as maskable
and are implemented here using a simple and efficient IRQ handler.

Signed-off-by: Antonios Motakis 
[Baptiste Reynal: fix masked interrupt initialization]
Signed-off-by: Baptiste Reynal 
Reviewed-by: Eric Auger 
Tested-by: Eric Auger 
Signed-off-by: Alex Williamson

vfio/platform: initial interrupts support code

2015-03-16T20:08:49+00:00

This patch is a skeleton for the VFIO_DEVICE_SET_IRQS IOCTL, around which
most IRQ functionality is implemented in VFIO.

Signed-off-by: Antonios Motakis 
Signed-off-by: Baptiste Reynal 
Reviewed-by: Eric Auger 
Tested-by: Eric Auger 
Signed-off-by: Alex Williamson

vfio/platform: return IRQ info

2015-03-16T20:08:48+00:00

Return information for the interrupts exposed by the device.
This patch extends VFIO_DEVICE_GET_INFO with the number of IRQs
and enables VFIO_DEVICE_GET_IRQ_INFO.

Signed-off-by: Antonios Motakis 
Signed-off-by: Baptiste Reynal 
Reviewed-by: Eric Auger 
Tested-by: Eric Auger 
Signed-off-by: Alex Williamson

vfio/platform: support MMAP of MMIO regions

2015-03-16T20:08:48+00:00

Allow to memory map the MMIO regions of the device so userspace can
directly access them. PIO regions are not being handled at this point.

Signed-off-by: Antonios Motakis 
Signed-off-by: Baptiste Reynal 
Reviewed-by: Eric Auger 
Tested-by: Eric Auger 
Signed-off-by: Alex Williamson

vfio/platform: read and write support for the device fd

2015-03-16T20:08:47+00:00

VFIO returns a file descriptor which we can use to manipulate the memory
regions of the device. Usually, the user will mmap memory regions that are
addressable on page boundaries, however for memory regions where this is
not the case we cannot provide mmap functionality due to security concerns.
For this reason we also allow to use read and write functions to the file
descriptor pointing to the memory regions.

We implement this functionality only for MMIO regions of platform devices;
PIO regions are not being handled at this point.

Signed-off-by: Antonios Motakis 
Signed-off-by: Baptiste Reynal 
Reviewed-by: Eric Auger 
Tested-by: Eric Auger 
Signed-off-by: Alex Williamson

vfio/platform: return info for device memory mapped IO regions

2015-03-16T20:08:46+00:00

This patch enables the IOCTLs VFIO_DEVICE_GET_REGION_INFO ioctl call,
which allows the user to learn about the available MMIO resources of
a device.

Signed-off-by: Antonios Motakis 
Signed-off-by: Baptiste Reynal 
Reviewed-by: Eric Auger 
Tested-by: Eric Auger 
Signed-off-by: Alex Williamson

vfio/platform: return info for bound device

2015-03-16T20:08:46+00:00

A VFIO userspace driver will start by opening the VFIO device
that corresponds to an IOMMU group, and will use the ioctl interface
to get the basic device info, such as number of memory regions and
interrupts, and their properties. This patch enables the
VFIO_DEVICE_GET_INFO ioctl call.

Signed-off-by: Antonios Motakis 
[Baptiste Reynal: added include in vfio_platform_common.c]
Signed-off-by: Baptiste Reynal 
Reviewed-by: Eric Auger 
Tested-by: Eric Auger 
Signed-off-by: Alex Williamson