From: "acme@kernel.org" <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: "Liang, Kan" <kan.liang@intel.com>,
"jolsa@kernel.org" <jolsa@kernel.org>,
"ak@linux.intel.com" <ak@linux.intel.com>,
"namhyung@kernel.org" <namhyung@kernel.org>,
"eranian@google.com" <eranian@google.com>,
"Hunter, Adrian" <adrian.hunter@intel.com>,
"dsahern@gmail.com" <dsahern@gmail.com>,
"a.p.zijlstra@chello.nl" <a.p.zijlstra@chello.nl>,
"mingo@redhat.com" <mingo@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] perf,tools: check and re-organize evsel cpu maps
Date: Tue, 30 Jun 2015 11:42:25 -0300 [thread overview]
Message-ID: <20150630144225.GD5888@kernel.org> (raw)
In-Reply-To: <20150630135449.GB2789@krava.brq.redhat.com>
Em Tue, Jun 30, 2015 at 03:54:49PM +0200, Jiri Olsa escreveu:
> On Tue, Jun 30, 2015 at 01:42:49PM +0000, Liang, Kan wrote:
> > > > +static int perf_evlist__check_evsel_cpus(struct perf_evlist *evlist,
> > > > +struct perf_evsel *evsel) {
> > > > + const struct cpu_map *cpus = evlist->cpus;
> > > > + const int ncpus = cpu_map__nr(evlist->cpus);
> > > > + int j = 0, cpu_nr = 0, tmp = 0;
> > > > + int i;
> > > > +
> > > > + /* ensure we process id in increasing order */
> > > > + qsort(evlist->cpus->map, evlist->cpus->nr, sizeof(int), cmp_ids);
> > >
> > > wouldn't sorting maps affect some other code?
> > >
> >
> > I didn't find any bad effect after sorting the maps.
> > Any codes I need to check?
>
> I dont think so, but I'm not sure either.. thats why I asked ;-)
>
> I guess any code dealing with cpu maps.. it might affect
> perf stat output.. but it looks sorted now anyway ;-)
> I dont think it's an issue
Is this being done at cpu_map__new time, i.e. when we first parse it?
That way any assumption about repositioning gets out of the way.
- Arnaldo
next prev parent reply other threads:[~2015-06-30 14:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 19:55 [PATCH 1/2] perf,tools: get correct cpu id for print_aggr kan.liang
2015-06-29 19:55 ` [PATCH 2/2] perf,tools: check and re-organize evsel cpu maps kan.liang
2015-06-30 12:14 ` Jiri Olsa
2015-06-30 13:42 ` Liang, Kan
2015-06-30 13:54 ` Jiri Olsa
2015-06-30 14:42 ` acme [this message]
2015-07-02 16:08 ` Jiri Olsa
2015-06-30 15:52 ` Stephane Eranian
2015-06-30 16:45 ` Liang, Kan
2015-07-02 16:10 ` Jiri Olsa
2015-06-30 6:46 ` [PATCH 1/2] perf,tools: get correct cpu id for print_aggr Jiri Olsa
2015-06-30 13:24 ` Liang, Kan
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=20150630144225.GD5888@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@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