From: Dave Hansen <dave.hansen@linux.intel.com>
To: torvalds@linux-foundation.org
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: [GIT PULL] x86/cpu for 7.1-rc1
Date: Mon, 13 Apr 2026 08:42:35 -0700 [thread overview]
Message-ID: <20260413154235.1543087-1-dave.hansen@linux.intel.com> (raw)
Hi Linus,
Please pull some x86/cpu changes for 7.1-rc1.
The existing Linear Address Space Separation (LASS) support punted on
support for common EFI and vsyscall configs. Complete the
implementation by supporting EFI and vsyscall=xonly.
The last few commits clean up CPUID use in the Intel "avs" sound
driver and update the x86-cpuid-db file.
--
The following changes since commit 11439c4635edd669ae435eec308f4ab8a0804808:
Linux 7.0-rc2 (2026-03-01 15:39:31 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_cpu_for_7.1-rc1
for you to fetch changes up to 124ad3034ec0029b65178f3ab8a6cdca5a0b0519:
tools/x86/kcpuid: Update bitfields to x86-cpuid-db v3.0 (2026-03-28 17:28:35 +0100)
----------------------------------------------------------------
- Complete LASS enabling: deal with vsyscall and EFI
- Clean up CPUID usage in newer Intel audio driver
----------------------------------------------------------------
Ahmed S. Darwish (3):
ASoC: Intel: avs: Check maximum valid CPUID leaf
ASoC: Intel: avs: Include CPUID header at file scope
tools/x86/kcpuid: Update bitfields to x86-cpuid-db v3.0
Sohil Mehta (8):
x86/cpu: Defer LASS enabling until userspace comes up
x86/efi: Disable LASS while executing runtime services
x86/cpu: Remove LASS restriction on EFI
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
Documentation/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 | 35 +-
arch/x86/kernel/traps.c | 12 +-
arch/x86/kernel/umip.c | 3 +
arch/x86/mm/fault.c | 2 +-
arch/x86/platform/efi/efi_64.c | 35 ++
sound/soc/intel/Kconfig | 2 +-
sound/soc/intel/avs/tgl.c | 38 +-
tools/arch/x86/kcpuid/cpuid.csv | 671 ++++++++++++------------
11 files changed, 506 insertions(+), 400 deletions(-)
next reply other threads:[~2026-04-13 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 15:42 Dave Hansen [this message]
2026-04-14 21:45 ` [GIT PULL] x86/cpu for 7.1-rc1 pr-tracker-bot
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=20260413154235.1543087-1-dave.hansen@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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