Add tracepoints to trace all system IRQs

This is a patch series aiming to trace all the system IRQs. The
tracepoints make it easier to find out when interrupts occur and how
much time is spent in kernel space versus user space.

Patches 1-5 add tracepoints to the generic kernel IRQ handlers to
benefit all the architectures, as suggested by Frederic. Patch#6 adds
trace events to trace all platform specific interrupt vectors which do
not have any generic handlers. This patch traces x86 IRQ vectors but can
be used by other architectures to trace their vectors too.


Vaibhav Nagarnaik (6):
  trace,x86: Add tracepoint to x86 timer interrupt handler
  trace: Add tracepoints to timer interrupt handlers
  trace: Add tracepoints to IRQ work run handler
  trace: Add tracepoints to reschedule interrupt handler
  trace: Add tracepoints to call function interrupt handlers
  trace,x86: Add platform_irq_vector_{entry|exit} trace events

 arch/x86/include/asm/irq_vectors.h       |   43 ++++
 arch/x86/kernel/apic/apic.c              |    4 +
 arch/x86/kernel/cpu/mcheck/therm_throt.c |    2 +
 arch/x86/kernel/cpu/mcheck/threshold.c   |    2 +
 arch/x86/kernel/irq.c                    |    2 +
 arch/x86/kernel/time.c                   |   15 +-
 arch/x86/kernel/traps.c                  |    2 +
 arch/x86/mm/tlb.c                        |    2 +
 include/trace/events/irq.h               |  370 ++++++++++++++++++++++++++++++
 kernel/hrtimer.c                         |    6 +
 kernel/irq_work.c                        |    4 +
 kernel/sched.c                           |    4 +
 kernel/smp.c                             |    5 +
 kernel/time/tick-broadcast.c             |   16 ++-
 kernel/time/tick-common.c                |    8 +-
 kernel/time/tick-sched.c                 |    4 +
 16 files changed, 480 insertions(+), 9 deletions(-)

-- 
1.7.3.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/