On Feb 27, 2013, at 5:33 AM, Joerg Roedel wrote:
On Mon, Feb 18, 2013 at 06:22:16PM +0530, Varun Sethi wrote:
Macros for checking FSL PCI controller version.
Signed-off-by: Varun Sethi varun.se...@freescale.com
---
arch/powerpc/include/asm/pci-bridge.h |4
1 files changed, 4
On Feb 27, 2013, at 4:56 AM, Sethi Varun-B16395 wrote:
This patch is present in the next branch of linux ppc tree maintained by
Kumar Gala.
Following is the commit id:
52c5affc545053d37c0b05224bbf70f5336caa20
I am not sure if this would be part of 3.9-rc1.
Regards
varun
This is now
On Tue, 2013-02-26 at 16:49 -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
On Thu, 2013-02-28 at 12:52 -0700, Shuah Khan wrote:
On Tue, 2013-02-26 at 16:49 -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
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 IOMMU. Make sure this does not
happen by initializing the
Hi Shuah,
On Thu, Feb 28, 2013 at 12:52:00PM -0700, Shuah Khan wrote:
On Tue, 2013-02-26 at 16:49 -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
Hi!
On POWERNV we use only the part of IOMMU API which handles devices and
groups. We do not use IOMMU domains as VFIO containers do everything we
need for VFIO and we do not implement iommu_ops as it is not very relevant
to our architecture (does not give dma window properties, etc).
So
