From: Abhishek Dubey <adubey@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: naveen.n.rao@linux.vnet.ibm.com, mpe@ellerman.id.au,
npiggin@gmail.com, peterz@infradead.org, mingo@redhat.com,
namhyung@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Abhishek Dubey <adubey@linux.ibm.com>
Subject: [PATCH] perf report: Calling available function for stats printing
Date: Fri, 28 Jun 2024 14:32:24 -0400 [thread overview]
Message-ID: <20240628183224.452055-1-adubey@linux.ibm.com> (raw)
For printing dump_trace, just use existing stats_print()
function.
Signed-off-by: Abhishek Dubey <adubey@linux.ibm.com>
---
tools/perf/builtin-report.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/tools/perf/builtin-report.c b/tools/perf/builtin-report.c
index 9718770facb5..6edc0d4ce6fb 100644
--- a/tools/perf/builtin-report.c
+++ b/tools/perf/builtin-report.c
@@ -1089,8 +1089,7 @@ static int __cmd_report(struct report *rep)
perf_session__fprintf_dsos(session, stdout);
if (dump_trace) {
- perf_session__fprintf_nr_events(session, stdout);
- evlist__fprintf_nr_events(session->evlist, stdout);
+ stats_print(rep);
return 0;
}
}
--
2.44.0
WARNING: multiple messages have this Message-ID (diff)
From: Abhishek Dubey <adubey@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: mark.rutland@arm.com, irogers@google.com, peterz@infradead.org,
adrian.hunter@intel.com, npiggin@gmail.com,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
alexander.shishkin@linux.intel.com, mingo@redhat.com,
jolsa@kernel.org, namhyung@kernel.org,
naveen.n.rao@linux.vnet.ibm.com,
Abhishek Dubey <adubey@linux.ibm.com>
Subject: [PATCH] perf report: Calling available function for stats printing
Date: Fri, 28 Jun 2024 14:32:24 -0400 [thread overview]
Message-ID: <20240628183224.452055-1-adubey@linux.ibm.com> (raw)
For printing dump_trace, just use existing stats_print()
function.
Signed-off-by: Abhishek Dubey <adubey@linux.ibm.com>
---
tools/perf/builtin-report.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/tools/perf/builtin-report.c b/tools/perf/builtin-report.c
index 9718770facb5..6edc0d4ce6fb 100644
--- a/tools/perf/builtin-report.c
+++ b/tools/perf/builtin-report.c
@@ -1089,8 +1089,7 @@ static int __cmd_report(struct report *rep)
perf_session__fprintf_dsos(session, stdout);
if (dump_trace) {
- perf_session__fprintf_nr_events(session, stdout);
- evlist__fprintf_nr_events(session->evlist, stdout);
+ stats_print(rep);
return 0;
}
}
--
2.44.0
next reply other threads:[~2024-06-28 18:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 18:32 Abhishek Dubey [this message]
2024-06-28 18:32 ` [PATCH] perf report: Calling available function for stats printing Abhishek Dubey
2024-06-28 18:35 ` Ian Rogers
2024-06-28 18:35 ` Ian Rogers
2024-07-03 21:53 ` Namhyung Kim
2024-07-03 21:53 ` Namhyung Kim
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=20240628183224.452055-1-adubey@linux.ibm.com \
--to=adubey@linux.ibm.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=namhyung@kernel.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=npiggin@gmail.com \
--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 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.