From: Jiri Olsa <jolsa@redhat.com>
To: Jin Yao <yao.jin@linux.intel.com>
Cc: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com,
Linux-kernel@vger.kernel.org, ak@linux.intel.com,
kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH v2 1/2] perf evsel: Create counts for collecting summary data
Date: Tue, 5 May 2020 01:50:59 +0200 [thread overview]
Message-ID: <20200504235059.GG1916255@krava> (raw)
In-Reply-To: <20200502020705.19295-2-yao.jin@linux.intel.com>
On Sat, May 02, 2020 at 10:07:04AM +0800, Jin Yao wrote:
> It would be useful to support the overall statistics for perf-stat
> interval mode. For example, report the summary at the end of
> "perf-stat -I" output.
>
> But since perf-stat can support many aggregation modes, such as
> --per-thread, --per-socket, -M and etc, we need a solution which
> doesn't bring much complexity.
>
> The idea is to create new 'evsel->summary_counts' which sums up the
> counts delta per interval. Before reporting the summary, we copy the
> data from evsel->summary_counts to evsel->counts, and next we just
> follow current code.
>
> v2:
> ---
> Rebase to perf/core branch
>
> Signed-off-by: Jin Yao <yao.jin@linux.intel.com>
> ---
> tools/perf/util/evsel.c | 10 ++++++++--
> tools/perf/util/evsel.h | 1 +
> tools/perf/util/stat.c | 20 ++++++++++++++++++++
> 3 files changed, 29 insertions(+), 2 deletions(-)
>
> diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c
> index a75bcb95bf23..abc503dd6eda 100644
> --- a/tools/perf/util/evsel.c
> +++ b/tools/perf/util/evsel.c
> @@ -1280,22 +1280,28 @@ void evsel__delete(struct evsel *evsel)
> void evsel__compute_deltas(struct evsel *evsel, int cpu, int thread,
> struct perf_counts_values *count)
> {
> - struct perf_counts_values tmp;
> + struct perf_counts_values tmp, *summary;
>
> - if (!evsel->prev_raw_counts)
> + if (!evsel->prev_raw_counts || !evsel->summary_counts)
> return;
>
> if (cpu == -1) {
> tmp = evsel->prev_raw_counts->aggr;
> evsel->prev_raw_counts->aggr = *count;
> + summary = &evsel->summary_counts->aggr;
> } else {
> tmp = *perf_counts(evsel->prev_raw_counts, cpu, thread);
> *perf_counts(evsel->prev_raw_counts, cpu, thread) = *count;
> + summary = perf_counts(evsel->summary_counts, cpu, thread);
shouldn't this be enough?
perf_counts(evsel->summary_counts, cpu, thread) = *count
without the code below.. and similar for aggr case
however I still wonder if we should count this in
perf_stat_process_counter and only for interval mode
> }
>
> count->val = count->val - tmp.val;
> count->ena = count->ena - tmp.ena;
> count->run = count->run - tmp.run;
> +
> + summary->val += count->val;
> + summary->ena += count->ena;
> + summary->run += count->run;
> }
>
> void perf_counts_values__scale(struct perf_counts_values *count,
> diff --git a/tools/perf/util/evsel.h b/tools/perf/util/evsel.h
> index 783246bf8d0d..430639c99d04 100644
> --- a/tools/perf/util/evsel.h
> +++ b/tools/perf/util/evsel.h
> @@ -46,6 +46,7 @@ struct evsel {
> char *filter;
> struct perf_counts *counts;
> struct perf_counts *prev_raw_counts;
> + struct perf_counts *summary_counts;
'sum_counts' might be better
jirka
> int idx;
> unsigned long max_events;
> unsigned long nr_events_printed;
> diff --git a/tools/perf/util/stat.c b/tools/perf/util/stat.c
> index 774468341851..c3fd008b4e84 100644
> --- a/tools/perf/util/stat.c
SNIP
next prev parent reply other threads:[~2020-05-04 23:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 2:07 [PATCH v2 0/2] perf stat: Support overall statistics for interval mode Jin Yao
2020-05-02 2:07 ` [PATCH v2 1/2] perf evsel: Create counts for collecting summary data Jin Yao
2020-05-04 23:50 ` Jiri Olsa [this message]
2020-05-06 8:19 ` Jin, Yao
2020-05-02 2:07 ` [PATCH v2 2/2] perf stat: Report summary for interval mode Jin Yao
2020-05-04 23:41 ` Jiri Olsa
2020-05-06 10:52 ` Jin, Yao
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=20200504235059.GG1916255@krava \
--to=jolsa@redhat.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@intel.com \
--cc=yao.jin@linux.intel.com \
/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