1. 19 11月, 2008 1 次提交
  2. 23 10月, 2008 2 次提交
  3. 03 10月, 2008 1 次提交
  4. 11 9月, 2008 1 次提交
  5. 10 9月, 2008 1 次提交
    • N
      x86: some lock annotations for user copy paths · c10d38dd
      Nick Piggin 提交于
      copy_to/from_user and all its variants (except the atomic ones) can take a
      page fault and perform non-trivial work like taking mmap_sem and entering
      the filesyste/pagecache.
      
      Unfortunately, this often escapes lockdep because a common pattern is to
      use it to read in some arguments just set up from userspace, or write data
      back to a hot buffer. In those cases, it will be unlikely for page reclaim
      to get a window in to cause copy_*_user to fault.
      
      With the new might_lock primitives, add some annotations to x86. I don't
      know if I caught all possible faulting points (it's a bit of a maze, and I
      didn't really look at 32-bit). But this is a starting point.
      
      Boots and runs OK so far.
      Signed-off-by: NNick Piggin <npiggin@suse.de>
      Acked-by: NPeter Zijlstra <a.p.zijlstra@chello.nl>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      c10d38dd
  6. 23 7月, 2008 1 次提交
    • V
      x86: consolidate header guards · 77ef50a5
      Vegard Nossum 提交于
      This patch is the result of an automatic script that consolidates the
      format of all the headers in include/asm-x86/.
      
      The format:
      
      1. No leading underscore. Names with leading underscores are reserved.
      2. Pathname components are separated by two underscores. So we can
         distinguish between mm_types.h and mm/types.h.
      3. Everything except letters and numbers are turned into single
         underscores.
      Signed-off-by: NVegard Nossum <vegard.nossum@gmail.com>
      77ef50a5
  7. 09 7月, 2008 19 次提交
  8. 17 4月, 2008 1 次提交
  9. 04 2月, 2008 1 次提交
  10. 30 1月, 2008 1 次提交
  11. 11 10月, 2007 1 次提交
  12. 27 7月, 2007 1 次提交
  13. 15 3月, 2007 1 次提交
  14. 13 2月, 2007 1 次提交
    • A
      [PATCH] x86-64: Add __copy_from_user_nocache · 0812a579
      Andi Kleen 提交于
      This does user copies in fs write() into the page cache with write combining.
      This pushes the destination out of the CPU's cache, but allows higher bandwidth
      in some case.
      
      The theory is that the page cache data is usually not touched by the
      CPU again and it's better to not pollute the cache with it. Also it is a little
      faster.
      Signed-off-by: NAndi Kleen <ak@suse.de>
      0812a579
  15. 12 2月, 2007 1 次提交
  16. 26 1月, 2007 1 次提交
  17. 04 12月, 2006 1 次提交
  18. 30 9月, 2006 1 次提交
  19. 26 9月, 2006 3 次提交