linux-kernel - Re: [PATCH v3 2/2] x86/xstate: Make AVX512 status tracking more accurate

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: <YXmQSG7BYCcZ6jqZ@zn.tnic>
Date:   Wed, 27 Oct 2021 19:45:44 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     Noah Goldstein <goldstein.w.n@...il.com>
Cc:     tglx@...utronix.de, mingo@...hat.com, X86 ML <x86@...nel.org>,
        hpa@...or.com, Andy Lutomirski <luto@...nel.org>,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 2/2] x86/xstate: Make AVX512 status tracking more
 accurate

On Wed, Oct 27, 2021 at 12:37:16PM -0500, Noah Goldstein wrote:
> What about just splitting off a field for 'AVX512_ZMM_Hi256'?

Let's please not perpetuate this into what it cannot become anyway. The
more stuff we add to it, the more people will start using it and we're
stuck with it forever. And soon that thing will be worthless anyway.

So what's the point...

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette