mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: tip-bot for Adrian Hunter <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: tglx@linutronix.de, hpa@zytor.com, mingo@kernel.org,
	acme@redhat.com, jolsa@redhat.com, adrian.hunter@intel.com,
	linux-kernel@vger.kernel.org
Subject: [tip:perf/core] perf session: Print a newline when dumping PERF_RECORD_FINISHED_ROUND
Date: Thu, 25 Jun 2015 00:57:20 -0700	[thread overview]
Message-ID: <tip-5531e16227cc18bc13b028a052a609a233b49c07@git.kernel.org> (raw)
In-Reply-To: <1435045969-15999-1-git-send-email-adrian.hunter@intel.com>

Commit-ID:  5531e16227cc18bc13b028a052a609a233b49c07
Gitweb:     http://git.kernel.org/tip/5531e16227cc18bc13b028a052a609a233b49c07
Author:     Adrian Hunter <adrian.hunter@intel.com>
AuthorDate: Tue, 23 Jun 2015 10:52:48 +0300
Committer:  Arnaldo Carvalho de Melo <acme@redhat.com>
CommitDate: Tue, 23 Jun 2015 18:21:43 -0300

perf session: Print a newline when dumping PERF_RECORD_FINISHED_ROUND

With 'perf report -D' the PERF_RECORD_FINISHED_ROUND event was printed
without a newline, resulting in:

	0x91a18 [0x8]: PERF_RECORD_FINISHED_ROUNDAggregated stats

Other events print their details, but PERF_RECORD_FINISHED_ROUND doesn't
have any so just add a print for a newline.

Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
Cc: Jiri Olsa <jolsa@redhat.com>
Link: http://lkml.kernel.org/r/1435045969-15999-1-git-send-email-adrian.hunter@intel.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
 tools/perf/util/session.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/tools/perf/util/session.c b/tools/perf/util/session.c
index aa482c1..aac1c4c 100644
--- a/tools/perf/util/session.c
+++ b/tools/perf/util/session.c
@@ -686,6 +686,8 @@ static int process_finished_round(struct perf_tool *tool __maybe_unused,
 				  union perf_event *event __maybe_unused,
 				  struct ordered_events *oe)
 {
+	if (dump_trace)
+		fprintf(stdout, "\n");
 	return ordered_events__flush(oe, OE_FLUSH__ROUND);
 }
 

      parent reply	other threads:[~2015-06-25  7:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23  7:52 [PATCH 1/2] perf tools: " Adrian Hunter
2015-06-23  7:52 ` [PATCH 2/2] perf tools: Print a newline before dumping Aggregated stats Adrian Hunter
2015-06-25  7:57   ` [tip:perf/core] " tip-bot for Adrian Hunter
2015-06-25  7:57 ` tip-bot for Adrian Hunter [this message]

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=tip-5531e16227cc18bc13b028a052a609a233b49c07@git.kernel.org \
    --to=tipbot@zytor.com \
    --cc=acme@redhat.com \
    --cc=adrian.hunter@intel.com \
    --cc=hpa@zytor.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    /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®