From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jean Pihet <jean.pihet@linaro.org>
Cc: Borislav Petkov <bp@alien8.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Fu Wei <fu.wei@linaro.org>, Robert Richter <rric@kernel.org>,
Jiri Olsa <jolsa@redhat.com>, David Ahern <dsahern@gmail.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH 1/1] rasd: Use perf_evlist__open() instead of open coded
Date: Tue, 7 Oct 2014 10:32:36 -0300 [thread overview]
Message-ID: <20141007133236.GG14113@kernel.org> (raw)
In-Reply-To: <CAFrcx1=swP-3E_pxWEcozFJhL+5YaUBPavQX=OfMtc8h4e=bDg@mail.gmail.com>
Em Tue, Oct 07, 2014 at 10:45:14AM +0200, Jean Pihet escreveu:
> > --- a/src/rasd.c
> > - evlist__for_each(evlist, c) {
> > - /* On all online cpus by default, system wide tracing */
> > - if (perf_evsel__open(c, evlist->cpus, NULL) < 0)
> > - err("opening tracepoint, are you root?");
> > - }
> > - perf_evlist__set_id_pos(evlist);
> > + /* On all online cpus by default, system wide tracing */
> > + if (perf_evlist__open(evlist) < 0)
> > + err("opening tracepoint, are you root?");
> That way the system wide tracing does not work. perf_evlist__open uses
> a non-NULL thread mapping and so it only traces the events generated
> by the daemon itself.
> perf top uses a similar approach but uses a lot of code in machine.c
> (machine__synthesize_threads) and util/event.c
> (perf_event__synthesize_threads) to synthesize the threads etc., which
> we want to avoid in the minimalistic approach of rasd.
Humm, I will look into making it support this usecase, the point of
evsel/evlist is to try to abstract away as much as possible, leaving
just a few methods to be used by tools.
I think the default for perf_evlist__open() should be the most useful
for the majority of tools, which I thought would serve rasd well. It is
not the case, so I'll into how the tools that currently use
perf_evlist__open() behave and try to get a sane default in place.
Hopefully we will completely remove the need to set up any thread or cpu
map, as what you want is syswide tracing, right?
- Arnaldo
> Maybe I missed something about the system wide tracing, any suggestion
> is welcome.
>
> Thanks for looking!
>
> Jean
>
> >
> > /* mmap buffers */
> > if (perf_evlist__mmap(evlist, 4 /* opts->mmap_pages */, false) < 0)
> > --
> > 1.9.3
> >
next prev parent reply other threads:[~2014-10-07 13:32 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 9:06 perf & rasd integration plan Jean Pihet
2014-09-30 13:24 ` Arnaldo Carvalho de Melo
2014-10-05 17:48 ` Borislav Petkov
2014-10-05 18:24 ` Jiri Olsa
2014-10-05 18:45 ` Borislav Petkov
2014-10-05 19:24 ` Chuck Ebbert
2014-10-05 19:28 ` Jiri Olsa
2014-10-06 6:53 ` Jean Pihet
2014-10-08 6:59 ` Jiri Olsa
2014-10-06 9:07 ` Robert Richter
2014-10-06 13:44 ` Jean Pihet
2014-10-06 14:58 ` Arnaldo Carvalho de Melo
2014-10-06 15:01 ` Borislav Petkov
2014-10-06 15:08 ` Arnaldo Carvalho de Melo
2014-10-06 15:16 ` Borislav Petkov
2014-10-06 15:02 ` Jean Pihet
2014-10-06 15:07 ` Arnaldo Carvalho de Melo
2014-10-06 15:16 ` Borislav Petkov
2014-10-06 19:12 ` Arnaldo Carvalho de Melo
2014-10-06 19:53 ` Borislav Petkov
2014-10-06 21:22 ` Arnaldo Carvalho de Melo
2014-10-07 11:23 ` Borislav Petkov
2014-10-07 13:40 ` Arnaldo Carvalho de Melo
2014-10-07 13:49 ` Borislav Petkov
2014-10-07 13:55 ` Arnaldo Carvalho de Melo
2014-10-07 14:02 ` Borislav Petkov
2014-10-07 14:13 ` Arnaldo Carvalho de Melo
2014-10-06 21:26 ` [PATCH 1/1] rasd: Use perf_evlist__open() instead of open coded Arnaldo Carvalho de Melo
2014-10-07 8:45 ` Jean Pihet
2014-10-07 13:32 ` Arnaldo Carvalho de Melo [this message]
2014-10-07 14:04 ` Borislav Petkov
2014-10-07 14:17 ` Arnaldo Carvalho de Melo
2014-10-10 20:07 ` Arnaldo Carvalho de Melo
2014-10-10 20:28 ` Borislav Petkov
2014-10-10 20:41 ` Arnaldo Carvalho de Melo
2014-10-10 20:44 ` Borislav Petkov
2014-10-13 7:29 ` Jean Pihet
2014-10-14 13:56 ` Jiri Olsa
2014-10-14 14:02 ` Arnaldo Carvalho de Melo
2014-10-14 14:22 ` Jiri Olsa
2014-10-14 15:17 ` Borislav Petkov
2014-10-14 15:20 ` Jean Pihet
2014-10-14 14:19 ` David Ahern
2014-10-14 17:09 ` 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=20141007133236.GG14113@kernel.org \
--to=acme@kernel.org \
--cc=bp@alien8.de \
--cc=dsahern@gmail.com \
--cc=fu.wei@linaro.org \
--cc=jean.pihet@linaro.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rric@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