| 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
| ||
|
Message-ID: <1271190201-25705-1-git-send-email-robert.richter@amd.com> Date: Tue, 13 Apr 2010 22:23:09 +0200 From: Robert Richter <robert.richter@....com> To: Peter Zijlstra <a.p.zijlstra@...llo.nl> CC: Ingo Molnar <mingo@...e.hu>, Stephane Eranian <eranian@...gle.com>, LKML <linux-kernel@...r.kernel.org> Subject: [PATCH 00/12] perf: introduce model specific events and AMD IBS This patch series introduces model specific events and impments AMD IBS (Instruction Based Sampling) for perf_events. IBS is documented here: BIOS and Kernel Developer’s Guide (BKDG) For AMD Family 10h Processors http://support.amd.com/us/Processor_TechDocs/31116.pdf AMD64 Architecture Programmer’s Manual Volume 2: System Programming http://support.amd.com/us/Processor_TechDocs/24593.pdf The general approach is to introduce a flag to mark an event as model specific. With that flag set a model specific ibs (raw) config value can be passed to the pmu for setup. When there are ibs samples available, it is sent back as a raw data sample to the userland. So we have a raw config value and raw sampling data. This requires the userland to setup ibs and further extract and process sampling data. Patches 1-8 rework and refactor the code to prepare the ibs implementation. This is done in patches 9-12. I will add ibs example code to libpfm4. -Robert -- 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