1. 03 Apr, 2019 3 commits
    • Jan Kiszka's avatar
      ipipe: Fix output layout of tracer · 432d2adc
      Jan Kiszka authored and Philippe Gerum's avatar Philippe Gerum committed
      
      
      A long time ago (probably in 2.6-times), someone converted spaces to
      tabs, shuffling the layout around this way, and by forgetting to account
      for the multi-domain removal.
      Signed-off-by: Jan Kiszka's avatarJan Kiszka <jan.kiszka@siemens.com>
      432d2adc
    • Jan Kiszka's avatar
      ipipe: Fix panic output of tracer · 4e5bb6a4
      Jan Kiszka authored and Philippe Gerum's avatar Philippe Gerum committed
      
      
      Since 4.9, we need to declare continued lines via KERN_CONT.
      Signed-off-by: Jan Kiszka's avatarJan Kiszka <jan.kiszka@siemens.com>
      4e5bb6a4
    • Philippe Gerum's avatar
      ipipe: add latency tracer · 798079bc
      Philippe Gerum authored
      The latency tracer is a variant of ftrace's 'function' tracer
      providing detailed information about the current interrupt state at
      each function entry (i.e. virtual interrupt flag and CPU interrupt
      disable bit). This commit introduces the generic tracer code, which
      builds upon the regular ftrace API.
      
      The arch-specific code should provide for ipipe_read_tsc(), a helper
      routine returning a 64bit monotonic time value for timestamping
      purpose. HAVE_IPIPE_TRACER_SUPPORT should be selected by the
      arch-specific code for enabling the tracer, which in turn makes
      CONFIG_IPIPE_TRACE available from the Kconfig interface.
      798079bc