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: <1267810752.4942.5.camel@laptop>
Date:	Fri, 05 Mar 2010 18:39:12 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Frederic Weisbecker <fweisbec@...il.com>
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, 2010-03-05 at 18:33 +0100, Frederic Weisbecker wrote:
> 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.

Can't, software events already are an ABI so we'll have to support that
forever, but sure you can make something that reduces to the current
software event callback on TRACE=n and maps to the right software event
id when TRACE=y.

> Software events could be made optionals too.

Sure, but they're nowhere near as much code as tracepoints.

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

Simply for build testing that would be useful, we could make it an
embedded switch.

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