From: Adrian Hunter <adrian.hunter@intel.com>
To: Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: 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>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: [PATCH V5 22/25] perf tools: Hit all build ids when Instruction Tracing
Date: Sat, 7 Mar 2015 23:06:31 +0200 [thread overview]
Message-ID: <1425762394-29799-23-git-send-email-adrian.hunter@intel.com> (raw)
In-Reply-To: <1425762394-29799-1-git-send-email-adrian.hunter@intel.com>
We need to include all buildids when a perf.data
file contains Instruction Tracing data because we
do not decode the trace for that purpose because
it would take too long.
Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
---
tools/perf/builtin-buildid-list.c | 9 +++++++++
tools/perf/builtin-inject.c | 8 +++++++-
tools/perf/builtin-record.c | 10 +++++++++-
3 files changed, 25 insertions(+), 2 deletions(-)
diff --git a/tools/perf/builtin-buildid-list.c b/tools/perf/builtin-buildid-list.c
index ed3873b..d694309 100644
--- a/tools/perf/builtin-buildid-list.c
+++ b/tools/perf/builtin-buildid-list.c
@@ -69,6 +69,15 @@ static int perf_session__list_build_ids(bool force, bool with_hits)
session = perf_session__new(&file, false, &build_id__mark_dso_hit_ops);
if (session == NULL)
return -1;
+
+ /*
+ * We take all buildids when the file contains Instruction Tracing data
+ * because we do not decode the trace because it would take too long.
+ */
+ if (!perf_data_file__is_pipe(&file) &&
+ perf_header__has_feat(&session->header, HEADER_ITRACE))
+ with_hits = false;
+
/*
* in pipe-mode, the only way to get the buildids is to parse
* the record stream. Buildids are stored as RECORD_HEADER_BUILD_ID
diff --git a/tools/perf/builtin-inject.c b/tools/perf/builtin-inject.c
index 8932161..69e1747 100644
--- a/tools/perf/builtin-inject.c
+++ b/tools/perf/builtin-inject.c
@@ -27,6 +27,7 @@ struct perf_inject {
struct perf_session *session;
bool build_ids;
bool sched_stat;
+ bool have_itrace;
const char *input_name;
struct perf_data_file output;
u64 bytes_written;
@@ -115,6 +116,8 @@ static s64 perf_event__repipe_itrace(struct perf_tool *tool,
tool);
int ret;
+ inject->have_itrace = true;
+
if (!inject->output.is_pipe) {
off_t offset;
@@ -503,9 +506,12 @@ static int __cmd_inject(struct perf_inject *inject)
ret = perf_session__process_events(session, &inject->tool);
if (!file_out->is_pipe) {
- if (inject->build_ids)
+ if (inject->build_ids) {
perf_header__set_feat(&session->header,
HEADER_BUILD_ID);
+ if (inject->have_itrace)
+ dsos__hit_all(session);
+ }
/*
* The instruction traces have been removed and replaced with
* synthesized hardware events, so clear the feature flag.
diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
index caeaf43..cea5119 100644
--- a/tools/perf/builtin-record.c
+++ b/tools/perf/builtin-record.c
@@ -618,8 +618,16 @@ out_child:
if (!err && !file->is_pipe) {
rec->session->header.data_size += rec->bytes_written;
- if (!rec->no_buildid)
+ if (!rec->no_buildid) {
process_buildids(rec);
+ /*
+ * We take all buildids when the file contains
+ * Instruction Tracing data because we do not decode the
+ * trace because it would take too long.
+ */
+ if (rec->opts.full_itrace)
+ dsos__hit_all(rec->session);
+ }
perf_session__write_header(rec->session, rec->evlist, fd, true);
}
--
1.9.1
next prev parent reply other threads:[~2015-03-07 21:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 21:06 [PATCH V5 00/25] perf tools: Introduce an abstraction for " Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 01/25] perf header: Add Instruction Tracing feature Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 02/25] perf evlist: Add initial support for mmapping an Instruction Trace buffer Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 03/25] perf tools: Add user events for Instruction Tracing Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 04/25] perf tools: Add support for Instruction Trace recording Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 05/25] perf record: Add basic Instruction Tracing support Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 06/25] perf record: Extend -m option for Instruction Tracing mmap pages Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 07/25] perf tools: Add a user event for Instruction Tracing errors Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 08/25] perf session: Add hooks to allow transparent decoding of Instruction Tracing data Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 09/25] perf session: Add Instruction Tracing options Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 10/25] perf itrace: Add helpers for Instruction Tracing errors Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 11/25] perf itrace: Add helpers for queuing Instruction Tracing data Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 12/25] perf itrace: Add a heap for sorting Instruction Tracing queues Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 13/25] perf itrace: Add processing for Instruction Tracing events Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 14/25] perf itrace: Add a hashtable for caching decoded instructions Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 15/25] perf tools: Add member to struct dso for an instruction cache Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 16/25] perf script: Add Instruction Tracing support Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 17/25] perf script: Always allow fields 'addr' and 'cpu' for itrace Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 18/25] perf report: Add Instruction Tracing support Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 19/25] perf inject: Re-pipe Instruction Tracing events Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 20/25] perf inject: Add Instruction Tracing support Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 21/25] perf tools: Add Instruction Tracing index Adrian Hunter
2015-03-07 21:06 ` Adrian Hunter [this message]
2015-03-07 21:06 ` [PATCH V5 23/25] perf tools: Add build option NO_ITRACE to exclude Instruction Tracing Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 24/25] perf itrace: Add option to synthesize events for transactions Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 25/25] perf script: Add field option 'flags' to print sample flags Adrian Hunter
2015-03-11 15:55 ` [PATCH V5 00/25] perf tools: Introduce an abstraction for Instruction Tracing Adrian Hunter
2015-03-11 19:33 ` Arnaldo Carvalho de Melo
2015-03-12 20:51 ` Adrian Hunter
2015-03-12 20:57 ` Arnaldo Carvalho de Melo
2015-03-13 11:40 ` Adrian Hunter
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=1425762394-29799-23-git-send-email-adrian.hunter@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--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
Powered by JetHome