All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Jiri Olsa <jolsa@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC V2 3/3] perf script: Add callindent option
Date: Mon, 20 Jun 2016 16:50:52 -0700	[thread overview]
Message-ID: <20160620235052.GC25121@tassilo.jf.intel.com> (raw)
In-Reply-To: <1466151776-8738-1-git-send-email-adrian.hunter@intel.com>

On Fri, Jun 17, 2016 at 11:22:56AM +0300, Adrian Hunter wrote:
> Based on patches from Andi Kleen.
> 
> When printing PT instruction traces with perf script it is rather useful to
> see some indentation for the call tree. This patch adds a new callindent
> field to perf script that prints spaces for the function call stack depth.
> 
> We already have code to track the function call stack for PT, that we can
> reuse with minor modifications.
> 
> The resulting output is not quite as nice as ftrace yet, but a lot better
> than what was there before.
> 
> Note there are some corner cases when the thread stack gets code confused
> and prints incorrect indentation. Even with that it is fairly useful.
> 
> When displaying kernel code traces it is recommended to run as root, as
> otherwise perf doesn't understand the kernel addresses properly, and may
> not reset the call stack correctly on kernel boundaries.

I still would prefer to have call returns as event names instead of branches,
and not implicitly in the output, mainly so that it can be disabled if needed,
and give easier to read output.

The rest of the patch looks good to me. Perhaps you could just drop
the prefix for now.

-Andi

  reply	other threads:[~2016-06-20 23:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-16 12:34 [PATCH RFC 0/3] perf script: Add callindent option Adrian Hunter
2016-06-16 12:34 ` [PATCH RFC 1/3] perf: script: Fix documentation of '-f' when it should be '-F' Adrian Hunter
2016-06-16 19:53   ` Arnaldo Carvalho de Melo
2016-06-16 12:34 ` [PATCH RFC 2/3] perf auxtrace: Add option to feed branches to the thread stack Adrian Hunter
2016-06-16 12:34 ` [PATCH RFC 3/3] perf script: Add callindent option Adrian Hunter
2016-06-17  8:22   ` [PATCH RFC V2 " Adrian Hunter
2016-06-20 23:50     ` Andi Kleen [this message]
2016-06-16 16:37 ` [PATCH RFC 0/3] " Arnaldo Carvalho de Melo

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=20160620235052.GC25121@tassilo.jf.intel.com \
    --to=ak@linux.intel.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.