From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: kan.liang@intel.com, jolsa@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] perf,tools: open event on evsel cpus and threads
Date: Mon, 31 Aug 2015 17:31:15 -0300 [thread overview]
Message-ID: <20150831203115.GI4423@kernel.org> (raw)
In-Reply-To: <20150821135436.GD27650@krava.brq.redhat.com>
Em Fri, Aug 21, 2015 at 03:54:36PM +0200, Jiri Olsa escreveu:
> On Fri, Aug 21, 2015 at 02:23:14AM -0400, kan.liang@intel.com wrote:
> > From: Kan Liang <kan.liang@intel.com>
> >
> > evsel may have different cpus and threads as evlist's.
> > Use it's own cpus and threads, when open evsel in perf record.
>
> Acked-by: Jiri Olsa <jolsa@kernel.org>
Applying, I wonder if this isn't affecting other tools as well... And
also perf_evlist__open(), that has to be fixed as well, right?
- Arnaldo
> thanks,
> jirka
>
> >
> > Signed-off-by: Kan Liang <kan.liang@intel.com>
> > ---
> > tools/perf/builtin-record.c | 2 +-
> > tools/perf/util/evlist.c | 4 ++++
> > 2 files changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
> > index 25cf6b4..a0178bf 100644
> > --- a/tools/perf/builtin-record.c
> > +++ b/tools/perf/builtin-record.c
> > @@ -279,7 +279,7 @@ static int record__open(struct record *rec)
> >
> > evlist__for_each(evlist, pos) {
> > try_again:
> > - if (perf_evsel__open(pos, evlist->cpus, evlist->threads) < 0) {
> > + if (perf_evsel__open(pos, pos->cpus, pos->threads) < 0) {
> > if (perf_evsel__fallback(pos, errno, msg, sizeof(msg))) {
> > if (verbose)
> > ui__warning("%s\n", msg);
> > diff --git a/tools/perf/util/evlist.c b/tools/perf/util/evlist.c
> > index 373f65b..be6fde9 100644
> > --- a/tools/perf/util/evlist.c
> > +++ b/tools/perf/util/evlist.c
> > @@ -1179,6 +1179,10 @@ int perf_evlist__apply_filters(struct perf_evlist *evlist, struct perf_evsel **e
> > if (evsel->filter == NULL)
> > continue;
> >
> > + /*
> > + * filters only work for tracepoint event, which doesn't have cpu limit.
> > + * So evlist and evsel should always be same.
> > + */
> > err = perf_evsel__apply_filter(evsel, ncpus, nthreads, evsel->filter);
> > if (err) {
> > *err_evsel = evsel;
> > --
> > 1.8.3.1
> >
next prev parent reply other threads:[~2015-08-31 20:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 6:23 kan.liang
2015-08-21 13:54 ` Jiri Olsa
2015-08-31 20:31 ` Arnaldo Carvalho de Melo [this message]
2015-08-31 21:06 ` Liang, Kan
2015-08-31 21:14 ` Arnaldo Carvalho de Melo
2015-08-31 21:28 ` Liang, Kan
2015-08-31 21:34 ` Arnaldo Carvalho de Melo
2015-09-01 8:31 ` [tip:perf/urgent] perf evlist: Open " tip-bot for Kan Liang
2015-09-03 13:34 ` Adrian Hunter
2015-09-03 15:27 ` Arnaldo Carvalho de Melo
2015-09-03 16:23 ` Adrian Hunter
2015-09-03 16:41 ` Arnaldo Carvalho de Melo
2015-09-03 18:19 ` Jiri Olsa
2015-09-03 18:38 ` Adrian Hunter
2015-09-03 19:04 ` Jiri Olsa
2015-09-03 20:41 ` Arnaldo Carvalho de Melo
2015-09-04 7:05 ` Jiri Olsa
2015-09-04 7:09 ` Adrian Hunter
2015-09-04 12:15 ` [PATCH] perf tools: Fix gaps propagating maps Adrian Hunter
2015-09-04 13:28 ` Arnaldo Carvalho de Melo
2015-09-04 13:42 ` Adrian Hunter
2015-09-04 14:48 ` Arnaldo Carvalho de Melo
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=20150831203115.GI4423@kernel.org \
--to=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--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
Powered by JetHome