[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87cyrvjbpb.ffs@tglx>
Date: Sat, 16 Mar 2024 00:51:28 +0100
From: Thomas Gleixner <tglx@...utronix.de>
To: Borislav Petkov <bp@...en8.de>, Dave Hansen <dave.hansen@...el.com>
Cc: Vignesh Balasubramanian <vigbalas@....com>,
linux-kernel@...r.kernel.org, linux-toolchains@...r.kernel.org,
mpe@...erman.id.au, npiggin@...il.com, christophe.leroy@...roup.eu,
aneesh.kumar@...nel.org, naveen.n.rao@...ux.ibm.com,
ebiederm@...ssion.com, keescook@...omium.org, x86@...nel.org,
linuxppc-dev@...ts.ozlabs.org, linux-mm@...ck.org,
jinisusan.george@....com, matz@...e.de, binutils@...rceware.org,
jhb@...ebsd.org, felix.willgerodt@...el.com
Subject: Re: [PATCH 1/1] x86/elf: Add a new .note section containing
Xfeatures information to x86 core files
On Thu, Mar 14 2024 at 17:29, Borislav Petkov wrote:
> On Thu, Mar 14, 2024 at 09:19:15AM -0700, Dave Hansen wrote:
>> Are you envisioning an *XSAVE* state component that's not described by
>> CPUID?
>
> I want to be prepared. You can imagine some of the short cuts and
> corners cutting hw guys would do so I'd want to be prepared there and
> not tie this to CPUID.
Anything which is not enumerated in CPUID does not exist in
XSTATE. Period and end of story.
Stop paving the way for hardware people to have an excuse for being
stupid.
Aside of that XSTATE is a dead end as we all know.
Thanks,
tglx
Powered by blists - more mailing lists