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: Wed, 21 Apr 2010 20:40:07 +0200 From: Stephane Eranian <eranian@...gle.com> To: Robert Richter <robert.richter@....com> Cc: Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...e.hu>, LKML <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 00/12] perf: introduce model specific events and AMD IBS On Wed, Apr 21, 2010 at 8:26 PM, Robert Richter <robert.richter@....com> wrote: > On 21.04.10 15:21:35, Stephane Eranian wrote: >> Okay, so you're suggesting everything is exposed via PERF_SAMPLE_REGS. >> PEBS does capture machine state which is easily mapped onto PERF_SAMPLE_REGS. >> Well, that's until you look at PEB-LL on Nehalem where is captures >> latencies and data >> addresses. >> >> Those could be funneled through PERF_SAMPLE_REGS >> as well, I believe. But that means, PERF_SAMPLE_REGS would need some >> configuration >> bitmask to name the registers of interest, e.g. EAX, EDX, IBSOP_DATA, >> IBSOP_PHYSAD, >> and so on. > > What is the idea of PERF_SAMPLE_REGS? A git grep PERF_SAMPLE_REGS only > returns a single line in -tip. I know nothing about it. > You may want to collect some of the general purpose registers (interrupted state) in each sample. This is what you get today in a signal handler (ucontext) for instance. That may also be a way to export PEBS samples. -- 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