linux-kernel - RE: [PATCH] perf script: add script to profile and resolve physical mem type

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <37D7C6CF3E00A74B8858931C1DB2F077537D6C9F@SHSMSX103.ccr.corp.intel.com>
Date:   Tue, 17 Oct 2017 21:10:16 +0000
From:   "Liang, Kan" <kan.liang@...el.com>
To:     Andi Kleen <ak@...ux.intel.com>
CC:     Stephane Eranian <eranian@...gle.com>,
        Arnaldo Carvalho de Melo <acme@...nel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        "mingo@...hat.com" <mingo@...hat.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Jiri Olsa <jolsa@...nel.org>,
        "Williams, Dan J" <dan.j.williams@...el.com>
Subject: RE: [PATCH] perf script: add script to profile and resolve physical
 mem type

 > >
> > Right, it doesn’t need load latency. 0x81d0 should be a better choice.
> > I will use 0x81d0 and 0x82d0 as default event for V2.
> 
> That's model specific. You would need to check the model number if you do
> that.
> 
> Also with modern perf you can use the correct event names of course.

The event names are model specific as well.
For Mem load events,
MEM_INST_RETIRED.ALL_LOADS is the event name for skylake.
MEM_UOPS_RETIRED.ALL_LOADS is the event name for the rest of platforms.
I think it still need to check the model number.

Thanks,
Kan