| 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: <20150521025653.GC7484@tassilo.jf.intel.com> Date: Wed, 20 May 2015 19:56:53 -0700 From: Andi Kleen <ak@...ux.intel.com> To: Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com> Cc: mingo@...hat.com, Michael Ellerman <mpe@...erman.id.au>, Jiri Olsa <jolsa@...hat.com>, Arnaldo Carvalho de Melo <acme@...nel.org>, Paul Mackerras <paulus@...ba.org>, namhyung@...nel.org, linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 3/4] perf: Use pmu_events_map table to create event aliases > Obviously, that does not fit into the VFM field. We could either > add a new PVR field to the mapfile: > > [vfm, version, type, pvr] > > or, as the patch currently does, let architectures intepret the > "version" field as they see fit? > > IOW, leave it to architectures to keep arch_pmu_events_match_cpu() > consistent with _their_ mapfile? version is the version number of the event file. This way you can't signify the version number if you ever change something. If you need something else in vfm to identify the CPU can't you just add it there? I wouldn't really call it vfm, it's really a "abstract cpu identifier per architecture". So if you need pvr just add it there. -Andi -- ak@...ux.intel.com -- Speaking for myself only -- 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