[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150520004304.GF26111@kernel.org>
Date: Tue, 19 May 2015 21:43:04 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Namhyung Kim <namhyung@...nel.org>
Cc: Alexei Starovoitov <ast@...mgrid.com>,
Wang Nan <wangnan0@...wei.com>, paulus@...ba.org,
a.p.zijlstra@...llo.nl, mingo@...hat.com, jolsa@...nel.org,
dsahern@...il.com, daniel@...earbox.net, brendan.d.gregg@...il.com,
masami.hiramatsu.pt@...achi.com, lizefan@...wei.com,
linux-kernel@...r.kernel.org, pi3orama@....com
Subject: Re: [RFC PATCH v3 00/37] perf tools: introduce 'perf bpf' command to
load eBPF programs.
Em Wed, May 20, 2015 at 09:30:52AM +0900, Namhyung Kim escreveu:
> On Tue, May 19, 2015 at 06:10:33PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Tue, May 19, 2015 at 01:46:10PM -0700, Alexei Starovoitov escreveu:
> > > if you're proposing to do something like:
> > > perf script bpf_file.c
> > > that will do event creation, filtering, aggregation, reporting
> > > and printing results, then it's fine.
> > > This is pretty much what I thought 'perf bpf run' will do.
> > Agreed, that is what I think should be done, parts of what is in
> > bpf.file.c are related to the data collection, some are for filtering,
> > and parts are for reporting, etc.
> Looks great! :)
> > This all should use infrastructure in perf for symbol resolving,
> > callcahins, etc.
> But then we need to stabilize libperf APIs IMHO. :)
Well, all this will remain in tools/, more so in tools/perf/ where we
can continue to do what you propose :-)
- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists