From: "H. Peter Anvin" <hpa@zytor.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
x86-ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Save a WRMSR GS.base?
Date: Mon, 8 Jun 2026 10:30:36 -0700 [thread overview]
Message-ID: <87cfce38-4b5a-4014-a098-2c43e3067df1@zytor.com> (raw)
In-Reply-To: <20260608143835.GAaibT6_Ypd2OzVkWD@fat_crate.local>
On 2026-06-08 07:38, Borislav Petkov wrote:
> On Sun, Jun 07, 2026 at 11:46:34PM -0700, H. Peter Anvin wrote:
>> WRxSBASE does a 64-bit write,
>
> When REX.W.
>
> The SDM text is confusing:
>
> "If no REX.W prefix is used, the operand size is 32 bits; the upper 32 bits of
> the source register are ignored and upper 32 bits of the base address (for FS
> or GS) are cleared."
>
> Does this last part that GS is cleared, refer to when WRGSBASE is used with no
> REX.W or in general?
>
Without REX.W (e.g. wrgsbase %eax as opposed to wrgsbase %rax).
>> but for GS it would incorrectly address the kernel GS.base.
>
> What does that mean?
>
It means that in kernel mode, it is the currently active GS.base that is
written (or read with rdgsbase), that is, the one that belongs to
kernel, not the user space one in what is confusingly enough called
MSR_KERNEL_GS_BASE.
In other words, not the one we want to task switch, *unless* you are in
IDT mode and can surround it with SWAPGS.
-hpa
next prev parent reply other threads:[~2026-06-08 17:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 1:53 Borislav Petkov
2026-06-04 9:17 ` Andrew Cooper
2026-06-05 2:24 ` Borislav Petkov
2026-06-05 2:36 ` H. Peter Anvin
2026-06-05 2:54 ` Borislav Petkov
2026-06-05 3:20 ` H. Peter Anvin
2026-06-05 4:26 ` Borislav Petkov
2026-06-05 4:30 ` H. Peter Anvin
2026-06-05 4:38 ` Borislav Petkov
2026-06-05 5:05 ` H. Peter Anvin
2026-06-05 9:13 ` Andrew Cooper
2026-06-05 15:13 ` H. Peter Anvin
2026-06-05 15:16 ` Andrew Cooper
2026-06-05 15:51 ` H. Peter Anvin
2026-06-05 17:17 ` Borislav Petkov
2026-06-08 6:46 ` H. Peter Anvin
2026-06-08 14:38 ` Borislav Petkov
2026-06-08 17:30 ` H. Peter Anvin [this message]
2026-06-08 20:05 ` Borislav Petkov
2026-06-08 21:21 ` Borislav Petkov
2026-06-08 21:52 ` H. Peter Anvin
2026-06-08 22:58 ` Andrew Cooper
2026-06-18 1:09 ` Borislav Petkov
2026-06-18 10:22 ` David Laight
2026-06-18 18:17 ` H. Peter Anvin
2026-06-18 21:25 ` H. Peter Anvin
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=87cfce38-4b5a-4014-a098-2c43e3067df1@zytor.com \
--to=hpa@zytor.com \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--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®