Re: [PATCH 6/7] VFIO: Update documentation for VFIO_IOMMU_TYPE1 driver

2013-09-30 Thread Alex Williamson
On Mon, 2013-09-30 at 17:28 +0200, Antonios Motakis wrote: The VFIO documentation is slightly out of date. This minor correction replaces references to VFIO_IOMMU_X86 with the correct reference to VFIO_IOMMU_TYPE1 Signed-off-by: Antonios Motakis a.mota...@virtualopensystems.com ---

Re: [PATCH 1/7] VFIO_IOMMU_TYPE1 workaround to build for platform devices

2013-09-30 Thread Alex Williamson
On Mon, 2013-09-30 at 17:28 +0200, Antonios Motakis wrote: This is a workaround to make the VFIO_IOMMU_TYPE1 driver usable with platform devices instead of PCI. A future permanent fix should support both. This is required in order to use the Exynos SMMU, or ARM SMMU driver with VFIO.

Re: [PATCH 3/7] Return info for device and its memory regions and interrupts

2013-09-30 Thread Alex Williamson
On Mon, 2013-09-30 at 17:28 +0200, Antonios Motakis wrote: 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.

Re: [RFC PATCH v2 0/7] VFIO for device tree based platform devices (work in progress)

2013-09-30 Thread Alex Williamson
On Mon, 2013-09-30 at 17:28 +0200, Antonios Motakis wrote: This is a preview of the base work, towards VFIO support on ARM platforms with an IOMMU. It forms a base on to which to implement the functionality necessary to enable using device tree devices on ARM (and other platforms based on

Re: [PATCH 2/7] Initial skeleton of VFIO support for Device Tree based devices

2013-09-30 Thread Alex Williamson
On Mon, 2013-09-30 at 17:28 +0200, Antonios Motakis wrote: Platform devices in the Linux kernel are usually managed by the DT interface. This patch forms the base to support these kind of devices with VFIO. Signed-off-by: Antonios Motakis a.mota...@virtualopensystems.com ---

Re: [PATCH 3/7] Return info for device and its memory regions and interrupts

2013-10-01 Thread Alex Williamson
On Tue, 2013-10-01 at 19:32 +, Yoder Stuart-B08248 wrote: Antonios Motakis wrote Alex Williamson alex.william...@redhat.com wrote: I notice all the open firmware calls here and I'm curious, will all platform devices be making use of open firmware? I don't know

Re: [PATCH v10 20/20] iommu/exynos: add devices attached to the System MMU to an IOMMU group

2013-10-10 Thread Alex Williamson
On Mon, 2013-10-07 at 10:58 +0900, Cho KyongHo wrote: Patch written by Antonios Motakis a.mota...@virtualopensystems.com: IOMMU groups are expected by certain users of the IOMMU API, e.g. VFIO. Since each device is behind its own System MMU, we can allocate a new IOMMU group for each device.

Re: [PATCH 2/7] Initial skeleton of VFIO support for Device Tree based devices

2013-10-29 Thread Alex Williamson
On Mon, 2013-10-28 at 21:29 -0400, Don Dutile wrote: On 09/30/2013 11:37 AM, Bhushan Bharat-R65777 wrote: -Original Message- From: iommu-boun...@lists.linux-foundation.org [mailto:iommu- boun...@lists.linux-foundation.org] On Behalf Of Antonios Motakis Sent: Monday, September

Re: [PATCH 2/3] Initial skeleton of VFIO support for Device Tree based devices

2013-08-05 Thread Alex Williamson
On Mon, 2013-08-05 at 15:17 +0200, Antonios Motakis wrote: Platform devices in the Linux kernel are usually managed by the DT interface. This patch forms the base to support these kind of devices with VFIO. Signed-off-by: Antonios Motakis a.mota...@virtualopensystems.com ---

Re: [PATCH 00/16 v2] iommu: Move domain allocation into drivers

2015-03-27 Thread Alex Williamson
their own mappings The patches have been compile tested for x86, ARM and PPC and runtime tested on x86 (Intel VT-d and AMD IOMMU). Please review. For 1-5,16 Reviewed-by: Alex Williamson alex.william...@redhat.com My only comment/question is whether you'd want to consider using