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: Mon, 23 Mar 2015 10:45:07 +0100 From: Ingo Molnar <mingo@...nel.org> To: Andi Kleen <andi@...stfloor.org> Cc: peterz@...radead.org, linux-kernel@...r.kernel.org, Andi Kleen <ak@...ux.intel.com> Subject: Re: [PATCH 1/3] perf, x86: Add new cache events table for Haswell * Andi Kleen <andi@...stfloor.org> wrote: > From: Andi Kleen <ak@...ux.intel.com> > > Haswell offcore events are quite different from Sandy Bridge. > Add a new table to handle Haswell properly. > > Note that the offcore bits listed in the SDM are not quite correct > (this is currently being fixed). An uptodate list of bits is > in the patch. > > The basic setup is similar to Sandy Bridge. The prefetch columns > have been removed, as prefetch counting is not very reliable > on Haswell. One L1 event that is not in the event list anymore > has been also removed. > > - data reads do not include code reads (comparable to earlier Sandy > Bridge tables) > - data counts include speculative execution (except L1 write, dtlb, bpu) > - remote node access includes both remote memory, remote cache, remote mmio. > - prefetches are not included in the counts for consistency > (different from Sandy Bridge, which includes prefetches in the remote node) > > The events with additional caveats have references to the specification update. > + [ C(RESULT_ACCESS) ] = 0x81d0, /* MEM_UOPS_RETIRED.ALL_LOADS, HSM30 */ > + [ C(RESULT_ACCESS) ] = 0x82d0, /* MEM_UOPS_RETIRED.ALL_STORES, HSM30 */ > + [ C(RESULT_ACCESS) ] = 0x81d0, /* MEM_UOPS_RETIRED.ALL_LOADS, HSM30 */ > + [ C(RESULT_ACCESS) ] = 0x82d0, /* MEM_UOPS_RETIRED.ALL_STORES, HSM30 */ So that 'HSM30' is code for the specification update? You'll need to properly describe HSM30 at least once instead of using obfuscation. Thanks, Ingo -- 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