| 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: Tue, 11 Aug 2015 09:58:00 +0100 From: Andrew Haley <aph@...hat.com> To: "Suzuki K. Poulose" <Suzuki.Poulose@....com>, Catalin Marinas <Catalin.Marinas@....com> CC: "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, Mark Rutland <Mark.Rutland@....com>, Will Deacon <Will.Deacon@....com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "edward.nevill@...aro.org" <edward.nevill@...aro.org> Subject: Re: [RFC PATCH 01/10] arm64: feature registers: Documentation On 11/08/15 09:41, Suzuki K. Poulose wrote: > The REVIDR has to be used in conjunction with the MIDR to make real sense. Sure, of course. > We cannot guarantee that the REVIDR that we read (would) belong to the CPU > where MIDR would have been read (unless the process is pinned) and hence the > user may not be able to make any use of the information. Well, yes, nothing is perfect. The situation we're in now, for example, is that if we see Cortex A57 we have to assume Cortex A53 and include workarounds. People might mix and match processors. So it goes. > Steve has a patch [1] > to expose the MIDR,REVIDR info via sysfs. > > [1] https://lkml.org/lkml/2015/7/24/420 OK. As long as I can get at it I'm happy. Andrew. -- 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