public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Richard Hughes <hughsient@gmail.com>
Cc: Borislav Petkov <bp@alien8.de>,
	Daniel Gutson <daniel@eclypsium.com>,
	Dave Hansen <dave.hansen@intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Peter Zijlstra <peterz@infradead.org>,
	"David S. Miller" <davem@davemloft.net>,
	Rob Herring <robh@kernel.org>, Tony Luck <tony.luck@intel.com>,
	Rahul Tanwar <rahul.tanwar@linux.intel.com>,
	Xiaoyao Li <xiaoyao.li@intel.com>,
	Sean Christopherson <sean.j.christopherson@intel.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Ability to read the MKTME status from userspace
Date: Fri, 19 Jun 2020 18:40:56 +0200	[thread overview]
Message-ID: <20200619164056.GB2235992@kroah.com> (raw)
In-Reply-To: <CAD2FfiGN5kdHHEz-6Oy9S-fFT35bJH0ZOfqfn5SyCG_Y2LtE_w@mail.gmail.com>

On Fri, Jun 19, 2020 at 05:33:39PM +0100, Richard Hughes wrote:
> On Fri, 19 Jun 2020 at 17:10, Borislav Petkov <bp@alien8.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

  reply	other threads:[~2020-06-19 16:41 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18 21:02 [PATCH] Ability to read the MKTME status from userspace Daniel Gutson
2020-06-18 21:08 ` Dave Hansen
     [not found]   ` <CAFmMkTHNxSN_uWtm63TdkGxj44NXQQKEOmATXhjA=4DSCS92kQ@mail.gmail.com>
2020-06-18 22:01     ` Borislav Petkov
     [not found]       ` <CAFmMkTGMAu-huTnP1aeMb_W4NddbTD_b2jhbDVKBDrkwgB97wg@mail.gmail.com>
2020-06-19  7:40         ` Borislav Petkov
     [not found]           ` <CAFmMkTGV0ZR6C=EBGQAiz1vw1vrUXSLTnH5ZbBUvfhPLg_tF6g@mail.gmail.com>
2020-06-19 13:22             ` Borislav Petkov
2020-06-19 13:31               ` Richard Hughes
2020-06-19 13:44                 ` Borislav Petkov
2020-06-19 13:50                   ` Richard Hughes
2020-06-19 15:48                     ` Andy Lutomirski
2020-06-19 16:17                       ` Borislav Petkov
2020-06-19 16:28                         ` Andy Lutomirski
2020-06-19 16:31                         ` Richard Hughes
2020-06-19 16:10                     ` Borislav Petkov
2020-06-19 16:33                       ` Richard Hughes
2020-06-19 16:40                         ` Greg Kroah-Hartman [this message]
2020-06-19 16:47                           ` Richard Hughes
2020-06-19 19:41                             ` Andy Lutomirski
2020-06-19 19:58                               ` Richard Hughes
2020-06-19 20:20                                 ` Andy Lutomirski
2020-06-19 20:24                                   ` Dave Hansen
2020-06-22  9:34                                     ` Boris Petkov
2020-06-18 23:52     ` Dave Hansen
2020-06-19  7:41       ` Borislav Petkov
2020-06-19 13:25       ` Richard Hughes
2020-06-19 13:33         ` Dave Hansen
2020-06-19 13:37           ` Richard Hughes
2020-06-19 13:58             ` Dave Hansen
2020-06-19 14:09               ` Richard Hughes
2020-06-19 14:23                 ` Dave Hansen
2020-06-19 14:36                   ` Richard Hughes
2020-06-19 14:48                     ` Dave Hansen
2020-06-19 15:02                       ` Richard Hughes
2020-06-19 15:36                         ` Dave Hansen
2020-06-19  7:20 ` Greg Kroah-Hartman
     [not found]   ` <CAFmMkTF7QBJQdKxhsPiUPifsxykyCVv=NYandpB0z8EccAxMXw@mail.gmail.com>
2020-06-19 14:02     ` Greg Kroah-Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200619164056.GB2235992@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=bp@alien8.de \
    --cc=daniel@eclypsium.com \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=hpa@zytor.com \
    --cc=hughsient@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rahul.tanwar@linux.intel.com \
    --cc=robh@kernel.org \
    --cc=sean.j.christopherson@intel.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    --cc=xiaoyao.li@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox