1. 07 Nov, 2005 7 commits
  2. 06 Nov, 2005 1 commit
  3. 01 Nov, 2005 1 commit
  4. 31 Oct, 2005 26 commits
  5. 30 Oct, 2005 1 commit
    • Hugh Dickins's avatar
      [PATCH] mm: i386 sh sh64 ready for split ptlock · 60ec5585
      Hugh Dickins authored
      
      
      Use pte_offset_map_lock, instead of pte_offset_map (or inappropriate
      pte_offset_kernel) and mm-wide page_table_lock, in sundry arch places.
      
      The i386 vm86 mark_screen_rdonly: yes, there was and is an assumption that the
      screen fits inside the one page table, as indeed it does.
      
      The sh __do_page_fault: which handles both kernel faults (without lock) and
      user mm faults (locked - though it set_pte without locking before).
      
      The sh64 flush_cache_range and helpers: which wrongly thought callers held
      page_table_lock before (only its tlb_start_vma did, and no longer does so);
      moved the flush loop down, and adjusted the large versus small range decision
      to consider a range which spans page tables as large.
      Signed-off-by: default avatarHugh Dickins <hugh@veritas.com>
      Acked-by: default avatarPaul Mundt <lethal@linux-sh.org>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      60ec5585
  6. 28 Oct, 2005 1 commit
  7. 22 Oct, 2005 1 commit
  8. 21 Oct, 2005 1 commit
    • Dave Jones's avatar
      [PATCH] cpufreq: fix pending powernow timer stuck condition · 0213df74
      Dave Jones authored
      
      
      AMD recently discovered that on some hardware, there is a race condition
      possible when a C-state change request goes onto the bus at the same
      time as a P-state change request.
      
      Both requests happen, but the southbridge hardware only acknowledges the
      C-state change.  The PowerNow! driver is then stuck in a loop, waiting
      for the P-state change acknowledgement.  The driver eventually times
      out, but can no longer perform P-state changes.
      
      It turns out the solution is to resend the P-state change, which the
      southbridge will acknowledge normally.
      
      Thanks to Johannes Winkelmann for reporting this and testing the fix.
      Signed-off-by: default avatarMark Langsdorf <mark.langsdorf@amd.com>
      Signed-off-by: default avatarDave Jones <davej@redhat.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      0213df74
  9. 10 Oct, 2005 1 commit