1. 07 8月, 2007 1 次提交
  2. 04 8月, 2007 1 次提交
  3. 01 8月, 2007 2 次提交
    • P
      sh: Fix SH-X3 FPU exception handling. · e0a3647f
      Paul Mundt 提交于
      SH-X3 has the FPU exceptions on different vectors completely,
      patch in do_fpu_state_restore() to the proper vectors.
      
      Results in a much happier userspace.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      e0a3647f
    • P
      sh: Fix lockdep debugging oops on SH-3/4. · c347d12c
      Paul Mundt 提交于
      In the SH-3/4 TLB access violation path we were enabling IRQs before
      the call in to trace_hardirqs_on(), which ended up triggering:
      
              if (DEBUG_LOCKS_WARN_ON(!irqs_disabled()))
                      return;
      
      in kernel/lockdep.c:2031. Fix this up by removing the early re-enable,
      we were already re-enabling IRQs post-trace_hardirqs_on() already, so
      the semantics are now as was initially intended.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      c347d12c
  4. 31 7月, 2007 1 次提交
  5. 26 7月, 2007 3 次提交
  6. 25 7月, 2007 2 次提交
  7. 22 7月, 2007 1 次提交
  8. 20 7月, 2007 16 次提交
  9. 18 7月, 2007 3 次提交
  10. 17 7月, 2007 1 次提交
    • H
      generic bug: use show_regs() instead of dump_stack() · 608e2619
      Heiko Carstens 提交于
      The current generic bug implementation has a call to dump_stack() in case a
      WARN_ON(whatever) gets hit.  Since report_bug(), which calls dump_stack(),
      gets called from an exception handler we can do better: just pass the
      pt_regs structure to report_bug() and pass it to show_regs() in case of a
      warning.  This will give more debug informations like register contents,
      etc...  In addition this avoids some pointless lines that dump_stack()
      emits, since it includes a stack backtrace of the exception handler which
      is of no interest in case of a warning.  E.g.  on s390 the following lines
      are currently always present in a stack backtrace if dump_stack() gets
      called from report_bug():
      
       [<000000000001517a>] show_trace+0x92/0xe8)
       [<0000000000015270>] show_stack+0xa0/0xd0
       [<00000000000152ce>] dump_stack+0x2e/0x3c
       [<0000000000195450>] report_bug+0x98/0xf8
       [<0000000000016cc8>] illegal_op+0x1fc/0x21c
       [<00000000000227d6>] sysc_return+0x0/0x10
      Acked-by: NJeremy Fitzhardinge <jeremy@goop.org>
      Acked-by: NHaavard Skinnemoen <hskinnemoen@atmel.com>
      Cc: Andi Kleen <ak@suse.de>
      Cc: Kyle McMartin <kyle@parisc-linux.org>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Paul Mundt <lethal@linux-sh.org>
      Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
      Signed-off-by: NHeiko Carstens <heiko.carstens@de.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      608e2619
  11. 16 7月, 2007 1 次提交
  12. 13 7月, 2007 1 次提交
    • P
      sh: Export div symbols for GCC 4.2 and ST GCC. · 2414b86d
      Paul Mundt 提交于
      GCC 4.2 can emit integer variants of the FP division routines, so
      these need to be exported in order to keep the modules happy.
      
      4.1.x versions of the ST compiler have these things backported,
      and so also generate these symbols (whereas vanilla gcc 4.1.x
      does not), so handle the __GNUC_STM_RELEASE__ case to accomodate
      updated versions of the 4.1.x toolchain.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      2414b86d
  13. 12 7月, 2007 2 次提交
  14. 20 6月, 2007 2 次提交
  15. 19 6月, 2007 1 次提交
  16. 18 6月, 2007 2 次提交