Lines Matching full:ioctl
15 whole SEV firmware. These ioctl are used by platform provisioning tools.
23 from the SEV firmware. For each ioctl, the following information is provided
27 which SEV technology provides this ioctl. SEV, SEV-ES, SEV-SNP or all.
30 hypervisor or guest. The ioctl can be used inside the guest or the
34 what parameters are accepted by the ioctl.
40 The guest ioctl should be issued on a file descriptor of the /dev/sev-guest
41 device. The ioctl accepts struct snp_user_guest_request. The input and
43 respectively. If the ioctl fails to execute due to a firmware error, then
71 The ioctl accepts the command ID/input structure documented below.
91 :Type: guest ioctl
95 The SNP_GET_REPORT ioctl can be used to query the attestation report from the
96 SEV-SNP firmware. The ioctl uses the SNP_GUEST_REQUEST (MSG_REPORT_REQ) command
106 :Type: guest ioctl
110 The SNP_GET_DERIVED_KEY ioctl can be used to get a key derive from a root key.
114 The ioctl uses the SNP_GUEST_REQUEST (MSG_KEY_REQ) command provided by the
125 :Type: guest ioctl
129 The SNP_GET_EXT_REPORT ioctl is similar to the SNP_GET_REPORT. The difference is
134 The ioctl uses the SNP_GUEST_REQUEST (MSG_REPORT_REQ) command provided by the SEV-SNP
147 :Type: hypervisor ioctl cmd
158 :Type: hypervisor ioctl cmd
169 :Type: hypervisor ioctl cmd
182 :Type: hypervisor ioctl cmd