mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Xin Li <xin@zytor.com>, Borislav Petkov <bp@kernel.org>,
	Xin Li <xin3.li@intel.com>, X86 ML <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/cpufeatures: Correct LKGS feature flag description
Date: Wed, 15 Oct 2025 20:12:08 -0700	[thread overview]
Message-ID: <4CDD31CE-7040-4ADB-B3F1-E095E3C5BDF5@zytor.com> (raw)
In-Reply-To: <20251015154911.GCaO_Cd0XNyE8bi5Db@fat_crate.local>

On October 15, 2025 8:49:11 AM PDT, Borislav Petkov <bp@alien8.de> wrote:
>On Wed, Oct 15, 2025 at 08:44:55AM -0700, H. Peter Anvin wrote:
>> >> Except that that is also wrong, because that's not all of what the instruction does. "Load user space GS" is really what it does, despite the initiate historical naming.
>> >> 
>> >
>> >Do you mean the load of GS attributes by LKGS is still missing?
>> 
>> Yes. It's really a modified MOV GS,... instruction that loads the base, limit, selector, and attributes; it just loads the base into a different place.
>
>Ok, "Load user space GS base" it is. Considering how you can't load any other
>GS.base due to it GPing for CPL > 0.
>

No, "load user space GS." It loads everything, not just the base.

  reply	other threads:[~2025-10-16  3:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-15 10:35 Borislav Petkov
2025-10-15 15:08 ` Xin Li
2025-10-15 15:18   ` H. Peter Anvin
2025-10-15 15:34     ` Xin Li
2025-10-15 15:36       ` H. Peter Anvin
2025-10-15 15:41         ` Xin Li
2025-10-15 15:44           ` H. Peter Anvin
2025-10-15 15:49             ` Borislav Petkov
2025-10-16  3:12               ` H. Peter Anvin [this message]
2025-10-16 12:41                 ` Borislav Petkov

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=4CDD31CE-7040-4ADB-B3F1-E095E3C5BDF5@zytor.com \
    --to=hpa@zytor.com \
    --cc=bp@alien8.de \
    --cc=bp@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@kernel.org \
    --cc=xin3.li@intel.com \
    --cc=xin@zytor.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

all inboxes | Powered by JetHome®