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

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

2013-03-03 Thread Joerg Roedel
Hi Ben, On Sat, Mar 02, 2013 at 11:00:35PM +, Ben Hutchings wrote: I'm not convinced about this backport, because the order of initialisation already changed a lot after 3.2 and before the upstream commit. So I'm going to wait for Joerg to confirm that this makes sense before adding it

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

2013-02-28 Thread Shuah Khan
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