1. 27 11月, 2009 11 次提交
  2. 23 11月, 2009 1 次提交
    • J
      x86/amd-iommu: attach devices to pre-allocated domains early · be831297
      Joerg Roedel 提交于
      For some devices the ACPI table may define unity map
      requirements which must me met when the IOMMU is enabled. So
      we need to attach devices to their domains as early as
      possible so that these mappings are in place when needed.
      This patch assigns the domains right after they are
      allocated. Otherwise this can result in I/O page faults
      before a driver binds to a device and BIOS is still using
      it.
      
      Cc: stable@kernel.org
      Signed-off-by: NJoerg Roedel <joerg.roedel@amd.com>
      be831297
  3. 17 11月, 2009 1 次提交
    • F
      x86: Kill bad_dma_address variable · 8fd524b3
      FUJITA Tomonori 提交于
      This kills bad_dma_address variable, the old mechanism to enable
      IOMMU drivers to make dma_mapping_error() work in IOMMU's
      specific way.
      
      bad_dma_address variable was introduced to enable IOMMU drivers
      to make dma_mapping_error() work in IOMMU's specific way.
      However, it can't handle systems that use both swiotlb and HW
      IOMMU. SO we introduced dma_map_ops->mapping_error to solve that
      case.
      
      Intel VT-d, GART, and swiotlb already use
      dma_map_ops->mapping_error. Calgary, AMD IOMMU, and nommu use
      zero for an error dma address. This adds DMA_ERROR_CODE and
      converts them to use it (as SPARC and POWER does).
      Signed-off-by: NFUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
      Acked-by: NJesse Barnes <jbarnes@virtuousgeek.org>
      Cc: muli@il.ibm.com
      Cc: joerg.roedel@amd.com
      LKML-Reference: <1258287594-8777-3-git-send-email-fujita.tomonori@lab.ntt.co.jp>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      8fd524b3
  4. 10 11月, 2009 1 次提交
    • F
      x86: Handle HW IOMMU initialization failure gracefully · 75f1cdf1
      FUJITA Tomonori 提交于
      If HW IOMMU initialization fails (Intel VT-d often does this,
      typically due to BIOS bugs), we fall back to nommu. It doesn't
      work for the majority since nowadays we have more than 4GB
      memory so we must use swiotlb instead of nommu.
      
      The problem is that it's too late to initialize swiotlb when HW
      IOMMU initialization fails. We need to allocate swiotlb memory
      earlier from bootmem allocator. Chris explained the issue in
      detail:
      
        http://marc.info/?l=linux-kernel&m=125657444317079&w=2
      
      The current x86 IOMMU initialization sequence is too complicated
      and handling the above issue makes it more hacky.
      
      This patch changes x86 IOMMU initialization sequence to handle
      the above issue cleanly.
      
      The new x86 IOMMU initialization sequence are:
      
      1. we initialize the swiotlb (and setting swiotlb to 1) in the case
         of (max_pfn > MAX_DMA32_PFN && !no_iommu). dma_ops is set to
         swiotlb_dma_ops or nommu_dma_ops. if swiotlb usage is forced by
         the boot option, we finish here.
      
      2. we call the detection functions of all the IOMMUs
      
      3. the detection function sets x86_init.iommu.iommu_init to the
         IOMMU initialization function (so we can avoid calling the
         initialization functions of all the IOMMUs needlessly).
      
      4. if the IOMMU initialization function doesn't need to swiotlb
         then sets swiotlb to zero (e.g. the initialization is
         sucessful).
      
      5. if we find that swiotlb is set to zero, we free swiotlb
         resource.
      Signed-off-by: NFUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
      Cc: chrisw@sous-sol.org
      Cc: dwmw2@infradead.org
      Cc: joerg.roedel@amd.com
      Cc: muli@il.ibm.com
      LKML-Reference: <1257849980-22640-10-git-send-email-fujita.tomonori@lab.ntt.co.jp>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      75f1cdf1
  5. 10 10月, 2009 1 次提交
    • J
      x86/amd-iommu: Workaround for erratum 63 · c5cca146
      Joerg Roedel 提交于
      There is an erratum for IOMMU hardware which documents
      undefined behavior when forwarding SMI requests from
      peripherals and the DTE of that peripheral has a sysmgt
      value of 01b. This problem caused weird IO_PAGE_FAULTS in my
      case.
      This patch implements the suggested workaround for that
      erratum into the AMD IOMMU driver.  The erratum is
      documented with number 63.
      
      Cc: stable@kernel.org
      Signed-off-by: NJoerg Roedel <joerg.roedel@amd.com>
      c5cca146
  6. 03 9月, 2009 25 次提交