From: Jiri Olsa <jolsa@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: acme@kernel.org, jolsa@kernel.org, linux-kernel@vger.kernel.org,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 1/2] perf, tools, stat: Use xyarray dimensions to iterate fds
Date: Wed, 21 Feb 2018 15:33:11 +0100 [thread overview]
Message-ID: <20180221143311.GC2565@krava> (raw)
In-Reply-To: <20171006020029.13339-1-andi@firstfloor.org>
On Thu, Oct 05, 2017 at 07:00:28PM -0700, Andi Kleen wrote:
> From: Andi Kleen <ak@linux.intel.com>
>
> Now that the xyarray stores the dimensions we can use those
> to iterate over the FDs for a evsel.
>
> Signed-off-by: Andi Kleen <ak@linux.intel.com>
Acked-by: Jiri Olsa <jolsa@kernel.org>
thanks,
jirka
> ---
> tools/perf/builtin-stat.c | 11 +++++------
> 1 file changed, 5 insertions(+), 6 deletions(-)
>
> diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c
> index dd525417880a..3c697118e44b 100644
> --- a/tools/perf/builtin-stat.c
> +++ b/tools/perf/builtin-stat.c
> @@ -557,14 +557,13 @@ static int perf_stat_synthesize_config(bool is_pipe)
>
> #define FD(e, x, y) (*(int *)xyarray__entry(e->fd, x, y))
>
> -static int __store_counter_ids(struct perf_evsel *counter,
> - struct cpu_map *cpus,
> - struct thread_map *threads)
> +static int __store_counter_ids(struct perf_evsel *counter)
> {
> int cpu, thread;
>
> - for (cpu = 0; cpu < cpus->nr; cpu++) {
> - for (thread = 0; thread < threads->nr; thread++) {
> + for (cpu = 0; cpu < xyarray__max_x(counter->fd); cpu++) {
> + for (thread = 0; thread < xyarray__max_y(counter->fd);
> + thread++) {
> int fd = FD(counter, cpu, thread);
>
> if (perf_evlist__id_add_fd(evsel_list, counter,
> @@ -584,7 +583,7 @@ static int store_counter_ids(struct perf_evsel *counter)
> if (perf_evsel__alloc_id(counter, cpus->nr, threads->nr))
> return -ENOMEM;
>
> - return __store_counter_ids(counter, cpus, threads);
> + return __store_counter_ids(counter);
> }
>
> static bool perf_evsel__should_store_id(struct perf_evsel *counter)
> --
> 2.13.6
>
next prev parent reply other threads:[~2018-02-21 14:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 2:00 [PATCH 1/2] perf, tools, stat: Use xyarray dimensions to iterate fds Andi Kleen
2017-10-06 2:00 ` [PATCH 2/2] perf, tools, stat: Reset ids counter when retrying events Andi Kleen
2017-10-06 3:36 ` Andi Kleen
2018-02-21 14:00 ` Arnaldo Carvalho de Melo
2018-02-21 14:39 ` Jiri Olsa
2018-02-21 14:31 ` Jiri Olsa
2018-02-21 14:33 ` Arnaldo Carvalho de Melo
2018-02-21 14:37 ` Jiri Olsa
2018-02-21 14:33 ` Jiri Olsa [this message]
2018-02-21 14:37 ` [PATCH 1/2] perf, tools, stat: Use xyarray dimensions to iterate fds Arnaldo Carvalho de Melo
2018-03-06 6:41 ` [tip:perf/core] perf " tip-bot for Andi Kleen
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=20180221143311.GC2565@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=jolsa@kernel.org \
--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