An error occurred fetching the project authors.
  1. 08 Apr, 2004 1 commit
  2. 01 Oct, 2003 1 commit
    • Andrew Morton's avatar
      [PATCH] memory writeback/invalidation fixes · b2dd8674
      Andrew Morton authored
      From: "David S. Miller" <davem@redhat.com>
      
      This attempts to take care of 2 of the MM todos I had on
      my backlog:
      
      1) Zap the stupid flush_cache_all() thing with more meaningful
         interfaces.
      
      2) Resolve the ptrace user page access issues, first stage.
      
      The "first stage" mentioned for #2 is simply creating the
      user page accesor interfaces.  The next stage needs to be
      mucking with get_user_pages() so that we can control when
      the flush_dcache_page() occurs.  Then we:
      
      1) For every platform where flush_dcache_page() is a non-nop
         add a call to the beginning of copy_{from,to}_user_page().
      2) Make access_process_vm() set the "no dcache flush" bit in
         it's call to get_user_pages().
      
      The idea also was that we'd consolidate the write etc. boolean
      args passed to get_user_pages() into flag bits too.
      
      But at least with the below, we can delete that reminder FIXME
      comment from kernel/ptrace.c, the platforms have the necessary
      tools and just need to make use of it :)
      
      As a bonus I noticed that VMALLOC_VMADDR() did absolutely nothing.
      
      After all of this I only have 1 real TODO left, and that's dealing
      with the SMP TLB/pte invalidation stuff, very low priority until
      someone starts doing more work with sparc32/SMP in 2.6.x :)
      b2dd8674
  3. 21 Nov, 2002 1 commit
    • Russell King's avatar
      [ARM] Fix ARM module support · fbbe4a70
      Russell King authored
      This cset allows ARM modules to work again.  The solution was
      suggested by Andi Kleen.
      
      We shrink the available user space size by 16MB, thereby opening up
      a window in virtual memory space between user space and the kernel
      direct mapped RAM.  We place modules into this space, and, since the
      kernel image is always at the bottom of kernel direct mapped RAM, we
      can be assured that any 24-bit PC relocations (which have a range
      of +/- 32MB) will always be able to reach the kernel.
      fbbe4a70
  4. 05 Feb, 2002 2 commits
    • Linus Torvalds's avatar
      v2.4.13.1 -> v2.4.13.2 · 4fd9cc9e
      Linus Torvalds authored
        - Alan Cox: more merging
        - Alexander Viro: block device module race fixes
        - Richard Henderson: mmap for 32-bit alpha personality
        - Jeff Garzik: 8139 and natsemi update
      4fd9cc9e
    • Linus Torvalds's avatar
      v2.4.2.1 -> v2.4.2.2 · 44e8778c
      Linus Torvalds authored
        - Jens Axboe: fix loop device deadlocks
        - Greg KH: USB updates
        - Alan Cox: continued merging
        - Tim Waugh: parport and documentation updates
        - Cort Dougan: PowerPC merge
        - Jeff Garzik: network driver updates
        - Justin Gibbs: new and much improved aic7xxx driver 6.1.5
      44e8778c