Re: Adding a filter to events (instead of replacing one) was Re: [PATCH 1/2] perf, tools: Add PERF_PID

Em Wed, Oct 01, 2014 at 03:02:18PM -0700, Andi Kleen escreveu: > On Wed, Oct 01, 2014 at 03:03:16PM -0300, Arnaldo Carvalho de Melo wrote: > > Em Wed, Sep 24, 2014 at 01:51:08PM -0700, Andi Kleen escreveu: > > > It's currently difficult to filter out perf itself using a filter. > > > This can give

Re: Adding a filter to events (instead of replacing one) was Re: [PATCH 1/2] perf, tools: Add PERF_PID

On Wed, Oct 01, 2014 at 03:03:16PM -0300, Arnaldo Carvalho de Melo wrote: > Em Wed, Sep 24, 2014 at 01:51:08PM -0700, Andi Kleen escreveu: > > > It's currently difficult to filter out perf itself using a filter. > > This can give cascading effects during IO tracing when the IO perf > > does itself

Adding a filter to events (instead of replacing one) was Re: [PATCH 1/2] perf, tools: Add PERF_PID

Em Wed, Sep 24, 2014 at 01:51:08PM -0700, Andi Kleen escreveu: > It's currently difficult to filter out perf itself using a filter. > This can give cascading effects during IO tracing when the IO perf > does itself causes more trace output. > The best way to filter is to use the pid. But it's di

[PATCH 1/2] perf, tools: Add PERF_PID

From: Andi Kleen It's currently difficult to filter out perf itself using a filter. This can give cascading effects during IO tracing when the IO perf does itself causes more trace output. The best way to filter is to use the pid. But it's difficult to get the pid of perf without using hacks. A