Re: [PATCH] Quirk to support Marvell 88SE91xx SATA controllers with Intel IOMMU.

2013-03-05 Thread Andrew Cooks
On Wed, Mar 6, 2013 at 12:04 PM, Alex Williamson wrote: > On Fri, 2013-03-01 at 16:26 +0800, Andrew Cooks wrote: > >> + >> + for (fn = 1; fn < 8; fn++) { > > Wouldn't you want to do 0 to 7, then add: > > if (fn == PCI_FUNC(pdev->devfn)) > continue; > > You could also get more creative

Re: [PATCH] Quirk to support Marvell 88SE91xx SATA controllers with Intel IOMMU.

2013-03-05 Thread Alex Williamson
On Fri, 2013-03-01 at 16:26 +0800, Andrew Cooks wrote: > This is my third submitted patch to make Marvell 88SE91xx SATA controllers > work when IOMMU is enabled.[1][2] > > What's changed: > * Adopt David Woodhouse's terminology by referring to the quirky functions as > 'ghost' functions. > * Unm

Re: Marvell 88NV9143 in mini-PCIe not working with intel_iommu=on

2013-03-05 Thread Alex Williamson
On Wed, 2013-03-06 at 10:48 +0800, Andrew Cooks wrote: > On Tue, Mar 5, 2013 at 11:03 PM, Gaudenz Steinlin > wrote: > > > > [ Sending this to the MVUMI driver authors and the IOMMU list as I can't > > tell which part is at fault. ] > > > > [ ... ] > > [4.342079] dmar: DRHD: handling fault sta

Re: Marvell 88NV9143 in mini-PCIe not working with intel_iommu=on

2013-03-05 Thread Andrew Cooks
On Tue, Mar 5, 2013 at 11:03 PM, Gaudenz Steinlin wrote: > > [ Sending this to the MVUMI driver authors and the IOMMU list as I can't > tell which part is at fault. ] > > [ ... ] > [4.342079] dmar: DRHD: handling fault status reg 2 > [4.342132] dmar: DMAR:[DMA Read] Request device [02:00.0

Re: [PATCH 8/9] iommu: OMAP: build only on OMAP2+

2013-03-05 Thread Tony Lindgren
* Arnd Bergmann [130305 14:21]: > The OMAP IOMMU driver intentionally fails to build on OMAP1 > platforms, so we should not allow enabling it there. > > Signed-off-by: Arnd Bergmann > Cc: Joerg Roedel > Cc: iommu@lists.linux-foundation.org > Cc: Ohad Ben-Cohen > Cc: Tony Lindgren > Cc: Omar R

[PATCH 0/9] fixes for ARM build regressions in 3.9-rc1

2013-03-05 Thread Arnd Bergmann
This is the result of my my build tests on 3.9-rc1, mostly bugs that I had not caught before the merge window, or where the fix for some reason has not yet made it in. I hope the subsystem maintainers can take care of applying these, for the arch/arm/mach-* patches I can either apply them directly

[PATCH 8/9] iommu: OMAP: build only on OMAP2+

2013-03-05 Thread Arnd Bergmann
The OMAP IOMMU driver intentionally fails to build on OMAP1 platforms, so we should not allow enabling it there. Signed-off-by: Arnd Bergmann Cc: Joerg Roedel Cc: iommu@lists.linux-foundation.org Cc: Ohad Ben-Cohen Cc: Tony Lindgren Cc: Omar Ramirez Luna --- drivers/iommu/Kconfig | 2 +- 1 f

Problem with ethernet/sound with IOMMU enabled on M5A99FX pro r2.0 motherboard

2013-03-05 Thread JapHack
I recently bought this board as I wanted to start doing pci passthrough emulation. I noticed that after I had installed it and booted up, with IOMMU enabled the network would work fine for a while then I would get an AMD-Vi IO page fault and the driver would crash. IF I turn off IOMMU there is

Re: [PATCH 3.2] iommu/amd: Initialize device table after dma_ops

2013-03-05 Thread Ben Hutchings
On Thu, 2013-02-28 at 14:39 -0700, Shuah Khan wrote: > When dma_ops are initialized the unity mappings are created. The > init_device_table_dma() function makes sure DMA from all devices is > blocked by default. This opens a short window in time where DMA to > unity mapped regions is blocked by the