1. 09 10月, 2010 2 次提交
  2. 08 10月, 2010 1 次提交
  3. 29 9月, 2010 2 次提交
  4. 28 9月, 2010 8 次提交
  5. 27 9月, 2010 2 次提交
  6. 26 9月, 2010 2 次提交
  7. 25 9月, 2010 15 次提交
  8. 24 9月, 2010 4 次提交
  9. 23 9月, 2010 4 次提交
    • J
      x86/amd-iommu: Fix rounding-bug in __unmap_single · 04e0463e
      Joerg Roedel 提交于
      In the __unmap_single function the dma_addr is rounded down
      to a page boundary before the dma pages are unmapped. The
      address is later also used to flush the TLB entries for that
      mapping. But without the offset into the dma page the amount
      of pages to flush might be miscalculated in the TLB flushing
      path. This patch fixes this bug by using the original
      address to flush the TLB.
      
      Cc: stable@kernel.org
      Signed-off-by: NJoerg Roedel <joerg.roedel@amd.com>
      04e0463e
    • J
      x86/amd-iommu: Work around S3 BIOS bug · 4c894f47
      Joerg Roedel 提交于
      This patch adds a workaround for an IOMMU BIOS problem to
      the AMD IOMMU driver. The result of the bug is that the
      IOMMU does not execute commands anymore when the system
      comes out of the S3 state resulting in system failure. The
      bug in the BIOS is that is does not restore certain hardware
      specific registers correctly. This workaround reads out the
      contents of these registers at boot time and restores them
      on resume from S3. The workaround is limited to the specific
      IOMMU chipset where this problem occurs.
      
      Cc: stable@kernel.org
      Signed-off-by: NJoerg Roedel <joerg.roedel@amd.com>
      4c894f47
    • J
      x86/amd-iommu: Set iommu configuration flags in enable-loop · e9bf5197
      Joerg Roedel 提交于
      This patch moves the setting of the configuration and
      feature flags out out the acpi table parsing path and moves
      it into the iommu-enable path. This is needed to reliably
      fix resume-from-s3.
      
      Cc: stable@kernel.org
      Signed-off-by: NJoerg Roedel <joerg.roedel@amd.com>
      e9bf5197
    • N
      ARM: 6401/1: plug a race in the alignment trap handler · 2f27bf83
      Nicolas Pitre 提交于
      When the policy for user space is to ignore misaligned accesses from user
      space, the processor then performs a documented rotation on the accessed
      data.  This is the result of the access being trapped, and the kernel
      disabling the alignment trap before returning to user space again.
      
      In kernel space we always want misaligned accesses to be fixed up.  This
      is enforced by always re-enabling the alignment trap on every entry into
      kernel space from user space.  No such re-enabling is performed when an
      exception occurs while already in kernel space as the alignment trap is
      always supposed to be enabled in that case.
      
      There is however a small race window when a misaligned access in user
      space is trapped and the alignment trap disabled, but the CPU didn't
      return to user space just yet.  Any exception would be entered from kernel
      space at that point and the kernel would then execute with the alignment
      trap disabled.
      
      Thanks to Maxime Bizon <mbizon@freebox.fr> for providing a test module
      that made this issue reproducible.
      Signed-off-by: NNicolas Pitre <nicolas.pitre@linaro.org>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      2f27bf83