[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e2a57ee8-6489-40d5-04d0-7d985eba961f@linux.intel.com>
Date: Sun, 27 Jun 2021 09:13:06 -0700
From: Andi Kleen <ak@...ux.intel.com>
To: Adrian Hunter <adrian.hunter@...el.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Jiri Olsa <jolsa@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Mark Rutland <mark.rutland@....com>,
Namhyung Kim <namhyung@...nel.org>,
Leo Yan <leo.yan@...aro.org>,
Kan Liang <kan.liang@...ux.intel.com>,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2 00/10] perf script: Add API for filtering via
dynamically loaded shared object
On 6/27/2021 6:18 AM, Adrian Hunter wrote:
> Hi
>
> In some cases, users want to filter very large amounts of data (e.g. from
> AUX area tracing like Intel PT) looking for something specific. While
> scripting such as Python can be used, Python is 10 to 20 times slower than
> C. So define a C API so that custom filters can be written and loaded.
While I appreciate this for complex cases, in my experience filtering is
usually just a simple expression. It would be nice to also have a way to
do this reasonably fast without having to write a custom C file. Is
the 10x-20x overhead just the python interpreter, or is it related to
perf? Maybe we could have some kind of python fast path just for
filters? Or maybe the alternative would be to have a frontend in perf
that can automatically generate/compile such a C filter based on a
simple expression, but I'm not sure if that would be much simpler.
-Andi
Powered by blists - more mailing lists