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
| ||
|
Date: Thu, 21 Jan 2010 09:47:42 +0100 From: stephane eranian <eranian@...glemail.com> To: Peter Zijlstra <peterz@...radead.org> Cc: Corey Ashford <cjashfor@...ux.vnet.ibm.com>, LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>, Andi Kleen <andi@...stfloor.org>, Paul Mackerras <paulus@...ba.org>, Frederic Weisbecker <fweisbec@...il.com>, Xiao Guangrong <xiaoguangrong@...fujitsu.com>, Dan Terpstra <terpstra@...s.utk.edu>, Philip Mucci <mucci@...s.utk.edu>, Maynard Johnson <mpjohn@...ibm.com>, Carl Love <cel@...ibm.com> Subject: Re: [RFC] perf_events: support for uncore a.k.a. nest units On Wed, Jan 20, 2010 at 10:33 PM, Peter Zijlstra <peterz@...radead.org> wrote: > On Wed, 2010-01-20 at 14:34 +0100, Peter Zijlstra wrote: > >> So how about PERF_TYPE_{CORE,NODE,SOCKET} like things? > > OK, so I read most of the intel uncore stuff, and it seems to suggest > you need a regular pmu event to receive uncore events (chained setup), > this seems rather retarded since it wastes a perfectly good pmu event > and makes configuring all this more intricate... > I don't think that is correct. You can be using the uncore PMU on Nehalem without any core PMU event. The only thing to realize is that uncore PMU shares the same interrupt vector as core PMU. You need to configure which core the uncore is going to interrupt on. This is done via a bitmask, so you can interrupt more than one core at a time. Several strategies are possible. > A well, nothing to be done about that I guess.. > > > > -- 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/
Powered by blists - more mailing lists