The irq_handler_entry tracepoint includes a "name" field, which allows
for easy identification and filtering of specific IRQs. However, the
irq_handler_exit tracepoint lacks this field, making it difficult to
pair corresponding entry and exit events for analysis.
Add the "name" field to irq_handler_exit to enable consistent tracking
and correlation of IRQ entry and exit events.
Signed-off-by: Wander Lairson Costa <wan...@redhat.com>
---
include/trace/events/irq.h | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/include/trace/events/irq.h b/include/trace/events/irq.h
index 837c1740d0d0..d705406daa37 100644
--- a/include/trace/events/irq.h
+++ b/include/trace/events/irq.h
@@ -88,16 +88,18 @@ TRACE_EVENT(irq_handler_exit,
TP_STRUCT__entry(
__field( int, irq )
+ __string( name, action->name )
__field( int, ret )
),
TP_fast_assign(
__entry->irq = irq;
+ __assign_str(name);
__entry->ret = ret;
),
- TP_printk("irq=%d ret=%s",
- __entry->irq, __entry->ret ? "handled" : "unhandled")
+ TP_printk("irq=%d name=%s ret=%s",
+ __entry->irq, __get_str(name), __entry->ret ? "handled" :
"unhandled")
);
DECLARE_EVENT_CLASS(softirq,
--
2.48.1
