Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752190AbbESVmT (ORCPT ); Tue, 19 May 2015 17:42:19 -0400 Received: from mail-pd0-f171.google.com ([209.85.192.171]:32860 "EHLO mail-pd0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751637AbbESVmO (ORCPT ); Tue, 19 May 2015 17:42:14 -0400 Message-ID: <555BAE33.5060502@plumgrid.com> Date: Tue, 19 May 2015 14:42:11 -0700 From: Alexei Starovoitov User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Arnaldo Carvalho de Melo CC: Namhyung Kim , Wang Nan , paulus@samba.org, a.p.zijlstra@chello.nl, mingo@redhat.com, jolsa@kernel.org, dsahern@gmail.com, daniel@iogearbox.net, brendan.d.gregg@gmail.com, masami.hiramatsu.pt@hitachi.com, lizefan@huawei.com, linux-kernel@vger.kernel.org, pi3orama@163.com Subject: Re: [RFC PATCH v3 00/37] perf tools: introduce 'perf bpf' command to load eBPF programs. References: <1431860222-61636-1-git-send-email-wangnan0@huawei.com> <555A3FC2.8060805@plumgrid.com> <20150518204416.GJ18563@kernel.org> <555A541F.6090606@plumgrid.com> <20150518212013.GB13946@kernel.org> <555A5D96.2070509@plumgrid.com> <20150519134458.GC13946@kernel.org> <20150519160448.GD29162@danjae.kornet> <20150519164040.GB19921@kernel.org> <555BA112.6090505@plumgrid.com> <20150519211033.GF19921@kernel.org> In-Reply-To: <20150519211033.GF19921@kernel.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1533 Lines: 41 On 5/19/15 2:10 PM, Arnaldo Carvalho de Melo wrote: > > This all should use infrastructure in perf for symbol resolving, > callcahins, etc. yes. 100% > Right, but if we do a: > > perf script -i perf.data bpf_file.c > > Then there would be a short circuit effect of just doing the > aggregation and/or reporting. That can work, but I don't see why I would use bpf for scripting on top of perf.data. If trace is already collected, the existing perl/python scripts will work fine. > Well, we could have a tee like mode where perf.data file could be > generated so that we could run it again after doing some change on the > aggregation code, so that we wouldn't have to re-run the data collection > parts, that could be about some condition hard to capture, etc. true, but again I don't think in such scenario you'd need bpf. bpf is needed when the number of events is huge and the user needs to aggregate/process them in-kernel. >> I guess I'm saying let's not get too much ahead of ourselves ;) > > No problem, but then we need to talk at this moment not to add new stuff > that we think should not be added, like 'perf bpf' :-) ahh, that's where you going :) Sure. I don't mind avoiding that unbearable abbreviation if we can :) 'perf script file.[oc]' command line works for me. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/