1. 08 5月, 2013 1 次提交
  2. 02 5月, 2013 1 次提交
  3. 05 4月, 2013 1 次提交
  4. 17 2月, 2013 1 次提交
  5. 01 2月, 2013 1 次提交
  6. 14 12月, 2012 2 次提交
  7. 09 11月, 2012 1 次提交
  8. 14 9月, 2012 1 次提交
  9. 19 7月, 2012 1 次提交
  10. 07 7月, 2012 1 次提交
  11. 17 5月, 2012 1 次提交
  12. 29 3月, 2012 1 次提交
  13. 20 3月, 2012 1 次提交
  14. 08 12月, 2011 1 次提交
  15. 20 10月, 2011 1 次提交
  16. 26 7月, 2011 1 次提交
    • K
      MIPS: Add SYNC after cacheflush · d0023c4a
      Kevin Cernekee 提交于
      On processors with deep write buffers, it is likely that many cycles
      will pass between a CACHE instruction and the time the data actually
      gets written out to DRAM.  Add a SYNC instruction to ensure that the
      buffers get emptied before the flush functions return.
      
      Actual problem seen in the wild:
      
      1) dma_alloc_coherent() allocates cached memory
      
      2) memset() is called to clear the new pages
      
      3) dma_cache_wback_inv() is called to flush the zero data out to memory
      
      4) dma_alloc_coherent() returns an uncached (kseg1) pointer to the
      freshly allocated pages
      
      5) Caller writes data through the kseg1 pointer
      
      6) Buffered writeback data finally gets flushed out to DRAM
      
      7) Part of caller's data is inexplicably zeroed out
      
      This patch adds SYNC between steps 3 and 4, which fixed the problem.
      Signed-off-by: NKevin Cernekee <cernekee@gmail.com>
      Cc: linux-mips@linux-mips.org
      Cc: linux-kernel@vger.kernel.org
      Patchwork: 
      Signed-off-by: NRalf Baechle <ralf@linux-mips.org>
      d0023c4a
  17. 19 5月, 2011 1 次提交
  18. 11 5月, 2011 1 次提交
    • R
      MIPS: c-r4k: Fix GCC 4.6.0 build error · 71271aab
      Ralf Baechle 提交于
        CC      arch/mips/mm/c-r4k.o
      arch/mips/mm/c-r4k.c: In function 'probe_scache':
      arch/mips/mm/c-r4k.c:1078:6: error: variable 'tmp' set but not used [-Werror=unused-but-set-variable]
      cc1: all warnings being treated as errors
      
      Older GCC versions didn't warn about the unused variable tmp because it was
      getting initialized.
      Signed-off-by: NRalf Baechle <ralf@linux-mips.org>
      71271aab
  19. 06 4月, 2011 1 次提交
  20. 30 10月, 2010 2 次提交
  21. 25 6月, 2009 1 次提交
  22. 17 6月, 2009 1 次提交
  23. 14 5月, 2009 1 次提交
  24. 30 3月, 2009 1 次提交
    • M
      MIPS: Alchemy: unify CPU model constants. · 270717a8
      Manuel Lauss 提交于
      This patch removes the various CPU_AU1??? model constants in favor of
      a single CPU_ALCHEMY one.
      
      All currently existing Alchemy models are identical in terms of cpu
      core and cache size/organization.  The parts of the mips kernel which
      need to know the exact CPU revision extract it from the c0_prid register
      already; and finally nothing else in-tree depends on those any more.
      
      Should a new variant with slightly different "company options" and/or
      "processor revision" bits in c0_prid appear, it will be supported
      immediately (minus an exact model string in cpuinfo).
      Signed-off-by: NManuel Lauss <mano@roarinelk.homelinux.net>
      Signed-off-by: NRalf Baechle <ralf@linux-mips.org>
      270717a8
  25. 24 3月, 2009 1 次提交
  26. 31 1月, 2009 1 次提交
  27. 06 9月, 2008 1 次提交
  28. 26 6月, 2008 1 次提交
  29. 16 6月, 2008 2 次提交
  30. 29 4月, 2008 2 次提交
  31. 08 4月, 2008 1 次提交
  32. 12 3月, 2008 1 次提交
  33. 20 2月, 2008 1 次提交
    • R
      [MIPS] Handle I-cache coherency in flush_cache_range() · 2eaa7ec2
      Ralf Baechle 提交于
      So far flush_cache_range() did't consider the I-cache largely because it
      did rarely ever matter to real world code.  This was working primarily
      because normally code and data are don't share the same pages - with the
      exception of MIPS16 code which uses address constants embedded between
      the code.   The following sequence of events may break the code:
      
       o MIPS16 executable being loaded
       o dynamic linker relocates the address constants embedded into the code:
       o   Uses mprotect(2) to make code pages PROT_READ|PROT_WRITE
       o   Performs the actual relocations by writing to the pages which likely
           are COW.  Because no PROT_EXEC is set I-cache coherence will not be
           considered.
       o   Uses mprotect(2) to switch code pages back to PROT_READ|PROT_EXEC.
           This results in a call to flush_cache_range() which also does not
           consider I-caches.
       o => executing the page just having been relocated may now result in the
         I-cache getting refilled with stale data from memory.
      Signed-off-by: NRalf Baechle <ralf@linux-mips.org>
      2eaa7ec2
  34. 03 2月, 2008 1 次提交
  35. 29 1月, 2008 2 次提交