1. 25 1月, 2017 1 次提交
    • P
      sh: migrate exception table users off module.h and onto extable.h · d92280d1
      Paul Gortmaker 提交于
      These files were only including module.h for exception table
      related functions.  We've now separated that content out into its
      own file "extable.h" so now move over to that and avoid all the
      extra header content in module.h that we don't really need to compile
      these files.
      
      One uses "print_modules" so that prevents us removing module.h in
      that case, however.
      
      We also delete a duplicate prototype that doesn't need to exist, as
      it duplicates content in extable.h
      
      Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
      Cc: Rich Felker <dalias@libc.org>
      Cc: linux-sh@vger.kernel.org
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      d92280d1
  2. 21 1月, 2013 1 次提交
  3. 14 6月, 2012 1 次提交
  4. 29 3月, 2012 1 次提交
  5. 26 1月, 2010 1 次提交
    • P
      sh: Mass ctrl_in/outX to __raw_read/writeX conversion. · 9d56dd3b
      Paul Mundt 提交于
      The old ctrl in/out routines are non-portable and unsuitable for
      cross-platform use. While drivers/sh has already been sanitized, there
      is still quite a lot of code that is not. This converts the arch/sh/ bits
      over, which permits us to flag the routines as deprecated whilst still
      building with -Werror for the architecture code, and to ensure that
      future users are not added.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      9d56dd3b
  6. 12 11月, 2009 1 次提交
  7. 14 10月, 2009 1 次提交
  8. 01 9月, 2009 1 次提交
    • P
      sh: nmi_debug support. · 1e1030dc
      Paul Mundt 提交于
      This implements support for NMI debugging that was shamelessly copied
      from the avr32 port. A bit of special magic is needed in the interrupt
      exception path given that the NMI exception handler is stubbed in to the
      regular exception handling table despite being reported in INTEVT. So we
      mangle the lookup and kick off an EXPEVT-style exception dispatch from
      the INTEVT path for exceptions that do_IRQ() has no chance of handling.
      As a result, we also drop the evt2irq() conversion from the do_IRQ() path
      and just do it in assembly.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      1e1030dc
  9. 22 8月, 2009 1 次提交
  10. 21 8月, 2009 1 次提交
    • M
      sh: unwinder: Introduce UNWINDER_BUG() and UNWINDER_BUG_ON() · b344e24a
      Matt Fleming 提交于
      We can't assume that if we execute the unwinder code and the unwinder
      was already running that it has faulted. Clearly two kernel threads can
      invoke the unwinder at the same time and may be running simultaneously.
      
      The previous approach used BUG() and BUG_ON() in the unwinder code to
      detect whether the unwinder was incapable of unwinding the stack, and
      that the next available unwinder should be used instead. A better
      approach is to explicitly invoke a trap handler to switch unwinders when
      the current unwinder cannot continue.
      Signed-off-by: NMatt Fleming <matt@console-pimps.org>
      b344e24a
  11. 17 6月, 2009 1 次提交
  12. 09 5月, 2009 1 次提交
  13. 19 5月, 2008 1 次提交
  14. 28 1月, 2008 3 次提交
  15. 20 10月, 2007 1 次提交
  16. 21 9月, 2007 1 次提交
  17. 01 8月, 2007 1 次提交
  18. 18 7月, 2007 1 次提交
  19. 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
  20. 18 6月, 2007 1 次提交
  21. 08 6月, 2007 3 次提交
  22. 21 5月, 2007 2 次提交
  23. 09 5月, 2007 2 次提交
    • P
      sh: Convert to common die chain. · b118ca57
      Paul Mundt 提交于
      This went in immediately after SH added the die chain notifiers,
      so move over to that instead..
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      b118ca57
    • P
      sh: Fix PC adjustments for varying opcode length. · 53f983a9
      Paul Mundt 提交于
      There are a few different cases for figuring out how to
      size the instruction. We read in the instruction located
      at regs->pc - 4 when rewinding the opcode to figure out if
      there's a 32-bit opcode before the faulting instruction, with
      a default of a - 2 adjustment on a mismatch. In practice this
      works for the cases where pc - 4 is just another 16-bit opcode,
      or we happen to have a 32-bit and a 16-bit immediately
      preceeding the pc value.
      
      In the cases where we aren't rewinding, this is much less ugly..
      
      We also don't bother fixing up the places where we're explicitly
      dealing with 16-bit instructions, since this might lead to
      confusion regarding the encoding size possibilities on other
      CPU variants.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      53f983a9
  24. 07 5月, 2007 2 次提交
  25. 13 2月, 2007 2 次提交
  26. 12 12月, 2006 1 次提交
    • P
      sh: BUG() handling through trapa vector. · dc34d312
      Paul Mundt 提交于
      Previously we haven't been doing anything with verbose BUG() reporting,
      and we've been relying on the oops path for handling BUG()'s, which is
      rather sub-optimal.
      
      This switches BUG handling to use a fixed trapa vector (#0x3e) where we
      construct a small bug frame post trapa instruction to get the context
      right. This also makes it trivial to wire up a DIE_BUG for the atomic
      die chain, which we couldn't really do before.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      dc34d312
  27. 06 12月, 2006 5 次提交
  28. 19 10月, 2006 1 次提交
    • P
      sh: Fix exception_handling_table alignment. · 1f666587
      Paul Mundt 提交于
      With the recent change ripping out interrupt_table, explicit
      padding of the table was missing, causing bad things to happen
      when manually inserting handlers in to the table. This problem
      particularly showed up in relation to do_fpu_state_restore()
      which was inserted quite deeply in to the table and ended up
      scribbling over a slab object.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      1f666587