linux-kernel - Re: [tip:perf/core] perf/ftrace: Optimize perf/tracepoint interaction for single events

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 for Android: free password hash cracker in your pocket

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

Message-ID: <1274257885.5605.10289.camel@twins>
Date:	Wed, 19 May 2010 10:31:25 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	mingo@...hat.com, hpa@...or.com, paulus@...ba.org, acme@...hat.com,
	linux-kernel@...r.kernel.org, efault@....de, rostedt@...dmis.org,
	tglx@...utronix.de, mingo@...e.hu,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:perf/core] perf/ftrace: Optimize perf/tracepoint
 interaction for single events

On Wed, 2010-05-19 at 10:23 +0200, Frederic Weisbecker wrote:

> Yeah, then if you launch perf sched for example, you'll have NR_CPU perf events
> attached to each lock trace events, since we create one event per cpu.

Right, but simple per task (non-inherited) would have only 1.

But yeah, plenty of room to improve here.
--
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/