public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Badhri Jagan Sridharan <badhri@google.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] tracing: Adds handler name to irq_handler_entry
Date: Thu, 07 May 2015 14:44:49 -0700	[thread overview]
Message-ID: <554BDCD1.8040508@google.com> (raw)
In-Reply-To: <20150505231932.1500a4ad@grimm.local.home>

Yes Steven.. It shouldn't be too difficult to find out the
handler for a specific device. But, I am looking
at some user space scripts that looks across different devices,
to data-mine interrupt stats. Although, the interrupt
numbers from the device tree change from one device to
another, if its the same device driver, the handlers
remain the same. So it gives me a good sense of
similar interrupts that fire.

If you think that its not to much of an overhead,I will send
a follow up patch to correct the spacing error that you
mentioned.

And did you really add Thomas to CC ?

Thanks,
Badhri

On 05/05/2015 08:19 PM, Steven Rostedt wrote:
> [ Added Thomas to the Cc, as he maintains interrupts ]
>
> On Tue,  5 May 2015 20:06:27 -0700
> Badhri Jagan Sridharan <badhri@google.com> wrote:
>
>> This patch includes the ISR function name to
>> irq_handler_entry trace point.
>
> It states what this patch does, but not why it does it.
>
> How much more difficult to map the handler to the interrupt?
>
> Just asking, I'm not sure I needed this, and I use this tracepoint all
> the time. But then again, I'm a bit of an tracing expert, and can add
> function graph tracing to see what is happening too. I shouldn't always
> be the judge on usefulness of added info here ;-)
>
>>
>> Signed-off-by: Badhri Jagan Sridharan <Badhri@google.com>
>> ---
>> Changelog since v1:
>> - fixed indentation
>>
>>   include/trace/events/irq.h | 5 ++++-
>>   1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/include/trace/events/irq.h b/include/trace/events/irq.h
>> index ff8f6c0..dd8918c 100644
>> --- a/include/trace/events/irq.h
>> +++ b/include/trace/events/irq.h
>> @@ -58,14 +58,17 @@ TRACE_EVENT(irq_handler_entry,
>>   	TP_STRUCT__entry(
>>   		__field(	int,	irq		)
>>   		__string(	name,	action->name	)
>> +		__field(	void*,	handler		)
>
> Nit, you need a space between 'void' and '*'.
>
> -- Steve
>
>>   	),
>>
>>   	TP_fast_assign(
>>   		__entry->irq = irq;
>>   		__assign_str(name, action->name);
>> +		__entry->handler = action->handler;
>>   	),
>>
>> -	TP_printk("irq=%d name=%s", __entry->irq, __get_str(name))
>> +	TP_printk("irq=%d name=%s handler=%pf",
>> +		  __entry->irq, __get_str(name), __entry->handler)
>>   );
>>
>>   /**
>

  reply	other threads:[~2015-05-07 21:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06  3:06 [PATCH v2] tracing: Adds handler name to irq_handler_entry Badhri Jagan Sridharan
2015-05-06  3:19 ` Steven Rostedt
2015-05-07 21:44   ` Badhri Jagan Sridharan [this message]
2015-05-07 21:54     ` Steven Rostedt
2015-05-07 22:49       ` Badhri Jagan Sridharan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=554BDCD1.8040508@google.com \
    --to=badhri@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox