From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
the arch/x86 maintainers <x86@kernel.org>,
"Chang S. Bae" <chang.seok.bae@intel.com>,
Oleg Nesterov <oleg@redhat.com>
Subject: [GIT PULL] x86/fpu updates for v6.17
Date: Tue, 29 Jul 2025 09:12:14 +0200 [thread overview]
Message-ID: <aIh0TvRcSPfV0ULC@gmail.com> (raw)
Linus,
Please pull the latest x86/fpu Git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-fpu-2025-07-29
# HEAD: 1cec9ac2d071cfd2da562241aab0ef701355762a x86/fpu: Delay instruction pointer fixup until after warning
x86 FPU changes for v6.17:
- Most of the changes are related to the implementation of
CET supervisor state support for guests, and its preparatory
changes. (Chao Gao)
- Improve/fix the debug output for unexpected FPU exceptions
(Dave Hansen)
Thanks,
Ingo
------------------>
Chao Gao (4):
x86/fpu/xstate: Differentiate default features for host and guest FPUs
x86/fpu: Initialize guest FPU permissions from guest defaults
x86/fpu: Initialize guest fpstate and FPU pseudo container from guest defaults
x86/fpu: Remove xfd argument from __fpstate_reset()
Dave Hansen (1):
x86/fpu: Delay instruction pointer fixup until after warning
Yang Weijiang (2):
x86/fpu/xstate: Introduce "guest-only" supervisor xfeature set
x86/fpu/xstate: Add CET supervisor xfeature support as a guest-only feature
arch/x86/include/asm/fpu/types.h | 49 +++++++++++++++++++++++++++++++-----
arch/x86/include/asm/fpu/xstate.h | 9 ++++---
arch/x86/kernel/fpu/core.c | 53 ++++++++++++++++++++++++++++-----------
arch/x86/kernel/fpu/init.c | 1 +
arch/x86/kernel/fpu/xstate.c | 40 +++++++++++++++++++++++------
arch/x86/mm/extable.c | 5 ++--
6 files changed, 124 insertions(+), 33 deletions(-)
next reply other threads:[~2025-07-29 7:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 7:12 Ingo Molnar [this message]
2025-07-30 3:39 ` [GIT PULL] x86/fpu updates for v6.17 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=aIh0TvRcSPfV0ULC@gmail.com \
--to=mingo@kernel.org \
--cc=chang.seok.bae@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.