kvm/svm/sev.c

37  * When this config is not defined, SEV feature is not supported and APIs in
41  * We will not have MISC_CG_RES_SEV and MISC_CG_RES_SEV_ES entries in the enum
42  * misc_res_type {} defined in linux/misc_cgroup.h.
246 	/* Guard DEACTIVATE against WBINVD/DF_FLUSH used in ASID recycling */
538 	 * Flush (on non-coherent CPUs) before LAUNCH_UPDATE encrypts pages in
555 		/* Calculate the number of pages that can be encrypted in one go. */
592 	 * traditional VMSA as it has been built so far (in prep
654 	 * The LAUNCH_UPDATE_VMSA command will perform in-place encryption of
893 	 *   - decrypt destination in an intermediate buffer
894 	 *   - copy the source buffer in an intermediate buffer
1048 	 * Flush (on non-coherent CPUs) before LAUNCH_SECRET encrypts pages in
1593 	 * Bail if these VMs are already involved in a migration to avoid
2206 	 * SEV must obviously be supported in hardware.  Sanity check that the
2233 	 * Initialize SEV ASID bitmaps. Allocate space for ASID 0 in the bitmap,
2261 	 * instruction stream, i.e. can't emulate in response to a #NPF and
2339 	 * takes a pointer to deter passing in a user address.
2346 	 * flush is still needed in order to work properly with DMA devices.
2356 	 * by leaving stale encrypted data in the cache.
2660 	 * 2) or this VMCB was executed on different host CPU in previous VMRUNs.
2701 		 * completely contained in the GHCB shared buffer area.
2965 int sev_es_string_io(struct vcpu_svm *svm, int size, unsigned int port, int in)
2978 	r = setup_vmgexit_scratch(svm, in, bytes);
2983 				    count, in);
3003 	 * if X86_FEATURE_XSAVES isn't configured in the guest to ensure host
3007 	 * guests will still get intercepted and caught in the normal
3022 	/* For sev guests, the memory encryption bit is not reserved in CR3.  */
3127 	 * A: VMRUN:   Host state saved in host save area
3130 	 * B: VMRUN:   Host state _NOT_ saved in host save area
3133 	 * C: VMRUN:   Host state _NOT_ saved in host save area