From: David Laight <david.laight.linux@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
"H. Peter Anvin" <hpa@zytor.com>, x86-ML <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Save a WRMSR GS.base?
Date: Thu, 18 Jun 2026 11:22:56 +0100 [thread overview]
Message-ID: <20260618112256.1ed7904b@pumpkin> (raw)
In-Reply-To: <20260618010902.GAajNFLjwKOM-Cdj5l@fat_crate.local>
On Wed, 17 Jun 2026 18:09:02 -0700
Borislav Petkov <bp@alien8.de> wrote:
> Ok,
>
> I think I incorporated them all:
...
> +Btw, while running in kernel mode, MSR_KERNEL_GS_BASE contains actually the
> +*user* GS.base. Thus, the naming can be confusing. Unless one thinks of it as
> +the kernel's access to GS.base as MSRs are accessible only in CPL0.
That last sentence doesn't read right. Maybe:
The naming of MSR_KERNEL_GS_BASE is rather confusing.
In can only be accessed in kernel mode where it normally contains the
USER GS.base.
The only time it contains the KERNEL GS.base is on system call/interrupt entry
prior to swapgs being executed (and late in the return to user paths).
As an aside I think a 32bit program can detect hardware interrupts.
If %gs/%fs is loaded from an LDT and then the LDT entry changed (eg
a different limit) then the new limit will be loaded by the ISR
return path.
I seem to remember deciding that it was impossible to actual restore
the actual register value.
David
next prev parent reply other threads:[~2026-06-18 10:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 1:53 Save a WRMSR GS.base? 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
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 [this message]
2026-06-18 18:17 ` 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=20260618112256.1ed7904b@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--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 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.