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/misc for 6.19-rc1
Date: Mon, 1 Dec 2025 14:54:20 -0800 [thread overview]
Message-ID: <20251201225420.728817-1-dave.hansen@linux.intel.com> (raw)
Hi Linus,
Please pull some x86/misc changes for 6.19-rc1. The most significant
are some changes to ensure that symbols exported for KVM are used only
by KVM modules themselves, along with some related cleanups.
In true x86/misc fashion, the other patch is completely unrelated and
just enhances an existing pr_warn() to make it clear to users how they
have tainted their kernel when something is mucking with MSRs.
--
The following changes since commit 6146a0f1dfae5d37442a9ddcba012add260bceb0:
Linux 6.18-rc4 (2025-11-02 11:28:02 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_misc_for_6.19-rc1
for you to fetch changes up to 6276c67f2bc4aeaf350a7cf889c33c38b3330ea9:
x86: Restrict KVM-induced symbol exports to KVM modules where obvious/possible (2025-11-12 15:29:38 -0800)
----------------------------------------------------------------
* Make MSR-induced taint easier for users to track down
* Restrict KVM-specific exports to KVM itself
----------------------------------------------------------------
Marc Herbert (1):
x86/msr: Add CPU_OUT_OF_SPEC taint name to "unrecognized" pr_warn(msg)
Sean Christopherson (4):
x86/bugs: Drop unnecessary export of "x86_spec_ctrl_base"
x86/mtrr: Drop unnecessary export of "mtrr_state"
x86/mm: Drop unnecessary export of "ptdump_walk_pgd_level_debugfs"
x86: Restrict KVM-induced symbol exports to KVM modules where obvious/possible
arch/x86/entry/entry.S | 7 ++--
arch/x86/entry/entry_64.S | 3 +-
arch/x86/entry/entry_64_fred.S | 3 +-
arch/x86/events/amd/core.c | 5 +--
arch/x86/events/core.c | 7 ++--
arch/x86/events/intel/lbr.c | 3 +-
arch/x86/events/intel/pt.c | 7 ++--
arch/x86/include/asm/kvm_types.h | 5 +++
arch/x86/kernel/apic/apic.c | 3 +-
arch/x86/kernel/apic/apic_common.c | 3 +-
arch/x86/kernel/cpu/amd.c | 4 +--
arch/x86/kernel/cpu/bugs.c | 18 +++++-----
arch/x86/kernel/cpu/bus_lock.c | 3 +-
arch/x86/kernel/cpu/common.c | 7 ++--
arch/x86/kernel/cpu/mtrr/generic.c | 1 -
arch/x86/kernel/cpu/sgx/main.c | 3 +-
arch/x86/kernel/cpu/sgx/virt.c | 5 +--
arch/x86/kernel/e820.c | 3 +-
arch/x86/kernel/fpu/core.c | 21 ++++++------
arch/x86/kernel/fpu/xstate.c | 7 ++--
arch/x86/kernel/hw_breakpoint.c | 3 +-
arch/x86/kernel/irq.c | 3 +-
arch/x86/kernel/kvm.c | 5 +--
arch/x86/kernel/msr.c | 2 +-
arch/x86/kernel/nmi.c | 5 ++-
arch/x86/kernel/process_64.c | 5 ++-
arch/x86/kernel/reboot.c | 5 +--
arch/x86/kernel/tsc.c | 1 +
arch/x86/lib/cache-smp.c | 9 ++---
arch/x86/lib/msr.c | 5 +--
arch/x86/mm/dump_pagetables.c | 1 -
arch/x86/mm/pat/memtype.c | 3 +-
arch/x86/mm/tlb.c | 5 +--
arch/x86/virt/vmx/tdx/tdx.c | 69 +++++++++++++++++++-------------------
include/linux/kvm_types.h | 14 ++++++++
35 files changed, 145 insertions(+), 108 deletions(-)
next reply other threads:[~2025-12-01 22:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 22:54 Dave Hansen [this message]
2025-12-02 22:57 ` [GIT PULL] x86/misc for 6.19-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=20251201225420.728817-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