public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Tim Bird <tim.bird@am.sony.com>
Cc: "Uwe �" <u.kleine-koenig@pengutronix.de>,
	"linux kernel" <linux-kernel@vger.kernel.org>,
	"Steven Rostedt" <rostedt@goodmis.org>,
	"Ingo Molnar" <mingo@elte.hu>,
	linux-arm-kernel <linux-arm-kernel@lists.arm.linux.org.uk>,
	"Russell King" <rmk@arm.linux.org.uk>
Subject: Re: [PATCH] Add function graph tracer support for ARM
Date: Fri, 24 Apr 2009 00:15:17 +0200	[thread overview]
Message-ID: <20090423221516.GB5976@nowhere> (raw)
In-Reply-To: <49F0E284.2080104@am.sony.com>

On Thu, Apr 23, 2009 at 02:49:56PM -0700, Tim Bird wrote:
> Uwe � wrote:
> >> Signed-off-by: <tim.bird@am.sony.com>
> > According to Documentation/SubmittingPatches you need to provide your
> > real name in the S-o-b line.
> 
> OK -that's embarrassing - I'll fix this.
> scripts/checkpatch.pl didn't catch this.  I may look at adding
> something to checkpatch.pl to catch empty names.
> 
> > For the lazy of us, can you point me^Uus to some documentation how to
> > use the graph tracer?
> 
> It looks like Documentation/ftrace.txt is missing anything about
> function graph tracing.
> 
> Should I add a section?



There is already a section in Documentation/frace.txt as well in 2.6.30 :-)



> 
> Here are some quick steps:
> 
> $ mount -t debugfs none /debug
> $ cd /debug/tracing/
> $ cat available_tracers
> function_graph function sched_switch nop
> $ echo function_graph >current_tracer
> $ cat trace
> # tracer: function_graph
> #
> # CPU OVERHEAD/DURATION            FUNCTION CALLS
> # |   |        |                   |   |   |   |
>  ------------------------------------------
>  0)      --1       =>   events/-5
>  ------------------------------------------
> 
>  0)               |                activate_task() {
>  0)               |                  enqueue_task() {
>  0)               |                    enqueue_task_fair() {
>  0)               |                      update_curr() {
>  0)   0.000 us    |                        calc_delta_mine();
>  0)   0.000 us    |                        update_min_vruntime();
>  0) + 61.035 us   |                      }
>  0)   0.000 us    |                      place_entity();
>  0)   0.000 us    |                      __enqueue_entity();
>  0) + 91.552 us   |                    }
>  0) ! 122.070 us  |                  }
>  0) ! 152.588 us  |                }
>  0)               |                check_preempt_wakeup() {
>  0)   0.000 us    |                  update_curr();
>  0)   0.000 us    |                  wakeup_preempt_entity();
>  0) + 61.035 us   |                }
> 
> Clearly, my clock stinks, but that's a separate issue.


Oh, that's the first function graph trace from Arm I can see.
/me feels a bit moved...

Just one childish caprice...it would be nice to see a part of a
trace which shows specific Arm arch functions in the next changelog :-)


Thanks,
Frederic.


  reply	other threads:[~2009-04-23 22:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 18:08 [PATCH] Add function graph tracer support for ARM Tim Bird
2009-04-23 18:39 ` Uwe Kleine-König
2009-04-23 21:49   ` Tim Bird
2009-04-23 22:15     ` Frederic Weisbecker [this message]
2009-04-23 22:40       ` Tim Bird
2009-04-24  6:44     ` Uwe Kleine-König
2009-04-24 18:00       ` Tim Bird
2009-04-23 19:20 ` Frederic Weisbecker
2009-04-23 22:33   ` Tim Bird
2009-04-23 23:42     ` Frederic Weisbecker
2009-04-24  6:32     ` Uwe Kleine-König

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=20090423221516.GB5976@nowhere \
    --to=fweisbec@gmail.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rmk@arm.linux.org.uk \
    --cc=rostedt@goodmis.org \
    --cc=tim.bird@am.sony.com \
    --cc=u.kleine-koenig@pengutronix.de \
    /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