public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] tracing/function-graph-tracer: signal interrupts entry/exit points on outpout
Date: Mon, 08 Dec 2008 07:19:32 +0100	[thread overview]
Message-ID: <1228717172.23742.1.camel@twins> (raw)
In-Reply-To: <493C7058.4060709@gmail.com>

On Mon, 2008-12-08 at 01:54 +0100, Frederic Weisbecker wrote:
> Impact: provide interrupt detection on output
> 
> Suggested by Ingo.
> If a hardirq is raised, we want it to be signaled on output, so this patch
> adds two arrows on the output to find entry and exit points of a hardirq.
> 
> Unfortunately, there are many interrupt entrypoints and these can be differents
> from one arch to another.
> 
> The approach here is one of the easiest, but doesn't shine by its scalability:
> we have an array of the interrupt entrypoints names that we compare with the
> symbol of the current traced function, if it matches, we draw the arrow.
> 
> Ie:
> 
>  1)               |                                unlock_buffer() {
>  1)               |                                  wake_up_bit() {
>  1)               |                                    bit_waitqueue() {
>  1)   0.872 us    |                                      __phys_addr();
>  1)   2.722 us    |                                    }
>  1)               |                                    __wake_up_bit() {
>  1)              ==>                                   __wake_up_bit() {
>  1)               |                                      do_IRQ() {

Would be much nicer, the current proposal is lost when grepping and adds
a weird visual break in the output.


  reply	other threads:[~2008-12-08  6:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-08  0:54 [PATCH 1/2] tracing/function-graph-tracer: signal interrupts entry/exit points on outpout Frederic Weisbecker
2008-12-08  6:19 ` Peter Zijlstra [this message]
2008-12-08 13:38   ` Frédéric Weisbecker
2008-12-08 13:47     ` Ingo Molnar
2008-12-08 13:51       ` Frédéric Weisbecker
2008-12-08 12:22 ` Ingo Molnar
2008-12-08 13:47   ` Frédéric Weisbecker
2008-12-08 14:03     ` Ingo Molnar

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=1228717172.23742.1.camel@twins \
    --to=a.p.zijlstra@chello.nl \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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