1. 23 5月, 2014 2 次提交
  2. 21 5月, 2014 12 次提交
  3. 27 3月, 2014 3 次提交
  4. 12 3月, 2014 1 次提交
  5. 14 1月, 2014 3 次提交
  6. 26 8月, 2013 1 次提交
  7. 21 8月, 2013 1 次提交
  8. 01 7月, 2013 1 次提交
  9. 09 5月, 2013 1 次提交
  10. 01 2月, 2013 2 次提交
  11. 14 12月, 2012 1 次提交
  12. 29 3月, 2012 1 次提交
  13. 08 12月, 2011 1 次提交
    • M
      MIPS Kprobes: Refactor branch emulation · d8d4e3ae
      Maneesh Soni 提交于
      This patch refactors MIPS branch emulation code so as to allow skipping
      delay slot instruction in case of branch likely instructions when branch is
      not taken. This is useful for keeping the code common for use cases like
      kprobes where one would like to handle the branch instructions keeping the
      delay slot instuction also in picture for branch likely instructions. Also
      allow emulation when instruction to be decoded is not at pt_regs->cp0_epc
      as in case of kprobes where pt_regs->cp0_epc points to the breakpoint
      instruction.
      
      The patch also exports the function for modules.
      Signed-off-by: NManeesh Soni <manesoni@cisco.com>
      Signed-off-by: NVictor Kamensky <kamensky@cisco.com>
      Cc: David Daney <david.daney@cavium.com>
      Cc: ananth@in.ibm.com
      Cc: linux-kernel@vger.kernel.org
      Cc: linux-mips@linux-mips.org
      Patchwork: https://patchwork.linux-mips.org/patch/2913/Signed-off-by: NRalf Baechle <ralf@linux-mips.org>
      d8d4e3ae
  14. 01 7月, 2011 1 次提交
    • P
      perf: Remove the nmi parameter from the swevent and overflow interface · a8b0ca17
      Peter Zijlstra 提交于
      The nmi parameter indicated if we could do wakeups from the current
      context, if not, we would set some state and self-IPI and let the
      resulting interrupt do the wakeup.
      
      For the various event classes:
      
        - hardware: nmi=0; PMI is in fact an NMI or we run irq_work_run from
          the PMI-tail (ARM etc.)
        - tracepoint: nmi=0; since tracepoint could be from NMI context.
        - software: nmi=[0,1]; some, like the schedule thing cannot
          perform wakeups, and hence need 0.
      
      As one can see, there is very little nmi=1 usage, and the down-side of
      not using it is that on some platforms some software events can have a
      jiffy delay in wakeup (when arch_irq_work_raise isn't implemented).
      
      The up-side however is that we can remove the nmi parameter and save a
      bunch of conditionals in fast paths.
      Signed-off-by: NPeter Zijlstra <a.p.zijlstra@chello.nl>
      Cc: Michael Cree <mcree@orcon.net.nz>
      Cc: Will Deacon <will.deacon@arm.com>
      Cc: Deng-Cheng Zhu <dengcheng.zhu@gmail.com>
      Cc: Anton Blanchard <anton@samba.org>
      Cc: Eric B Munson <emunson@mgebm.net>
      Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
      Cc: Paul Mundt <lethal@linux-sh.org>
      Cc: David S. Miller <davem@davemloft.net>
      Cc: Frederic Weisbecker <fweisbec@gmail.com>
      Cc: Jason Wessel <jason.wessel@windriver.com>
      Cc: Don Zickus <dzickus@redhat.com>
      Link: http://lkml.kernel.org/n/tip-agjev8eu666tvknpb3iaj0fg@git.kernel.orgSigned-off-by: NIngo Molnar <mingo@elte.hu>
      a8b0ca17
  15. 31 3月, 2011 1 次提交
  16. 15 3月, 2011 1 次提交
  17. 17 12月, 2010 1 次提交
  18. 30 10月, 2010 1 次提交
  19. 18 10月, 2010 1 次提交
  20. 05 8月, 2010 4 次提交