public inbox for linux-efi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: Sohil Mehta <sohil.mehta@intel.com>
Cc: <x86@kernel.org>, Dave Hansen <dave.hansen@linux.intel.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "Borislav Petkov" <bp@alien8.de>,
	Ard Biesheuvel <ardb@kernel.org>,
	"H . Peter Anvin" <hpa@zytor.com>,
	Andy Lutomirski <luto@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	"Kirill A . Shutemov" <kas@kernel.org>,
	"Rick Edgecombe" <rick.p.edgecombe@intel.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	<linux-kernel@vger.kernel.org>, <linux-efi@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] x86: Extend LASS support to EFI configurations
Date: Thu, 5 Feb 2026 09:47:41 -0800	[thread overview]
Message-ID: <aYTXvX24FuBT49bd@agluck-desk3> (raw)
In-Reply-To: <20260120234730.2215498-1-sohil.mehta@intel.com>

On Tue, Jan 20, 2026 at 03:47:27PM -0800, Sohil Mehta wrote:
> Linear Address Space Separation (LASS) is currently disabled [1] when
> support for vsyscall emulation or EFI is compiled in. This series
> extends LASS support to EFI-enabled configurations.

I tried these patches on a LASS-capable system with a kernel built with
CONFIG_X86_VSYSCALL_EMULATION disabled, and traces added to efi_disable_lass()
and efi_enable_lass().

System boots OK (with a bunch of my trace messages showing that CR4.LASS
was disabled/enabled around EFI calls from several CPUs).

Just for grins I commented out the CR4 changes from the efi_disable_lass()
and efi_enable_lass(). System still boots OK, so it seems the EFI runtime
calls during boot don't have any of the BIOS bugs that require LASS disable.

Tested-by: Tony Luck <tony.luck@intel.com>

-Tony

  parent reply	other threads:[~2026-02-05 17:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20 23:47 [PATCH v2 0/3] x86: Extend LASS support to EFI configurations Sohil Mehta
2026-01-20 23:47 ` [PATCH v2 1/3] x86/cpu: Defer LASS enabling until userspace comes up Sohil Mehta
2026-02-19 21:02   ` Sohil Mehta
2026-03-03 17:41     ` Dave Hansen
2026-01-20 23:47 ` [PATCH v2 2/3] x86/efi: Disable LASS while executing runtime services Sohil Mehta
2026-01-20 23:47 ` [PATCH v2 3/3] x86/cpu: Remove LASS restriction on EFI Sohil Mehta
2026-02-04 17:08 ` [PATCH v2 0/3] x86: Extend LASS support to EFI configurations Maciej Wieczor-Retman
2026-02-05 17:47 ` Luck, Tony [this message]
2026-02-24 18:45 ` Sohil Mehta
2026-02-24 18:49   ` Ard Biesheuvel
2026-03-03 17:42   ` Dave Hansen
  -- strict thread matches above, loose matches on Subject: below --
2026-02-04 17:03 Maciej Wieczor-Retman

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=aYTXvX24FuBT49bd@agluck-desk3 \
    --to=tony.luck@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ardb@kernel.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kas@kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rick.p.edgecombe@intel.com \
    --cc=sohil.mehta@intel.com \
    --cc=tglx@linutronix.de \
    --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