All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Vallejo <alejandro.vallejo@cloud.com>
To: xen-devel@lists.xenproject.org
Cc: "Alejandro Vallejo" <alejandro.vallejo@cloud.com>,
	"Jan Beulich" <jbeulich@suse.com>,
	"Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Subject: [PATCH v3 01/12] x86/xstate: Create map/unmap primitives for xsave areas
Date: Fri, 10 Jan 2025 13:28:12 +0000	[thread overview]
Message-ID: <20250110132823.24348-2-alejandro.vallejo@cloud.com> (raw)
In-Reply-To: <20250110132823.24348-1-alejandro.vallejo@cloud.com>

Add infrastructure to simplify ASI handling. With ASI in the picture
we'll have several different means of accessing the XSAVE area of a
given vCPU, depending on whether a domain is covered by ASI or not and
whether the vCPU is question is scheduled on the current pCPU or not.

Having these complexities exposed at the call sites becomes unwieldy
very fast. These wrappers are intended to be used in a similar way to
map_domain_page() and unmap_domain_page(); The map operation will
dispatch the appropriate pointer for each case in a future patch, while
unmap will remain a no-op where no unmap is required (e.g: when there's
no ASI) and remove the transient maping if one was required.

Follow-up patches replace all uses of raw v->arch.xsave_area by this
mechanism in preparation to add the beforementioned dispatch logic to be
added at a later time.

Signed-off-by: Alejandro Vallejo <alejandro.vallejo@cloud.com>
---
v2->v3:
  * Evaluate `v` in UNMAP (casted to void)

v1->v2:
  * Comment macros more heavily to show their performance characteristics.
  * Addressed various nits in the macro comments.
  * Macro names to uppercase.
---
 xen/arch/x86/include/asm/xstate.h | 42 +++++++++++++++++++++++++++++++
 1 file changed, 42 insertions(+)

diff --git a/xen/arch/x86/include/asm/xstate.h b/xen/arch/x86/include/asm/xstate.h
index 07017cc4edfd..ab81a4c8527e 100644
--- a/xen/arch/x86/include/asm/xstate.h
+++ b/xen/arch/x86/include/asm/xstate.h
@@ -143,4 +143,46 @@ static inline bool xstate_all(const struct vcpu *v)
            (v->arch.xcr0_accum & XSTATE_LAZY & ~XSTATE_FP_SSE);
 }
 
+/*
+ * Fetch a pointer to a vCPU's XSAVE area
+ *
+ * TL;DR: If v == current, the mapping is guaranteed to already exist.
+ *
+ * Despite the name, this macro might not actually map anything. The only case
+ * in which a mutation of page tables is strictly required is when ASI==on &&
+ * v!=current. For everything else the mapping already exists and needs not
+ * be created nor destroyed.
+ *
+ *                         +-----------------+--------------+
+ *                         |   v == current  | v != current |
+ *          +--------------+-----------------+--------------+
+ *          | ASI  enabled | per-vCPU fixmap |  actual map  |
+ *          +--------------+-----------------+--------------+
+ *          | ASI disabled |             directmap          |
+ *          +--------------+--------------------------------+
+ *
+ * There MUST NOT be outstanding maps of XSAVE areas of the non-current vCPU
+ * at the point of context switch. Otherwise, the unmap operation will
+ * misbehave.
+ *
+ * TODO: Expand the macro to the ASI cases after infra to do so is in place.
+ *
+ * @param v Owner of the XSAVE area
+ */
+#define VCPU_MAP_XSAVE_AREA(v) ((v)->arch.xsave_area)
+
+/*
+ * Drops the mapping of a vCPU's XSAVE area and nullifies its pointer on exit
+ *
+ * See VCPU_MAP_XSAVE_AREA() for additional information on the persistence of
+ * these mappings. This macro only tears down the mappings in the ASI=on &&
+ * v!=current case.
+ *
+ * TODO: Expand the macro to the ASI cases after infra to do so is in place.
+ *
+ * @param v Owner of the XSAVE area
+ * @param x XSAVE blob of v
+ */
+#define VCPU_UNMAP_XSAVE_AREA(v, x) do { (void)(v); (x) = NULL; } while(0)
+
 #endif /* __ASM_XSTATE_H */
-- 
2.47.1



  reply	other threads:[~2025-01-10 13:29 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10 13:28 [PATCH v3 00/12] x86: Address Space Isolation FPU preparations Alejandro Vallejo
2025-01-10 13:28 ` Alejandro Vallejo [this message]
2025-01-27 10:44   ` [PATCH v3 01/12] x86/xstate: Create map/unmap primitives for xsave areas Jan Beulich
2025-01-27 15:33     ` Alejandro Vallejo
2025-01-10 13:28 ` [PATCH v3 02/12] x86/hvm: Map/unmap xsave area in hvm_save_cpu_ctxt() Alejandro Vallejo
2025-01-10 13:28 ` [PATCH v3 03/12] x86/fpu: Map/umap xsave area in vcpu_{reset,setup}_fpu() Alejandro Vallejo
2025-01-10 13:28 ` [PATCH v3 04/12] x86/xstate: Map/unmap xsave area in xstate_set_init() and handle_setbv() Alejandro Vallejo
2025-01-10 13:28 ` [PATCH v3 05/12] x86/hvm: Map/unmap xsave area in hvmemul_{get,put}_fpu() Alejandro Vallejo
2025-01-10 13:28 ` [PATCH v3 06/12] x86/domctl: Map/unmap xsave area in arch_get_info_guest() Alejandro Vallejo
2025-01-10 13:28 ` [PATCH v3 07/12] x86/xstate: Map/unmap xsave area in {compress,expand}_xsave_states() Alejandro Vallejo
2025-01-27 10:46   ` Jan Beulich
2025-01-10 13:28 ` [PATCH v3 08/12] x86/emulator: Refactor FXSAVE_AREA to use wrappers Alejandro Vallejo
2025-01-27 10:52   ` Jan Beulich
2025-01-27 15:42     ` Alejandro Vallejo
2025-01-27 16:59       ` Jan Beulich
2025-03-05 15:29   ` Jan Beulich
2025-03-05 16:16     ` Alejandro Vallejo
2025-03-05 16:17       ` Jan Beulich
2025-01-10 13:28 ` [PATCH v3 09/12] x86/mpx: Map/unmap xsave area in in read_bndcfgu() Alejandro Vallejo
2025-01-27 10:57   ` Jan Beulich
2025-01-27 14:14     ` Alejandro Vallejo
2025-01-10 13:28 ` [PATCH v3 10/12] x86/fpu: Pass explicit xsave areas to fpu_(f)xsave() Alejandro Vallejo
2025-01-27 11:01   ` Jan Beulich
2025-01-27 15:43     ` Alejandro Vallejo
2025-01-10 13:28 ` [PATCH v3 11/12] x86/fpu: Pass explicit xsave areas to fpu_(f)xrstor() Alejandro Vallejo
2025-01-27 11:05   ` Jan Beulich
2025-01-27 15:48     ` Alejandro Vallejo
2025-01-27 17:01       ` Jan Beulich
2025-01-10 13:28 ` [PATCH v3 12/12] x86/xstate: Make xstate_all() and vcpu_xsave_mask() take explicit xstate Alejandro Vallejo

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=20250110132823.24348-2-alejandro.vallejo@cloud.com \
    --to=alejandro.vallejo@cloud.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=roger.pau@citrix.com \
    --cc=xen-devel@lists.xenproject.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.