Searched refs:sev_fd (Results 1 – 5 of 5) sorted by relevance
| /linux/arch/x86/kvm/svm/ |
| H A D | sev.c | 639 ret = __sev_issue_cmd(argp->sev_fd, SEV_CMD_LAUNCH_START, &start, error); in sev_launch_start()
660 sev->fd = argp->sev_fd; in sev_launch_start()
1779 ret = __sev_issue_cmd(argp->sev_fd, SEV_CMD_RECEIVE_START, &start, in sev_receive_start()
1800 sev->fd = argp->sev_fd; in sev_receive_start()
2177 rc = __sev_issue_cmd(argp->sev_fd, SEV_CMD_SNP_GCTX_CREATE, &data, &argp->error); in snp_context_create()
2240 rc = __sev_issue_cmd(argp->sev_fd, SEV_CMD_SNP_LAUNCH_START, &start, &argp->error); in snp_launch_start()
2248 sev->fd = argp->sev_fd; in snp_launch_start()
2266 int sev_fd; member
2317 ret = __sev_issue_cmd(sev_populate_args->sev_fd, SEV_CMD_SNP_LAUNCH_UPDATE, in sev_gmem_post_populate()
2418 sev_populate_args.sev_fd = argp->sev_fd; in snp_launch_update()
[all …]
|
| /linux/Documentation/virt/kvm/x86/ |
| H A D | amd-memory-encryption.rst | 64 __u32 sev_fd;
69 another struct containing arguments specific to command. The ``sev_fd``
155 KVM_SEV_LAUNCH_START requires the ``sev_fd`` field to be valid.
|
| /linux/arch/x86/include/uapi/asm/ |
| H A D | kvm.h | 755 __u32 sev_fd; member
|
| /linux/tools/arch/x86/include/uapi/asm/ |
| H A D | kvm.h | 755 __u32 sev_fd; member
|
| /linux/tools/testing/selftests/kvm/lib/x86/ |
| H A D | processor.c | 1195 vm->arch.sev_fd = open_sev_dev_path_or_exit(); in kvm_init_vm_address_properties()
1199 vm->arch.sev_fd = -1; in kvm_init_vm_address_properties()
|