From: Andy Lutomirski <luto@kernel.org>
To: x86@kernel.org
Cc: Dave Hansen <dave.hansen@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@kernel.org>
Subject: [PATCH 2/2] x86/fpu: Improve FPU APIs for independent features
Date: Thu, 10 Jun 2021 22:13:37 -0700 [thread overview]
Message-ID: <657f57d4a50f0bdab7c74bf8ca47b413583b6db4.1623388344.git.luto@kernel.org> (raw)
In-Reply-To: <cover.1623388344.git.luto@kernel.org>
Having the functions that save and restore independent features accept,
but ignore, non-independent features is confusing, so instead require
that only independent features be independently saved and restored.
Remove a bunch of nonsense comments from the save and restore functions:
saving and restoring the XSAVE header makes no sense.
Document that fpu__clear_all() does not clear independent features.
Signed-off-by: Andy Lutomirski <luto@kernel.org>
---
arch/x86/include/asm/fpu/xstate.h | 5 ++++-
arch/x86/kernel/fpu/core.c | 3 +++
arch/x86/kernel/fpu/xstate.c | 33 +++++++++++--------------------
3 files changed, 19 insertions(+), 22 deletions(-)
diff --git a/arch/x86/include/asm/fpu/xstate.h b/arch/x86/include/asm/fpu/xstate.h
index 5802b1715c7f..3bc5e6c9e47a 100644
--- a/arch/x86/include/asm/fpu/xstate.h
+++ b/arch/x86/include/asm/fpu/xstate.h
@@ -34,7 +34,10 @@
XFEATURE_MASK_BNDREGS | \
XFEATURE_MASK_BNDCSR)
-/* All currently supported supervisor features */
+/*
+ * All currently supported supervisor features that are saved and
+ * restored as part of the main task XSAVE buffers.
+ */
#define XFEATURE_MASK_SUPERVISOR_SUPPORTED (XFEATURE_MASK_PASID)
/*
diff --git a/arch/x86/kernel/fpu/core.c b/arch/x86/kernel/fpu/core.c
index 571220ac8bea..9af361464c66 100644
--- a/arch/x86/kernel/fpu/core.c
+++ b/arch/x86/kernel/fpu/core.c
@@ -390,6 +390,9 @@ void fpu__clear_user_states(struct fpu *fpu)
fpu__clear(fpu, true);
}
+/*
+ * This does not affect independent features -- see XFEATURE_MASK_INDEPENDENT.
+ */
void fpu__clear_all(struct fpu *fpu)
{
fpu__clear(fpu, false);
diff --git a/arch/x86/kernel/fpu/xstate.c b/arch/x86/kernel/fpu/xstate.c
index d582275164ad..15bb87f4f510 100644
--- a/arch/x86/kernel/fpu/xstate.c
+++ b/arch/x86/kernel/fpu/xstate.c
@@ -1292,29 +1292,26 @@ void copy_supervisor_to_kernel(struct xregs_state *xstate)
* @xstate: A pointer to an xsave area
* @mask: Represent the independent supervisor features saved into the xsave area
*
- * Only the independent supervisor states sets in the mask are saved into the xsave
- * area (See the comment in XFEATURE_MASK_INDEPENDENT for the details of independent
- * supervisor feature). Besides the independent supervisor states, the legacy
- * region and XSAVE header are also saved into the xsave area. The supervisor
- * features in the XFEATURE_MASK_SUPERVISOR_SUPPORTED and
- * XFEATURE_MASK_SUPERVISOR_UNSUPPORTED are not saved.
+ * The XSAVE header in the target buffer must already be initialized, as the
+ * XSAVES instruction may not fully initialize the XSAVE header.
*
* The xsave area must be 64-bytes aligned.
*/
void copy_independent_supervisor_to_kernel(struct xregs_state *xstate, u64 mask)
{
- u64 independent_mask = xfeatures_mask_independent() & mask;
u32 lmask, hmask;
int err;
+ WARN_ON_FPU(mask & ~xfeatures_mask_independent());
+
if (WARN_ON_FPU(!boot_cpu_has(X86_FEATURE_XSAVES)))
return;
- if (WARN_ON_FPU(!independent_mask))
+ if (WARN_ON_FPU(!mask))
return;
- lmask = independent_mask;
- hmask = independent_mask >> 32;
+ lmask = mask;
+ hmask = mask >> 32;
XSTATE_OP(XSAVES, xstate, lmask, hmask, err);
@@ -1328,29 +1325,23 @@ void copy_independent_supervisor_to_kernel(struct xregs_state *xstate, u64 mask)
* @xstate: A pointer to an xsave area
* @mask: Represent the independent supervisor features restored from the xsave area
*
- * Only the independent supervisor states sets in the mask are restored from the
- * xsave area (See the comment in XFEATURE_MASK_INDEPENDENT for the details of
- * independent supervisor feature). Besides the independent supervisor states, the
- * legacy region and XSAVE header are also restored from the xsave area. The
- * supervisor features in the XFEATURE_MASK_SUPERVISOR_SUPPORTED and
- * XFEATURE_MASK_SUPERVISOR_UNSUPPORTED are not restored.
- *
* The xsave area must be 64-bytes aligned.
*/
void copy_kernel_to_independent_supervisor(struct xregs_state *xstate, u64 mask)
{
- u64 independent_mask = xfeatures_mask_independent() & mask;
u32 lmask, hmask;
int err;
+ WARN_ON_FPU(mask & ~xfeatures_mask_independent());
+
if (WARN_ON_FPU(!boot_cpu_has(X86_FEATURE_XSAVES)))
return;
- if (WARN_ON_FPU(!independent_mask))
+ if (WARN_ON_FPU(!mask))
return;
- lmask = independent_mask;
- hmask = independent_mask >> 32;
+ lmask = mask;
+ hmask = mask >> 32;
XSTATE_OP(XRSTORS, xstate, lmask, hmask, err);
--
2.31.1
prev parent reply other threads:[~2021-06-11 5:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 5:13 [PATCH 0/2] x86/fpu: Clean up "dynamic" APIs Andy Lutomirski
2021-06-11 5:13 ` [PATCH 1/2] x86/fpu: Rename "dynamic" XSTATEs to "independent" Andy Lutomirski
2021-06-11 8:01 ` Peter Zijlstra
2021-06-11 13:30 ` Thomas Gleixner
2021-06-23 22:09 ` [tip: x86/fpu] " tip-bot2 for Andy Lutomirski
2021-06-11 5:13 ` Andy Lutomirski [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=657f57d4a50f0bdab7c74bf8ca47b413583b6db4.1623388344.git.luto@kernel.org \
--to=luto@kernel.org \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®