linux-kernel - Re: [PATCH 2/2] perf: Walk through the relevant events only

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]

Message-ID: <20100305173342.GE5244@nowhere>
Date:	Fri, 5 Mar 2010 18:33:46 +0100
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	Paul Mackerras <paulus@...ba.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Masami Hiramatsu <mhiramat@...hat.com>,
	Jason Baron <jbaron@...hat.com>,
	Arnaldo Carvalho de Melo <acme@...hat.com>
Subject: Re: [PATCH 2/2] perf: Walk through the relevant events only

On Fri, Mar 05, 2010 at 06:20:29PM +0100, Peter Zijlstra wrote:
> On Fri, 2010-03-05 at 18:03 +0100, Frederic Weisbecker wrote:
> > 
> > Now isn't the problem more in the fact that most of the swevents
> > should be tracepoints? 
> 
> No, different interface, and I don't want to require TRACE=y, I already
> utterly hate that x86 requires PERF=y.
> 

This could be reduced to the strict minimum, say CONFIG_TRACEPOINT
and some code around just to support the event ids.

Software events could be made optionals too.

I just don't like this multiplication of probe points of different
natures in a single point. That's wasteful.


> I already
> utterly hate that x86 requires PERF=y.


Me too, and it's my bad, so me double too. Sometimes I think
we should make BREAKPOINTs optional, default y. I just don't know
if something like this that has always been builtin can be made
optional.

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