mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: mingo@elte.hu, rostedt@goodmis.org, fweisbec@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCHv5 0/4] tracing: function graph output for preempt/irqs-off tracers
Date: Thu,  1 Apr 2010 17:37:05 +0200	[thread overview]
Message-ID: <1270136229-15263-1-git-send-email-jolsa@redhat.com> (raw)

hi,

ok, saga continues ;)

I'm sending reworked version of the graph output support for
preemptirqsoff/preemptoff/irqsoff tracers.

v5:
- function graph events are back in game
- changed function graph tracer interface to be able to
  pass custom tracer flags
- changed calls to trace_function to trace graph records
  when the display-graph otion is enabled.  As function tracer
  and graph tracer have different spacing during the record
  output, this way it looks better, and the info stays.

  This could be also done via TRACE_PRINT, then it'd be displayed
  as comment.. I chose the first way, though it could be easily
  changed.

v4:
- fixed header to display all the info as for
  current irqsoff tracer
- fixed reset of the max_tr buffer during the
  display-graph switch

v3:
- the function_graph tracer should have the same output
  as current version even with events enabled,
  unless I missed something again ;)
- I gave up the idea of function_graph events,
  since it was unsuitable for outputing other
  events as comments "/* */"
- I'm not including the raw function_graph for now


attached patches:
- 1/4 adding ftrace events for graph tracer
- 2/4 graph tracer - adding support for passing flags to ouput functions
- 3/4 graph output support for irqsoff tracer
- 4/4 graph output support for preemptirqsoff/preemptoff tracers


plz let me know what you think

wbr,
jirka
---
 kernel/trace/trace.c                 |   35 +++--
 kernel/trace/trace.h                 |   27 +++-
 kernel/trace/trace_functions_graph.c |  164 +++++++++++++--------
 kernel/trace/trace_irqsoff.c         |  267 ++++++++++++++++++++++++++++++++--
 4 files changed, 408 insertions(+), 85 deletions(-)

             reply	other threads:[~2010-04-01 16:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-01 15:37 Jiri Olsa [this message]
2010-04-01 15:37 ` [PATCHv5 1/4] tracing: adding ftrace events for graph tracer Jiri Olsa
2010-04-01 15:37 ` [PATCHv5 2/4] tracing: graph tracer - adding support for passing flags to ouput functions Jiri Olsa
2010-04-01 15:37 ` [PATCHv5 3/4] tracing: graph output support for irqsoff tracer Jiri Olsa
2010-04-01 17:32   ` Frederic Weisbecker
2010-04-01 15:37 ` [PATCHv5 4/4] tracing: graph output support for preemptirqsoff/preemptoff tracers Jiri Olsa

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=1270136229-15263-1-git-send-email-jolsa@redhat.com \
    --to=jolsa@redhat.com \
    --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

all inboxes | Powered by JetHome®