1. 05 12月, 2009 1 次提交
  2. 04 12月, 2009 1 次提交
  3. 06 11月, 2009 1 次提交
    • C
      x86: Make sure get_user_desc() doesn't sign extend. · 2c75910f
      Chris Lalancette 提交于
      The current implementation of get_user_desc() sign extends the return
      value because of integer promotion rules.  For the most part, this
      doesn't matter, because the top bit of base2 is usually 0.  If, however,
      that bit is 1, then the entire value will be 0xffff...  which is
      probably not what the caller intended.
      
      This patch casts the entire thing to unsigned before returning, which
      generates almost the same assembly as the current code but replaces the
      final "cltq" (sign extend) with a "mov %eax %eax" (zero-extend).  This
      fixes booting certain guests under KVM.
      Signed-off-by: NChris Lalancette <clalance@redhat.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      2c75910f
  4. 04 11月, 2009 4 次提交
  5. 03 11月, 2009 1 次提交
  6. 02 11月, 2009 2 次提交
  7. 29 10月, 2009 1 次提交
  8. 28 10月, 2009 1 次提交
  9. 27 10月, 2009 1 次提交
  10. 26 10月, 2009 3 次提交
  11. 23 10月, 2009 1 次提交
  12. 21 10月, 2009 1 次提交
  13. 20 10月, 2009 1 次提交
  14. 16 10月, 2009 6 次提交
  15. 15 10月, 2009 2 次提交
  16. 14 10月, 2009 2 次提交
  17. 13 10月, 2009 3 次提交
  18. 12 10月, 2009 3 次提交
  19. 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
  20. 09 10月, 2009 2 次提交
  21. 08 10月, 2009 1 次提交
    • A
      x86, timers: Check for pending timers after (device) interrupts · 9bcbdd9c
      Arjan van de Ven 提交于
      Now that range timers and deferred timers are common, I found a
      problem with these using the "perf timechart" tool. Frans Pop also
      reported high scheduler latencies via LatencyTop, when using
      iwlagn.
      
      It turns out that on x86, these two 'opportunistic' timers only get
      checked when another "real" timer happens. These opportunistic
      timers have the objective to save power by hitchhiking on other
      wakeups, as to avoid CPU wakeups by themselves as much as possible.
      
      The change in this patch runs this check not only at timer
      interrupts, but at all (device) interrupts. The effect is that:
      
       1) the deferred timers/range timers get delayed less
      
       2) the range timers cause less wakeups by themselves because
          the percentage of hitchhiking on existing wakeup events goes up.
      
      I've verified the working of the patch using "perf timechart", the
      original exposed bug is gone with this patch. Frans also reported
      success - the latencies are now down in the expected ~10 msec
      range.
      Signed-off-by: NArjan van de Ven <arjan@linux.intel.com>
      Tested-by: NFrans Pop <elendil@planet.nl>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Cc: Peter Zijlstra <peterz@infradead.org>
      Cc: Mike Galbraith <efault@gmx.de>
      LKML-Reference: <20091008064041.67219b13@infradead.org>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      9bcbdd9c
  22. 04 10月, 2009 1 次提交