[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5484e005-3b3d-a53a-f18e-d9b6620cf84b@intel.com>
Date: Fri, 19 Jun 2020 13:24:23 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Andy Lutomirski <luto@...nel.org>,
Richard Hughes <hughsient@...il.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Borislav Petkov <bp@...en8.de>,
Daniel Gutson <daniel@...ypsium.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, X86 ML <x86@...nel.org>,
"H. Peter Anvin" <hpa@...or.com>, Arnd Bergmann <arnd@...db.de>,
Peter Zijlstra <peterz@...radead.org>,
"David S. Miller" <davem@...emloft.net>,
Rob Herring <robh@...nel.org>, Tony Luck <tony.luck@...el.com>,
Rahul Tanwar <rahul.tanwar@...ux.intel.com>,
Xiaoyao Li <xiaoyao.li@...el.com>,
Sean Christopherson <sean.j.christopherson@...el.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Ability to read the MKTME status from userspace
On 6/19/20 1:20 PM, Andy Lutomirski wrote:
> Boris, etc: would it be reasonable to add a list of CPU features that
> are present but turned off by firmware? SME is far from the only
> thing that's frequently in this category. x2apic, fast strings, and
> virtualization come to mind.
Sounds sane to me. I like the idea of proving ammo to end users to
either go flip a BIOS switch, or yell at their firmware vendor.
Powered by blists - more mailing lists