Linux Documentation
 help / color / mirror / Atom feed
From: Sohil Mehta <sohil.mehta@intel.com>
To: Dave Hansen <dave.hansen@linux.intel.com>, <x86@kernel.org>,
	"Andy Lutomirski" <luto@kernel.org>,
	Borislav Petkov <bp@alien8.de>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
	"H . Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	"Kiryl Shutsemau" <kas@kernel.org>,
	Brendan Jackman <jackmanb@google.com>,
	"Sean Christopherson" <seanjc@google.com>,
	Nam Cao <namcao@linutronix.de>,
	"Cedric Xing" <cedric.xing@intel.com>,
	Rick Edgecombe <rick.p.edgecombe@intel.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Tony Luck <tony.luck@intel.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	"Maciej Wieczor-Retman" <m.wieczorretman@pm.me>,
	<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/5] x86: Enable LASS support with vsyscall=xonly mode
Date: Thu, 19 Mar 2026 11:46:57 -0700	[thread overview]
Message-ID: <e5044e66-cdf8-4460-a0b1-5a3ff9130f3b@intel.com> (raw)
In-Reply-To: <20260309181029.398498-1-sohil.mehta@intel.com>

On 3/9/2026 11:10 AM, Sohil Mehta wrote:
> Linear Address Space Separation (LASS) is currently disabled [1] when
> support for vsyscall emulation is configured. This series extends LASS
> support specifically to the default mode (vsyscall=xonly).
> 

x86 maintainers, this series seems to be ready to me. Are there any
additional changes you are looking for?

There are a couple of small vsyscall related improvements that are based
on this series. They are completely independent of LASS, so I haven't
included them here.

https://lore.kernel.org/lkml/20260305232136.224922-1-hpa@zytor.com/

https://lore.kernel.org/lkml/51f5dc8d-e130-4769-84e2-588553c7fde3@intel.com/

Please let me know if you would prefer that I include them at the end
and send out another version.

> Sohil Mehta (5):
>   x86/vsyscall: Reorganize the page fault emulation code
>   x86/traps: Consolidate user fixups in the #GP handler
>   x86/vsyscall: Restore vsyscall=xonly mode under LASS
>   x86/vsyscall: Disable LASS if vsyscall mode is set to EMULATE
>   x86/cpu: Remove LASS restriction on vsyscall emulation
> 
>  .../admin-guide/kernel-parameters.txt         |  4 +-
>  arch/x86/entry/vsyscall/vsyscall_64.c         | 91 ++++++++++++-------
>  arch/x86/include/asm/vsyscall.h               | 13 ++-
>  arch/x86/kernel/cpu/common.c                  | 15 ---
>  arch/x86/kernel/traps.c                       | 12 ++-
>  arch/x86/kernel/umip.c                        |  3 +
>  arch/x86/mm/fault.c                           |  2 +-
>  7 files changed, 79 insertions(+), 61 deletions(-)
> 
> 
> base-commit: 68400c1aaf02636a97c45ba198110b66feb270a9


      parent reply	other threads:[~2026-03-19 18:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 18:10 [PATCH v3 0/5] x86: Enable LASS support with vsyscall=xonly mode Sohil Mehta
2026-03-09 18:10 ` [PATCH v3 1/5] x86/vsyscall: Reorganize the page fault emulation code Sohil Mehta
2026-03-09 18:10 ` [PATCH v3 2/5] x86/traps: Consolidate user fixups in the #GP handler Sohil Mehta
2026-03-09 18:10 ` [PATCH v3 3/5] x86/vsyscall: Restore vsyscall=xonly mode under LASS Sohil Mehta
2026-03-09 18:10 ` [PATCH v3 4/5] x86/vsyscall: Disable LASS if vsyscall mode is set to EMULATE Sohil Mehta
2026-03-09 18:10 ` [PATCH v3 5/5] x86/cpu: Remove LASS restriction on vsyscall emulation Sohil Mehta
2026-03-19 18:46 ` Sohil Mehta [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=e5044e66-cdf8-4460-a0b1-5a3ff9130f3b@intel.com \
    --to=sohil.mehta@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=bp@alien8.de \
    --cc=cedric.xing@intel.com \
    --cc=corbet@lwn.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jackmanb@google.com \
    --cc=kas@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=m.wieczorretman@pm.me \
    --cc=mingo@redhat.com \
    --cc=namcao@linutronix.de \
    --cc=peterz@infradead.org \
    --cc=rick.p.edgecombe@intel.com \
    --cc=seanjc@google.com \
    --cc=skhan@linuxfoundation.org \
    --cc=tglx@kernel.org \
    --cc=tony.luck@intel.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