1. 27 3月, 2013 1 次提交
  2. 08 2月, 2013 1 次提交
    • J
      iommu/amd: Initialize device table after dma_ops · f528d980
      Joerg Roedel 提交于
      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 device table after dma_ops.
      
      Cc: stable@vger.kernel.org
      Signed-off-by: NJoerg Roedel <joro@8bytes.org>
      f528d980
  3. 28 1月, 2013 1 次提交
  4. 16 10月, 2012 1 次提交
  5. 28 9月, 2012 10 次提交
  6. 18 9月, 2012 2 次提交
  7. 10 8月, 2012 1 次提交
  8. 07 8月, 2012 1 次提交
  9. 17 7月, 2012 9 次提交
  10. 02 7月, 2012 1 次提交
  11. 07 6月, 2012 1 次提交
  12. 04 6月, 2012 1 次提交
    • J
      iommu/amd: Cache pdev pointer to root-bridge · c1bf94ec
      Joerg Roedel 提交于
      At some point pci_get_bus_and_slot started to enable
      interrupts. Since this function is used in the
      amd_iommu_resume path it will enable interrupts on resume
      which causes a warning. The fix will use a cached pointer
      to the root-bridge to re-enable the IOMMU in case the BIOS
      is broken.
      
      Cc: stable@vger.kernel.org
      Signed-off-by: NJoerg Roedel <joerg.roedel@amd.com>
      c1bf94ec
  13. 23 3月, 2012 1 次提交
  14. 15 3月, 2012 2 次提交
  15. 09 3月, 2012 1 次提交
  16. 08 3月, 2012 1 次提交
  17. 01 3月, 2012 1 次提交
    • J
      iommu/amd: Split amd_iommu_init function · 8704a1ba
      Joerg Roedel 提交于
      The hardware-initializtion part of the AMD IOMMU driver is
      split out into a seperate function. This function can now be
      called either from amd_iommu_init() itself or any other
      place if the hardware needs to be ready earlier. This will
      be used to implement interrupt remapping for AMD.
      Signed-off-by: NJoerg Roedel <joerg.roedel@amd.com>
      8704a1ba
  18. 22 12月, 2011 2 次提交
  19. 12 12月, 2011 2 次提交