From: Adrian Hunter <adrian.hunter@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@redhat.com>
Subject: [PATCH 2/2] perf tools: Print a newline before dumping Aggregated stats
Date: Tue, 23 Jun 2015 10:52:49 +0300 [thread overview]
Message-ID: <1435045969-15999-2-git-send-email-adrian.hunter@intel.com> (raw)
In-Reply-To: <1435045969-15999-1-git-send-email-adrian.hunter@intel.com>
When dumping events with 'perf report -D' the event print
always starts with a newline (see dump_event()). Do the
same with the "Aggregated stats" print so that it is not
jammed up against the last event print.
Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
---
tools/perf/util/session.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/util/session.c b/tools/perf/util/session.c
index aac1c4cee1e8..b5549b58bb2b 100644
--- a/tools/perf/util/session.c
+++ b/tools/perf/util/session.c
@@ -1728,7 +1728,7 @@ size_t perf_session__fprintf_nr_events(struct perf_session *session, FILE *fp)
if (perf_header__has_feat(&session->header, HEADER_AUXTRACE))
msg = " (excludes AUX area (e.g. instruction trace) decoded / synthesized events)";
- ret = fprintf(fp, "Aggregated stats:%s\n", msg);
+ ret = fprintf(fp, "\nAggregated stats:%s\n", msg);
ret += events_stats__fprintf(&session->evlist->stats, fp);
return ret;
--
1.9.1
next prev parent reply other threads:[~2015-06-23 7:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 7:52 [PATCH 1/2] perf tools: Print a newline when dumping PERF_RECORD_FINISHED_ROUND Adrian Hunter
2015-06-23 7:52 ` Adrian Hunter [this message]
2015-06-25 7:57 ` [tip:perf/core] perf tools: Print a newline before dumping Aggregated stats tip-bot for Adrian Hunter
2015-06-25 7:57 ` [tip:perf/core] perf session: Print a newline when dumping PERF_RECORD_FINISHED_ROUND tip-bot for 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=1435045969-15999-2-git-send-email-adrian.hunter@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=jolsa@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®