From: Borislav Petkov <bp@alien8.de>
To: Daniel Gutson <daniel@eclypsium.com>
Cc: 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>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
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@vger.kernel.org,
Richard Hughes <hughsient@gmail.com>
Subject: Re: [PATCH] Ability to read the MKTME status from userspace
Date: Fri, 19 Jun 2020 09:40:53 +0200 [thread overview]
Message-ID: <20200619074053.GA32683@zn.tnic> (raw)
In-Reply-To: <CAFmMkTGMAu-huTnP1aeMb_W4NddbTD_b2jhbDVKBDrkwgB97wg@mail.gmail.com>
On Thu, Jun 18, 2020 at 07:34:21PM -0300, Daniel Gutson wrote:
> Besides being a CPU capability, it has to be enabled by the BIOS, which is
> what the flag represents.
... yes, and if it is disabled in the BIOS, you clear the CPU cap flag.
Something like this untested diff:
---
diff --git a/arch/x86/kernel/cpu/intel.c b/arch/x86/kernel/cpu/intel.c
index c25a67a34bd3..59d8342f6a64 100644
--- a/arch/x86/kernel/cpu/intel.c
+++ b/arch/x86/kernel/cpu/intel.c
@@ -525,6 +525,7 @@ static void detect_tme(struct cpuinfo_x86 *c)
if (!TME_ACTIVATE_LOCKED(tme_activate) || !TME_ACTIVATE_ENABLED(tme_activate)) {
pr_info_once("x86/tme: not enabled by BIOS\n");
mktme_status = MKTME_DISABLED;
+ clear_cpu_cap(c, X86_FEATURE_TME);
return;
}
@@ -553,10 +554,11 @@ static void detect_tme(struct cpuinfo_x86 *c)
pr_info_once("x86/mktme: disabled by BIOS\n");
}
- if (mktme_status == MKTME_UNINITIALIZED) {
- /* MKTME is usable */
+ /* MKTME is usable */
+ if (mktme_status == MKTME_UNINITIALIZED)
mktme_status = MKTME_ENABLED;
- }
+ else if (mktme_status == MKTME_DISABLED)
+ clear_cpu_cap(c, X86_FEATURE_TME);
/*
* KeyID bits effectively lower the number of physical address
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-06-19 7:41 UTC|newest]
Thread overview: 36+ 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 [this message]
[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
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
-- strict thread matches above, loose matches on Subject: below --
2020-06-25 0:33 kernel test robot
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=20200619074053.GA32683@zn.tnic \
--to=bp@alien8.de \
--cc=arnd@arndb.de \
--cc=daniel@eclypsium.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.