[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200902165501.GC21537@zn.tnic>
Date: Wed, 2 Sep 2020 18:55:01 +0200
From: Borislav Petkov <bp@...en8.de>
To: peterz@...radead.org
Cc: Feng Tang <feng.tang@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H . Peter Anvin" <hpa@...or.com>,
Dave Hansen <dave.hansen@...el.com>, x86@...nel.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] tools/x86: add kcpuid tool to show raw CPU features
On Wed, Sep 02, 2020 at 06:45:38PM +0200, peterz@...radead.org wrote:
> We really should clear the CPUID bits when the kernel explicitly
> disables things.
Actually, you want to *disable* the functionality behind it by clearing
a bit in CR4 - and yes, not all features have CR4 bits - so that
luserspace doesn't "probe" the existence of certain instructions.
Example: you can still try to run RDRAND and succeed even if the
corresponding CPUID bit is clear.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists