From: Adrian Hunter <adrian.hunter@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Andi Kleen <ak@linux.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH V3 0/3] perf tools: Support insn and insnlen in perf script
Date: Fri, 7 Oct 2016 16:42:24 +0300 [thread overview]
Message-ID: <1475847747-30994-1-git-send-email-adrian.hunter@intel.com> (raw)
Hi
I tidied Intel PT / BTS instruction buffer size usage, and took the liberty
of re-basing Andi's changes on top.
Adrian Hunter (1):
perf intel-pt/bts: Tidy instruction buffer size usage
Andi Kleen (2):
perf intel-pt/bts: Report instruction bytes and length in sample
perf tools: Support insn and insnlen in perf script
tools/perf/Documentation/perf-script.txt | 6 +++++-
tools/perf/builtin-script.c | 24 ++++++++++++++++++++--
tools/perf/util/event.h | 3 +++
tools/perf/util/intel-bts.c | 9 ++++----
.../perf/util/intel-pt-decoder/intel-pt-decoder.c | 2 ++
.../perf/util/intel-pt-decoder/intel-pt-decoder.h | 1 +
.../util/intel-pt-decoder/intel-pt-insn-decoder.c | 13 ++++++------
.../util/intel-pt-decoder/intel-pt-insn-decoder.h | 6 ++----
tools/perf/util/intel-pt-decoder/intel-pt-log.c | 4 ++--
tools/perf/util/intel-pt.c | 19 ++++++++++++-----
10 files changed, 61 insertions(+), 26 deletions(-)
Regards
Adrian
next reply other threads:[~2016-10-07 13:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 13:42 Adrian Hunter [this message]
2016-10-07 13:42 ` [PATCH V3 1/3] perf intel-pt/bts: Tidy instruction buffer size usage Adrian Hunter
2016-10-24 18:49 ` [tip:perf/core] " tip-bot for Adrian Hunter
2016-10-07 13:42 ` [PATCH V3 2/3] perf intel-pt/bts: Report instruction bytes and length in sample Adrian Hunter
2016-10-24 18:50 ` [tip:perf/core] " tip-bot for Andi Kleen
2016-10-07 13:42 ` [PATCH V3 3/3] perf tools: Support insn and insnlen in perf script Adrian Hunter
2016-10-24 18:50 ` [tip:perf/core] perf script: Support insn and insnlen tip-bot for Andi Kleen
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=1475847747-30994-1-git-send-email-adrian.hunter@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.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.