linux-kernel - Re: disabling group leader perf

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 6 Sep 2010 14:40:46 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Peter Zijlstra <peterz@...radead.org>,
	Tom Zanussi <tzanussi@...il.com>,
	Frédéric Weisbecker <fweisbec@...il.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>
Cc:	Avi Kivity <avi@...hat.com>, linux-perf-users@...r.kernel.org,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: disabling group leader perf_event


* Peter Zijlstra <peterz@...radead.org> wrote:

> On Mon, 2010-09-06 at 14:58 +0300, Avi Kivity wrote:
> > On 09/06/2010 02:54 PM, Peter Zijlstra wrote:
> > >
> > >> Basically, to read() all events in one go.  I have many of them.
> > >>
> > >> My current problem is that I have an event (kvm_exit) which I want to
> > >> drill down by looking at a field (exit_reason).  So I create lots of
> > >> separate perf_events with a filter for each reason:
> > >> kvm_exit(exit_reason==0), kvm_exit(exit_reason==1), etc.  But filters
> > >> are fairly slow (can have ~60 such events on AMD), so I want to make
> > >> this drill-down optional.
> > > Yeah, filters suck.
> > 
> > Any idea why?  I saw nothing obvious in the code, except that there 
> > is lots of it.
> 
> It filters after it does all the hard work of creating the trace 
> event, instead of before.

Btw., that's an implementational property of filters that would be nice 
to fix.

If it's not doable within CPP then outside of it.

	Ingo
--
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/