public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@gmail.com>,
	Paul Mackerras <paulus@samba.org>,
	Stephane Eranian <eranian@google.com>
Subject: [PATCH 0/7] perf tools: Add a thread stack for synthesizing call chains
Date: Thu, 30 Oct 2014 16:09:41 +0200	[thread overview]
Message-ID: <1414678188-14946-1-git-send-email-adrian.hunter@intel.com> (raw)

Hi

Here are the thread stack patches again.  Please let me
know if you want more explanation.

Changes:

	perf tools: Add a thread stack for synthesizing call chains
		Added some error returns
		Renamed PERF_FLAGS_ to PERF_IP_FLAGS_

	perf tools: Enhance the thread stack to output call/return data
		Expanded commit message
		Added more comments


Adrian Hunter (7):
      perf tools: Add a thread stack for synthesizing call chains
      perf tools: Add branch type to db export
      perf tools: Add branch_type and in_tx to Python export
      perf tools: Enhance the thread stack to output call/return data
      perf tools: Add call information to the database export API
      perf tools: Add call information to Python export
      perf tools: Defer export of comms that were not 'set'

 tools/perf/Makefile.perf                           |   2 +
 .../scripts/python/bin/export-to-postgresql-report |  15 +-
 tools/perf/scripts/python/export-to-postgresql.py  |  98 ++-
 tools/perf/util/db-export.c                        | 162 ++++-
 tools/perf/util/db-export.h                        |  21 +
 tools/perf/util/event.h                            |  26 +
 .../util/scripting-engines/trace-event-python.c    | 118 +++-
 tools/perf/util/thread-stack.c                     | 747 +++++++++++++++++++++
 tools/perf/util/thread-stack.h                     | 111 +++
 tools/perf/util/thread.c                           |   3 +
 tools/perf/util/thread.h                           |   3 +
 11 files changed, 1289 insertions(+), 17 deletions(-)
 create mode 100644 tools/perf/util/thread-stack.c
 create mode 100644 tools/perf/util/thread-stack.h


Regards
Adrian

             reply	other threads:[~2014-10-30 14:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-30 14:09 Adrian Hunter [this message]
2014-10-30 14:09 ` [PATCH 1/7] perf tools: Add a thread stack for synthesizing call chains 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
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=1414678188-14946-1-git-send-email-adrian.hunter@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=acme@kernel.org \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=jolsa@redhat.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