Lines Matching refs:guest

10 The SEV API is a set of ioctls that are used by the guest or hypervisor
22 This section describes ioctls that is used for querying the SEV guest report
30       hypervisor or guest. The ioctl can be used inside the guest or the
40 The guest ioctl should be issued on a file descriptor of the /dev/sev-guest
47 the guests message sequence counter. If guest driver fails to increment message
91 :Type: guest ioctl
106 :Type: guest ioctl
111 The derived key can be used by the guest for any purpose, such as sealing keys
125 :Type: guest ioctl
186 When requesting an attestation report a guest is able to specify whether
216    expected contents of a CPUID page as part of guest initialization will be
218    during SNP_LAUNCH_UPDATE, and noticeable later if the guest owner
223 Otherwise, guest owner attestation provides no assurance that the kernel wasn't
229 Communication between an SEV guest and the SEV firmware in the AMD Secure
231 (VMPCK). By default, the sev-guest driver uses the VMPCK associated with the
232 VM Privilege Level (VMPL) at which the guest is running. Should this key be
233 wiped by the sev-guest driver (see the driver for reasons why a VMPCK can be
234 wiped), a different key can be used by reloading the sev-guest driver and