From: Adrian Hunter <adrian.hunter@intel.com>
To: Andi Kleen <andi@firstfloor.org>, acme@kernel.org
Cc: linux-kernel@vger.kernel.org, jolsa@kernel.org,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 2/2] perf script: Support callindent
Date: Thu, 16 Jun 2016 15:41:05 +0300 [thread overview]
Message-ID: <57629E61.2000806@intel.com> (raw)
In-Reply-To: <1465599301-4240-2-git-send-email-andi@firstfloor.org>
On 11/06/16 01:55, Andi Kleen wrote:
> From: Andi Kleen <ak@linux.intel.com>
>
> 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.
I think there are advantages to having the decoder feed the thread stack so
I have tried to do that here:
http://marc.info/?l=linux-kernel&m=146608073131297
Please let me know what you think.
next prev parent reply other threads:[~2016-06-16 12:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 22:55 [PATCH 1/2] perf pt: Mark PT return events as "return" Andi Kleen
2016-06-10 22:55 ` [PATCH 2/2] perf script: Support callindent Andi Kleen
2016-06-16 12:41 ` Adrian Hunter [this message]
2016-06-16 12:38 ` [PATCH 1/2] perf pt: Mark PT return events as "return" Adrian Hunter
-- strict thread matches above, loose matches on Subject: below --
2016-05-20 19:52 Andi Kleen
2016-05-20 19:52 ` [PATCH 2/2] perf script: Support callindent Andi Kleen
2016-05-20 20:27 ` 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=57629E61.2000806@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=jolsa@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox