From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Jean Pihet <jean.pihet@linaro.org>,
"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: Fri, 10 Oct 2014 17:41:58 -0300 [thread overview]
Message-ID: <20141010204158.GA13834@kernel.org> (raw)
In-Reply-To: <20141010202854.GC13017@pd.tnic>
Em Fri, Oct 10, 2014 at 10:28:54PM +0200, Borislav Petkov escreveu:
> On Fri, Oct 10, 2014 at 05:07:08PM -0300, Arnaldo Carvalho de Melo wrote:
> > I'll try lding rasd.c with it and checking if it works.
> > Never having tried this, what are the requisites to test it? Some
> > specific hardware and a kernel with the right tracepoint? I guess some
> > recent 3.17-rc kernel is all that I need?
> Well, you'd need the part of Jean's patches which adds the event to evlist:
> https://lkml.kernel.org/r/1412933690-25576-1-git-send-email-jean.pihet@linaro.org
> AFAICT, you could apply patches 1-5 and replace 6 with yours. Now,
> rasd.cfg has the mce:mce_record tracepoint which rasd opens but you
> probably want to put a tracepoint which is much easier to exercise,
> maybe some syscall or whatever.
Right, stoopid me, no need for some specific tracepoint, just to see
that whatever tp it is, it will show up in "rasd"'s event loop. Ok, I'll
try that later.
Next stuff I probably will do is to move the bare minimum used by rasd
to tools/lib/api/perf/, i.e. there will be:
tools/lib/api/perf/evsel.c
tools/perf/util/evsel.c
Both will share the perf_evsel__ namespace (which I thought at some
point to make just: evsel__<METHOD_NAME>, wdyt?).
That way we just make public the bare minimum that already proved to be
useful outside tools/perf/ and over time we move stuff from
tools/perf/util/evsel.c (and from other tools in or out perf's repo)
into the lib.
> I think that should do it but we won't know until we've tried it.
>
> HTH and thanks a lot for doing this!
Np, had to be done at some point :)
- Arnaldo
> --
> Regards/Gruss,
> Boris.
>
> Sent from a fat crate under my desk. Formatting is fine.
> --
next prev parent reply other threads:[~2014-10-10 20:42 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
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 [this message]
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=20141010204158.GA13834@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.