[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200619164056.GB2235992@kroah.com>
Date: Fri, 19 Jun 2020 18:40:56 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Richard Hughes <hughsient@...il.com>
Cc: Borislav Petkov <bp@...en8.de>,
Daniel Gutson <daniel@...ypsium.com>,
Dave Hansen <dave.hansen@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, 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 Fri, Jun 19, 2020 at 05:33:39PM +0100, Richard Hughes wrote:
> On Fri, 19 Jun 2020 at 17:10, Borislav Petkov <bp@...en8.de> wrote:
> > - do you just want to display feature support?
>
> Yes. I want to show the user *why* TME is not available.
So even if it is "available" that's fine, even if it is not being used?
And how can you ever tell if a BIOS disables a CPU feature, yet the chip
still has it? That should be not seen from the OS as it really doesn't
care, it just knows if the feature is able to be used or not.
thanks,
greg k-h
Powered by blists - more mailing lists