From: Tom Lendacky <thomas.lendacky@amd.com>
To: "Limonciello, Mario" <mario.limonciello@amd.com>,
Borislav Petkov <bp@alien8.de>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
hughsient@gmail.com,
Martin Fernandez <martin.fernandez@eclypsium.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] x86: Use CPUID 0x8000001f to confirm SME availability
Date: Fri, 11 Feb 2022 15:09:12 -0600 [thread overview]
Message-ID: <d476d448-cd68-0c93-c98c-4f952d7caef6@amd.com> (raw)
In-Reply-To: <a52990c0-3e54-a5f2-22c2-3446e92f4294@amd.com>
On 2/11/22 13:51, Limonciello, Mario wrote:
> On 2/11/2022 08:55, Tom Lendacky wrote:
>> On 2/10/22 23:36, Mario Limonciello wrote:
> 1254: f6 45 d8 01 testb $0x1,-0x28(%rbp)
> 1258: 74 02 je 125c <stop_this_cpu+0x8c>
> 125a: 0f 09 wbinvd
> 125c: eb 07 jmp 1265 <stop_this_cpu+0x95>
> 125e: 0f 00 2d 00 00 00 00 verw 0x0(%rip) # 1265
> <stop_this_cpu+0x95>
> 1265: f4 hlt
> 1266: eb f4 jmp 125c <stop_this_cpu+0x8c>
That appears to be the same as today after the WBINVD is issued, so should
be good.
Thanks,
Tom
>
prev parent reply other threads:[~2022-02-11 21:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 5:36 Mario Limonciello
2022-02-11 5:36 ` [PATCH 2/2] x86/cpu: clear SME/SEV/SEV_ES features when not in use Mario Limonciello
2022-02-11 8:31 ` Borislav Petkov
2022-02-11 19:43 ` Limonciello, Mario
2022-02-11 14:46 ` Tom Lendacky
2022-02-11 19:54 ` Limonciello, Mario
2022-02-11 20:42 ` Tom Lendacky
2022-02-11 8:28 ` [PATCH 1/2] x86: Use CPUID 0x8000001f to confirm SME availability Borislav Petkov
2022-02-11 14:55 ` Tom Lendacky
2022-02-11 19:51 ` Limonciello, Mario
2022-02-11 21:09 ` Tom Lendacky [this message]
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=d476d448-cd68-0c93-c98c-4f952d7caef6@amd.com \
--to=thomas.lendacky@amd.com \
--cc=bp@alien8.de \
--cc=hughsient@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=martin.fernandez@eclypsium.com \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®