Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/linville/wirel...
[linux-2.6-block.git] / include / trace / events / irq.h
CommitLineData
d0b6e04a
LZ
1#undef TRACE_SYSTEM
2#define TRACE_SYSTEM irq
3
ea20d929 4#if !defined(_TRACE_IRQ_H) || defined(TRACE_HEADER_MULTI_READ)
af39241b
JB
5#define _TRACE_IRQ_H
6
af39241b 7#include <linux/tracepoint.h>
ea20d929
SR
8#include <linux/interrupt.h>
9
1d080d6c 10#define softirq_name(sirq) { sirq##_SOFTIRQ, #sirq }
5dd4de58
LZ
11#define show_softirq_name(val) \
12 __print_symbolic(val, \
13 softirq_name(HI), \
14 softirq_name(TIMER), \
15 softirq_name(NET_TX), \
16 softirq_name(NET_RX), \
17 softirq_name(BLOCK), \
18 softirq_name(BLOCK_IOPOLL), \
19 softirq_name(TASKLET), \
20 softirq_name(SCHED), \
21 softirq_name(HRTIMER), \
1d080d6c 22 softirq_name(RCU))
c2adae09 23
9ee1983c
JB
24/**
25 * irq_handler_entry - called immediately before the irq action handler
26 * @irq: irq number
27 * @action: pointer to struct irqaction
28 *
29 * The struct irqaction pointed to by @action contains various
30 * information about the handler, including the device name,
31 * @action->name, and the device id, @action->dev_id. When used in
32 * conjunction with the irq_handler_exit tracepoint, we can figure
33 * out irq handler latencies.
ea20d929 34 */
160031b5
SR
35TRACE_EVENT(irq_handler_entry,
36
ea20d929 37 TP_PROTO(int irq, struct irqaction *action),
160031b5 38
ea20d929 39 TP_ARGS(irq, action),
160031b5
SR
40
41 TP_STRUCT__entry(
42 __field( int, irq )
43 __string( name, action->name )
44 ),
45
46 TP_fast_assign(
47 __entry->irq = irq;
48 __assign_str(name, action->name);
49 ),
50
434a83c3 51 TP_printk("irq=%d name=%s", __entry->irq, __get_str(name))
160031b5 52);
ea20d929 53
9ee1983c
JB
54/**
55 * irq_handler_exit - called immediately after the irq action handler returns
56 * @irq: irq number
57 * @action: pointer to struct irqaction
58 * @ret: return value
59 *
60 * If the @ret value is set to IRQ_HANDLED, then we know that the corresponding
61 * @action->handler scuccessully handled this irq. Otherwise, the irq might be
62 * a shared irq line, or the irq was not handled successfully. Can be used in
63 * conjunction with the irq_handler_entry to understand irq handler latencies.
ea20d929
SR
64 */
65TRACE_EVENT(irq_handler_exit,
66
67 TP_PROTO(int irq, struct irqaction *action, int ret),
68
69 TP_ARGS(irq, action, ret),
70
71 TP_STRUCT__entry(
72 __field( int, irq )
73 __field( int, ret )
74 ),
75
76 TP_fast_assign(
77 __entry->irq = irq;
78 __entry->ret = ret;
79 ),
80
434a83c3 81 TP_printk("irq=%d ret=%s",
ea20d929
SR
82 __entry->irq, __entry->ret ? "handled" : "unhandled")
83);
84
c467307c 85DECLARE_EVENT_CLASS(softirq,
160031b5 86
ea20d929 87 TP_PROTO(struct softirq_action *h, struct softirq_action *vec),
160031b5 88
ea20d929 89 TP_ARGS(h, vec),
af39241b 90
160031b5
SR
91 TP_STRUCT__entry(
92 __field( int, vec )
160031b5
SR
93 ),
94
95 TP_fast_assign(
96 __entry->vec = (int)(h - vec);
160031b5
SR
97 ),
98
434a83c3 99 TP_printk("vec=%d [action=%s]", __entry->vec,
c2adae09 100 show_softirq_name(__entry->vec))
160031b5
SR
101);
102
c467307c
LZ
103/**
104 * softirq_entry - called immediately before the softirq handler
105 * @h: pointer to struct softirq_action
106 * @vec: pointer to first struct softirq_action in softirq_vec array
107 *
108 * The @h parameter, contains a pointer to the struct softirq_action
109 * which has a pointer to the action handler that is called. By subtracting
110 * the @vec pointer from the @h pointer, we can determine the softirq
111 * number. Also, when used in combination with the softirq_exit tracepoint
112 * we can determine the softirq latency.
113 */
114DEFINE_EVENT(softirq, softirq_entry,
115
116 TP_PROTO(struct softirq_action *h, struct softirq_action *vec),
117
118 TP_ARGS(h, vec)
119);
120
9ee1983c
JB
121/**
122 * softirq_exit - called immediately after the softirq handler returns
123 * @h: pointer to struct softirq_action
124 * @vec: pointer to first struct softirq_action in softirq_vec array
125 *
126 * The @h parameter contains a pointer to the struct softirq_action
127 * that has handled the softirq. By subtracting the @vec pointer from
128 * the @h pointer, we can determine the softirq number. Also, when used in
129 * combination with the softirq_entry tracepoint we can determine the softirq
130 * latency.
131 */
c467307c 132DEFINE_EVENT(softirq, softirq_exit,
160031b5 133
ea20d929 134 TP_PROTO(struct softirq_action *h, struct softirq_action *vec),
160031b5 135
c467307c 136 TP_ARGS(h, vec)
160031b5 137);
af39241b 138
a8d154b0
SR
139#endif /* _TRACE_IRQ_H */
140
141/* This part must be outside protection */
142#include <trace/define_trace.h>