On Fri, 2012-05-11 at 16:39 -0700, Greg KH wrote:
> On Fri, May 11, 2012 at 04:55:41PM -0600, Alex Williamson wrote:
> > IOMMU device groups are currently a rather vague associative notion
> > with assembly required by the user or user level driver provider to
> > do anything useful. This patch in
On Fri, 2012-05-11 at 16:38 -0700, Greg KH wrote:
> On Fri, May 11, 2012 at 04:55:35PM -0600, Alex Williamson wrote:
> > IOMMU groups allow IOMMU drivers to represent DMA visibility
> > and isolation of devices. Multiple devices may be grouped
> > together for the purposes of DMA. Placing a point
Fill in many missing definitions and add sizeof fields for many
sections allowing for more extensive config parsing.
Signed-off-by: Alex Williamson
---
include/linux/pci_regs.h | 112 +-
1 files changed, 100 insertions(+), 12 deletions(-)
diff --git
For returning errors out to non-PCI code. Re-name xen's version.
Signed-off-by: Alex Williamson
---
drivers/xen/xen-pciback/conf_space.c |6 +++---
include/linux/pci.h | 26 ++
2 files changed, 29 insertions(+), 3 deletions(-)
diff --git a/driver
VFIO PCI support will make use of these for user initiated
PCI config accesses.
Signed-off-by: Alex Williamson
---
drivers/pci/access.c |6 --
drivers/pci/pci.h|7 ---
include/linux/pci.h |8
3 files changed, 12 insertions(+), 9 deletions(-)
diff --git a/drive
x86 is probably the wrong name for this VFIO IOMMU driver, but x86
is the primary target for it. This driver support a very simple
usage model using the existing IOMMU API. The IOMMU is expected to
support the full host address space with no special IOVA windows,
number of mappings restrictions,
VFIO is a secure user level driver for use with both virtual machines
and user level drivers. VFIO makes use of IOMMU groups to ensure the
isolation of devices in use, allowing unprivileged user access. It's
intended that VFIO will replace KVM device assignment and UIO drivers
(in cases where the
Signed-off-by: Alex Williamson
---
Documentation/vfio.txt | 315
1 files changed, 315 insertions(+), 0 deletions(-)
create mode 100644 Documentation/vfio.txt
diff --git a/Documentation/vfio.txt b/Documentation/vfio.txt
new file mode 100644
inde
Incorporate DMA quirking and ACS checking into amd_iommu and
intel-iommu. Note that IOMMU groups are not yet used for
streaming DMA, so this doesn't immediately solve the problems
with broken Ricoh devices.
Signed-off-by: Alex Williamson
---
drivers/iommu/amd_iommu.c |3 +++
drivers/iomm
In a PCIe environment, transactions aren't always required to
reach the root bus before being re-routed. Peer-to-peer DMA
may actually not be seen by the IOMMU in these cases. For
IOMMU groups, we want to provide IOMMU drivers a way to detect
these restrictions. Provided with a PCI device, pci_a
Integrating IOMMU groups more closely into the driver core allows
us to more easily work around DMA quirks. The Ricoh multifunction
controller is a favorite example of devices that are currently
incompatible with IOMMU isolation as all the functions use the
requestor ID of function 0 for DMA. Pas
Add back group support for AMD & Intel. amd_iommu already tracks
devices and has init and uninit routines to manage groups.
intel-iommu does this on the fly, so we make use of the notifier
support built into iommu groups to create and remove groups.
Signed-off-by: Alex Williamson
---
drivers/i
IOMMU device groups are currently a rather vague associative notion
with assembly required by the user or user level driver provider to
do anything useful. This patch intends to grow the IOMMU group concept
into something a bit more consumable.
To do this, we first create an object representing t
or a
group. I've poorly chosen the name "x86" for the current IOMMU
backend, simply for lack of a good way to describe a non-window based,
page table driven IOMMU implementation.
These patches can be found in git here:
git://github.com/awilliam/linux-vfio.git (iommu-group-vfio-201
IOMMU groups allow IOMMU drivers to represent DMA visibility
and isolation of devices. Multiple devices may be grouped
together for the purposes of DMA. Placing a pointer on
struct device enable easy access for things like streaming
DMA programming and drivers like VFIO.
Signed-off-by: Alex Will
On 04/11/12 23:34, Marek Szyprowski wrote:
Fix registration to runtime pw and add missing resume callback.
Signed-off-by: Marek Szyprowski
Acked-by: Kyungmin Park
---
drivers/iommu/exynos-iommu.c | 20 ++--
1 files changed, 18 insertions(+), 2 deletions(-)
diff --git a/driv
On 05/11/12 21:43, Joerg Roedel wrote:
On Fri, May 11, 2012 at 09:27:09PM +0900, KyongHo wrote:
This is the System MMU driver and IOMMU API implementation for Exynos SOC
platforms. Exynos platforms has more than 10 System MMUs dedicated for each
multimedia accelerators.
The System MMU driver is
On Fri, May 11, 2012 at 09:27:09PM +0900, KyongHo wrote:
> This is the System MMU driver and IOMMU API implementation for Exynos SOC
> platforms. Exynos platforms has more than 10 System MMUs dedicated for each
> multimedia accelerators.
>
> The System MMU driver is already in arc/arm/plat-s5p but
This is the System MMU driver and IOMMU API implementation for Exynos SOC
platforms. Exynos platforms has more than 10 System MMUs dedicated for each
multimedia accelerators.
The System MMU driver is already in arc/arm/plat-s5p but it is moved to
drivers/iommu due to Ohad Ben-Cohen gathered IOMMU
Fix the following build issue:
arch/arm/mm/dma-mapping.c:726:42: error: 'pgprot_kernel' undeclared
(first use in this function)
make[2]: *** [arch/arm/mm/dma-mapping.o] Error 1
Reported-by: Paul Gortmaker
Signed-off-by: Marek Szyprowski
---
arch/arm/mm/dma-mapping.c | 17 +
1
Hello,
On Friday, May 11, 2012 4:09 AM Paul Gortmaker wrote:
> On Wed, Apr 18, 2012 at 9:44 AM, Marek Szyprowski
> wrote:
> > This patch add a complete implementation of DMA-mapping API for
> > devices which have IOMMU support.
>
> Hi Marek,
>
> It looks like this patch breaks no-MMU builds on
21 matches
Mail list logo
