From: Jiri Olsa <jolsa@redhat.com>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Namhyung Kim <namhyung@gmail.com>,
Paul Mackerras <paulus@samba.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 4/7] perf tools: Enhance the thread stack to output call/return data
Date: Mon, 3 Nov 2014 14:11:11 +0100 [thread overview]
Message-ID: <20141103131111.GB29906@krava.brq.redhat.com> (raw)
In-Reply-To: <1414678188-14946-5-git-send-email-adrian.hunter@intel.com>
On Thu, Oct 30, 2014 at 04:09:45PM +0200, Adrian Hunter wrote:
> Enhance the thread stack to output detailed information
> about paired calls and returns.
>
> The enhanced processing consumes sample information via
> thread_stack__process() and outputs information about
> paired calls / returns via a call-back. While the
> call-back makes it possible for the facility to be used
> by arbitrary tools, a subsequent patch will provide the
> information to Python scripting via the db-export
> interface.
>
> An important part of the call/return information is the
> call path which provides a structure that defines a context
> sensitive call graph.
>
> Note that there are now two ways to use the thread stack.
> For simply providing a call stack (like you would get
> from the perf record -g option) the interface consists of
> thread_stack__event() and thread_stack__sample(). Whereas
> the enhanced interface consists of call_return_processor__new()
> and thread_stack__process().
the interface seems pretty separated, with clear in and out values,
so it should be fairly easy to write automated tests for that ;-)
also given that there's no real user of this interface at the moment,
it'd be really nice to have ;-) anyway
Acked-by: Jiri Olsa <jolsa@kernel.org>
jirka
next prev parent reply other threads:[~2014-11-03 13:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 14:09 [PATCH 0/7] perf tools: Add a thread stack for synthesizing call chains Adrian Hunter
2014-10-30 14:09 ` [PATCH 1/7] " Adrian Hunter
2014-11-03 13:08 ` Jiri Olsa
2014-11-07 5:28 ` [tip:perf/core] " tip-bot for Adrian Hunter
2014-10-30 14:09 ` [PATCH 2/7] perf tools: Add branch type to db export Adrian Hunter
2014-11-07 5:28 ` [tip:perf/core] " tip-bot for Adrian Hunter
2014-10-30 14:09 ` [PATCH 3/7] perf tools: Add branch_type and in_tx to Python export Adrian Hunter
2014-11-07 5:28 ` [tip:perf/core] " tip-bot for Adrian Hunter
2014-10-30 14:09 ` [PATCH 4/7] perf tools: Enhance the thread stack to output call/return data Adrian Hunter
2014-11-03 13:11 ` Jiri Olsa [this message]
2014-11-07 5:28 ` [tip:perf/core] " tip-bot for Adrian Hunter
2014-10-30 14:09 ` [PATCH 5/7] perf tools: Add call information to the database export API Adrian Hunter
2014-11-07 5:29 ` [tip:perf/core] " tip-bot for Adrian Hunter
2014-10-30 14:09 ` [PATCH 6/7] perf tools: Add call information to Python export Adrian Hunter
2014-11-07 5:29 ` [tip:perf/core] " tip-bot for Adrian Hunter
2014-10-30 14:09 ` [PATCH 7/7] perf tools: Defer export of comms that were not 'set' Adrian Hunter
2014-11-07 5:29 ` [tip:perf/core] perf tools: Defer export of comms that were not ' set' tip-bot for Adrian Hunter
2014-11-03 21:13 ` [PATCH 0/7] perf tools: Add a thread stack for synthesizing call chains 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=20141103131111.GB29906@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@gmail.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.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
Powered by JetHome