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: <CAK8P3a1t5N_vW3rcMD_e+UMy5EQDrTrE4QqPDo7nM_s1-Bf0XQ@mail.gmail.com> Date: Wed, 19 Jan 2022 08:44:54 +0100 From: Arnd Bergmann <arnd@...db.de> To: Anshuman Khandual <anshuman.khandual@....com> Cc: Arnd Bergmann <arnd@...db.de>, Linux ARM <linux-arm-kernel@...ts.infradead.org>, Catalin Marinas <catalin.marinas@....com>, Will Deacon <will@...nel.org>, Mathieu Poirier <mathieu.poirier@...aro.org>, Suzuki Poulose <suzuki.poulose@....com>, coresight@...ts.linaro.org, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 1/2] arm64: Add Cortex-X2 CPU part definition On Wed, Jan 19, 2022 at 7:44 AM Anshuman Khandual <anshuman.khandual@....com> wrote: > On 1/13/22 5:17 PM, Arnd Bergmann wrote: > > > > It also helps me personally to have a known place to look up the names > > by value rather than chasing through reference manuals. > > IIUC the purpose here would be a quick CPU ID documentation reference check ? > I will wait for other opinions here and add the remaining in a separate patch > probably. The purpose would be to do what is obviously the right thing, and to avoid more patches getting sent the next time someone needs to add a workaround for another core that is already known. If you can't do this without more discussion, then just use your current version and let the next person do it. Arnd
Powered by blists - more mailing lists