[PATCH v2] trace/events: add chip name and hwirq to irq entry tracepoint
ankgupta at codeaurora.org
Tue Jun 23 08:16:39 PDT 2015
> On Mon, 22 Jun 2015, Ankit Gupta wrote:
>> Add chip name and hw-irq number to the trace_irq_handler_entry()
>> tracepoint. When tracing interrupt events the chip-name and hw-irq
>> numbers are stable and known in advance. This makes them a better
>> choice as a filtering criteria for the trace buffer dump. On the
>> flipside, the os-irq numbers are dynamically allocated which makes
>> them difficult to use for the same purpose.
>> Dump messages will look like:
>> ...irq_handler_entry: irq=22 name=msm_serial0 domain=GIC hwirq=140
> I can't see the domain name being captured/printed in the code below.
>> - TP_printk("irq=%d name=%s", __entry->irq, __get_str(name))
>> + TP_printk("irq=%d name=%s chip_name=%s hwirq=%ld", __entry->irq,
>> + __get_str(name), show_chip_name(__entry->irq),
>> + show_hwirq(__entry->irq))
Thanks Thomas for your comment. Its actually printing a chipname and not
the domain. Will correct the dump message in the next patch. It will print
...irq_handler_entry: irq=22 name=msm_serial0 Chip=GIC hwirq=140
> To unsubscribe from this list: send the line "unsubscribe linux-arm-msm"
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
More information about the linux-arm-kernel