* Andi Kleen <a...@firstfloor.org> wrote:
> From: Andi Kleen <a...@linux.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 majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
