It was trying to do too many things at once and there was no clear way of
defining what it was meant to do. This commit splits the function in two.
1. A function to return the FPU to power-on reset values.
2. A x87/SSE state loader (equivalent to the old function when it took
a data pointer).
The old function also had a concept of "default" values that the FPU
would be configured for in some cases but not others. This patch removes
that 3rd vague initial state and replaces it with power-on reset.
While doing this make sure the abridged control tag is consistent with the
manuals and starts as 0xFF
Signed-off-by: Alejandro Vallejo <alejandro.vallejo@cloud.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
--
@Jan: The patch changed substantially. Are you still ok with this R-by?
v4:
* Reworded commit message and title
* Remove vcpu_default_fpu() and replaced its uses with vcpu_reset_fpu()
* s/FTW_RESET/FXSAVE_FTW_RESET/ (plus comment)
* Remove FCW_DEFAULT, as it's the leftover reset value from the 80287
(which we largely don't care about anymore).
---
xen/arch/x86/domain.c | 7 +++--
xen/arch/x86/hvm/hvm.c | 12 +++-----
xen/arch/x86/i387.c | 51 +++++++++++--------------------
xen/arch/x86/include/asm/i387.h | 21 ++++++++++---
xen/arch/x86/include/asm/xstate.h | 1 +
5 files changed, 45 insertions(+), 47 deletions(-)
diff --git a/xen/arch/x86/domain.c b/xen/arch/x86/domain.c
index 89aad7e8978f..78a13e6812c9 100644
--- a/xen/arch/x86/domain.c
+++ b/xen/arch/x86/domain.c
@@ -1186,9 +1186,10 @@ int arch_set_info_guest(
is_pv_64bit_domain(d) )
v->arch.flags &= ~TF_kernel_mode;
- vcpu_setup_fpu(v, v->arch.xsave_area,
- flags & VGCF_I387_VALID ? &c.nat->fpu_ctxt : NULL,
- FCW_DEFAULT);
+ if ( flags & VGCF_I387_VALID )
+ vcpu_setup_fpu(v, &c.nat->fpu_ctxt);
+ else
+ vcpu_reset_fpu(v);
if ( !compat )
{
diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/hvm/hvm.c
index 77fe282118f7..44f4964aa036 100644
--- a/xen/arch/x86/hvm/hvm.c
+++ b/xen/arch/x86/hvm/hvm.c
@@ -1163,10 +1163,10 @@ static int cf_check hvm_load_cpu_ctxt(struct domain *d, hvm_domain_context_t *h)
seg.attr = ctxt.ldtr_arbytes;
hvm_set_segment_register(v, x86_seg_ldtr, &seg);
- /* Cover xsave-absent save file restoration on xsave-capable host. */
- vcpu_setup_fpu(v, xsave_enabled(v) ? NULL : v->arch.xsave_area,
- ctxt.flags & XEN_X86_FPU_INITIALISED ? ctxt.fpu_regs : NULL,
- FCW_RESET);
+ if ( ctxt.flags & XEN_X86_FPU_INITIALISED )
+ vcpu_setup_fpu(v, &ctxt.fpu_regs);
+ else
+ vcpu_reset_fpu(v);
v->arch.user_regs.rax = ctxt.rax;
v->arch.user_regs.rbx = ctxt.rbx;
@@ -4006,9 +4006,7 @@ void hvm_vcpu_reset_state(struct vcpu *v, uint16_t cs, uint16_t ip)
v->arch.guest_table = pagetable_null();
}
- if ( v->arch.xsave_area )
- v->arch.xsave_area->xsave_hdr.xstate_bv = 0;
- vcpu_setup_fpu(v, v->arch.xsave_area, NULL, FCW_RESET);
+ vcpu_reset_fpu(v);
arch_vcpu_regs_init(v);
v->arch.user_regs.rip = ip;
diff --git a/xen/arch/x86/i387.c b/xen/arch/x86/i387.c
index fbb9d3584a3d..916d9b572598 100644
--- a/xen/arch/x86/i387.c
+++ b/xen/arch/x86/i387.c
@@ -303,41 +303,26 @@ int vcpu_init_fpu(struct vcpu *v)
return xstate_alloc_save_area(v);
}
-void vcpu_setup_fpu(struct vcpu *v, struct xsave_struct *xsave_area,
- const void *data, unsigned int fcw_default)
+void vcpu_reset_fpu(struct vcpu *v)
{
- fpusse_t *fpu_sse = &v->arch.xsave_area->fpu_sse;
-
- ASSERT(!xsave_area || xsave_area == v->arch.xsave_area);
-
- v->fpu_initialised = !!data;
-
- if ( data )
- {
- memcpy(fpu_sse, data, sizeof(*fpu_sse));
- if ( xsave_area )
- xsave_area->xsave_hdr.xstate_bv = XSTATE_FP_SSE;
- }
- else if ( xsave_area && fcw_default == FCW_DEFAULT )
- {
- xsave_area->xsave_hdr.xstate_bv = 0;
- fpu_sse->mxcsr = MXCSR_DEFAULT;
- }
- else
- {
- memset(fpu_sse, 0, sizeof(*fpu_sse));
- fpu_sse->fcw = fcw_default;
- fpu_sse->mxcsr = MXCSR_DEFAULT;
- if ( v->arch.xsave_area )
- {
- v->arch.xsave_area->xsave_hdr.xstate_bv &= ~XSTATE_FP_SSE;
- if ( fcw_default != FCW_DEFAULT )
- v->arch.xsave_area->xsave_hdr.xstate_bv |= X86_XCR0_X87;
- }
- }
+ v->fpu_initialised = false;
+ *v->arch.xsave_area = (struct xsave_struct) {
+ .fpu_sse = {
+ .mxcsr = MXCSR_DEFAULT,
+ .fcw = FCW_RESET,
+ .ftw = FXSAVE_FTW_RESET,
+ },
+ .xsave_hdr.xstate_bv = X86_XCR0_X87,
+ };
+}
- if ( xsave_area )
- xsave_area->xsave_hdr.xcomp_bv = 0;
+void vcpu_setup_fpu(struct vcpu *v, const void *data)
+{
+ v->fpu_initialised = true;
+ *v->arch.xsave_area = (struct xsave_struct) {
+ .fpu_sse = *(const fpusse_t*)data,
+ .xsave_hdr.xstate_bv = XSTATE_FP_SSE,
+ };
}
/* Free FPU's context save area */
diff --git a/xen/arch/x86/include/asm/i387.h b/xen/arch/x86/include/asm/i387.h
index a783549db991..652d7ad2deb6 100644
--- a/xen/arch/x86/include/asm/i387.h
+++ b/xen/arch/x86/include/asm/i387.h
@@ -31,10 +31,23 @@ void vcpu_restore_fpu_nonlazy(struct vcpu *v, bool need_stts);
void vcpu_restore_fpu_lazy(struct vcpu *v);
void vcpu_save_fpu(struct vcpu *v);
void save_fpu_enable(void);
-
int vcpu_init_fpu(struct vcpu *v);
-struct xsave_struct;
-void vcpu_setup_fpu(struct vcpu *v, struct xsave_struct *xsave_area,
- const void *data, unsigned int fcw_default);
void vcpu_destroy_fpu(struct vcpu *v);
+
+/*
+ * Restore v's FPU to power-on reset values
+ *
+ * @param v vCPU containing the FPU
+ */
+void vcpu_reset_fpu(struct vcpu *v);
+
+/*
+ * Load x87/SSE state into v's FPU
+ *
+ * Overrides the XSAVE header to set the state components to be x87 and SSE.
+ *
+ * @param v vCPU containing the FPU
+ * @param data 512-octet blob for x87/SSE state
+ */
+void vcpu_setup_fpu(struct vcpu *v, const void *data);
#endif /* __ASM_I386_I387_H */
diff --git a/xen/arch/x86/include/asm/xstate.h b/xen/arch/x86/include/asm/xstate.h
index b4ee5559534a..07017cc4edfd 100644
--- a/xen/arch/x86/include/asm/xstate.h
+++ b/xen/arch/x86/include/asm/xstate.h
@@ -14,6 +14,7 @@
#define FCW_DEFAULT 0x037f
#define FCW_RESET 0x0040
+#define FXSAVE_FTW_RESET 0xFF /* Abridged Tag Word format */
#define MXCSR_DEFAULT 0x1f80
extern uint32_t mxcsr_mask;
--
2.46.0
On 07.10.2024 17:52, Alejandro Vallejo wrote: > It was trying to do too many things at once and there was no clear way of > defining what it was meant to do. This commit splits the function in two. > > 1. A function to return the FPU to power-on reset values. > 2. A x87/SSE state loader (equivalent to the old function when it took > a data pointer). > > The old function also had a concept of "default" values that the FPU > would be configured for in some cases but not others. This patch removes > that 3rd vague initial state and replaces it with power-on reset. > > While doing this make sure the abridged control tag is consistent with the > manuals and starts as 0xFF > > Signed-off-by: Alejandro Vallejo <alejandro.vallejo@cloud.com> > Reviewed-by: Jan Beulich <jbeulich@suse.com> > -- > @Jan: The patch changed substantially. Are you still ok with this R-by? I am. However in such a situation imo you'd better drop the tag, for it to be re-offered (if desired). It can very well happen that the person simply doesn't notice the question pointed at them. Jan
On Tue Oct 8, 2024 at 7:37 AM BST, Jan Beulich wrote: > On 07.10.2024 17:52, Alejandro Vallejo wrote: > > It was trying to do too many things at once and there was no clear way of > > defining what it was meant to do. This commit splits the function in two. > > > > 1. A function to return the FPU to power-on reset values. > > 2. A x87/SSE state loader (equivalent to the old function when it took > > a data pointer). > > > > The old function also had a concept of "default" values that the FPU > > would be configured for in some cases but not others. This patch removes > > that 3rd vague initial state and replaces it with power-on reset. > > > > While doing this make sure the abridged control tag is consistent with the > > manuals and starts as 0xFF > > > > Signed-off-by: Alejandro Vallejo <alejandro.vallejo@cloud.com> > > Reviewed-by: Jan Beulich <jbeulich@suse.com> > > -- > > @Jan: The patch changed substantially. Are you still ok with this R-by? > > I am. However in such a situation imo you'd better drop the tag, for it to > be re-offered (if desired). It can very well happen that the person simply > doesn't notice the question pointed at them. > > Jan Noted for next time. Thanks for the promptness! Cheers, Alejandro
© 2016 - 2024 Red Hat, Inc.