From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
seanjc@google.com
Cc: rick.p.edgecombe@intel.com, kai.huang@intel.com,
adrian.hunter@intel.com, reinette.chatre@intel.com,
tony.lindgren@intel.com, isaku.yamahata@intel.com,
yan.y.zhao@intel.com, mikko.ylinen@linux.intel.com,
kirill.shutemov@intel.com, jiewen.yao@intel.com,
binbin.wu@linux.intel.com
Subject: Re: [PATCH 3/3] KVM: TDX: Exit to userspace for GetTdVmCallInfo
Date: Fri, 20 Jun 2025 09:20:55 +0800 [thread overview]
Message-ID: <cc443335-442d-4ed0-aa01-a6bf5c27b39c@intel.com> (raw)
In-Reply-To: <20250619180159.187358-4-pbonzini@redhat.com>
On 6/20/2025 2:01 AM, Paolo Bonzini wrote:
> From: Binbin Wu <binbin.wu@linux.intel.com>
>
> Exit to userspace for TDG.VP.VMCALL<GetTdVmCallInfo> via KVM_EXIT_TDX,
> to allow userspace to provide information about the support of
> TDVMCALLs when r12 is 1 for the TDVMCALLs beyond the GHCI base API.
>
> GHCI spec defines the GHCI base TDVMCALLs: <GetTdVmCallInfo>, <MapGPA>,
> <ReportFatalError>, <Instruction.CPUID>, <#VE.RequestMMIO>,
> <Instruction.HLT>, <Instruction.IO>, <Instruction.RDMSR> and
> <Instruction.WRMSR>. They must be supported by VMM to support TDX guests.
>
> For GetTdVmCallInfo
> - When leaf (r12) to enumerate TDVMCALL functionality is set to 0,
> successful execution indicates all GHCI base TDVMCALLs listed above are
> supported.
>
> Update the KVM TDX document with the set of the GHCI base APIs.
>
> - When leaf (r12) to enumerate TDVMCALL functionality is set to 1, it
> indicates the TDX guest is querying the supported TDVMCALLs beyond
> the GHCI base TDVMCALLs.
> Exit to userspace to let userspace set the TDVMCALL sub-function bit(s)
> accordingly to the leaf outputs. KVM could set the TDVMCALL bit(s)
> supported by itself when the TDVMCALLs don't need support from userspace
> after returning from userspace and before entering guest. Currently, no
> such TDVMCALLs implemented, KVM just sets the values returned from
> userspace.
>
> Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
> Signed-off-by: Binbin Wu <binbin.wu@linux.intel.com>
> [Adjust userspace API. - Paolo]
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> Documentation/virt/kvm/api.rst | 15 +++++++++++++-
> arch/x86/kvm/vmx/tdx.c | 38 ++++++++++++++++++++++++++++++----
> include/uapi/linux/kvm.h | 5 +++++
> 3 files changed, 53 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
> index 3643d853a634..2b1656907356 100644
> --- a/Documentation/virt/kvm/api.rst
> +++ b/Documentation/virt/kvm/api.rst
> @@ -7190,6 +7190,11 @@ The valid value for 'flags' is:
> u64 gpa;
> u64 size;
> } get_quote;
> + struct {
> + u64 ret;
> + u64 leaf;
> + u64 r11, r12, r13, r14;
> + } get_tdvmcall_info;
> };
> } tdx;
>
> @@ -7216,9 +7221,17 @@ queued successfully, the TDX guest can poll the status field in the
> shared-memory area to check whether the Quote generation is completed or
> not. When completed, the generated Quote is returned via the same buffer.
>
> +* ``TDVMCALL_GET_TD_VM_CALL_INFO``: the guest has requested the support
> +status of TDVMCALLs. The output values for the given leaf should be
> +placed in fields from ``r11`` to ``r14`` of the ``get_tdvmcall_info``
> +field of the union. This TDVMCALL must succeed, therefore KVM leaves
> +``ret`` equal to ``TDVMCALL_STATUS_SUCCESS`` and ``r11`` to ``r14``
> +equal to zero on entry.
> +
> KVM may add support for more values in the future that may cause a userspace
> exit, even without calls to ``KVM_ENABLE_CAP`` or similar. In this case,
> -it will enter with output fields already valid; in the common case, the
> +it will enter with output fields already valid as mentioned for
> +``TDVMCALL_GET_TD_VM_CALL_INFO`` above; in the common case, the
> ``unknown.ret`` field of the union will be ``TDVMCALL_STATUS_SUBFUNC_UNSUPPORTED``.
> Userspace need not do anything if it does not wish to support a TDVMCALL.
> ::
> diff --git a/arch/x86/kvm/vmx/tdx.c b/arch/x86/kvm/vmx/tdx.c
> index 6878a76069f8..5804d1b1ea0e 100644
> --- a/arch/x86/kvm/vmx/tdx.c
> +++ b/arch/x86/kvm/vmx/tdx.c
> @@ -1451,18 +1451,49 @@ static int tdx_emulate_mmio(struct kvm_vcpu *vcpu)
> return 1;
> }
>
> +static int tdx_complete_get_td_vm_call_info(struct kvm_vcpu *vcpu)
> +{
> + struct vcpu_tdx *tdx = to_tdx(vcpu);
> +
> + tdvmcall_set_return_code(vcpu, vcpu->run->tdx.get_tdvmcall_info.ret);
> +
> + /*
> + * For now, there is no TDVMCALL beyond GHCI base API supported by KVM
> + * directly without the support from userspace, just set the value
> + * returned from userspace.
> + */
> + tdx->vp_enter_args.r11 = vcpu->run->tdx.get_tdvmcall_info.r11;
> + tdx->vp_enter_args.r12 = vcpu->run->tdx.get_tdvmcall_info.r12;
> + tdx->vp_enter_args.r13 = vcpu->run->tdx.get_tdvmcall_info.r13;
> + tdx->vp_enter_args.r14 = vcpu->run->tdx.get_tdvmcall_info.r14;
> +
> + return 1;
> +}
> +
> static int tdx_get_td_vm_call_info(struct kvm_vcpu *vcpu)
> {
> struct vcpu_tdx *tdx = to_tdx(vcpu);
>
> - if (tdx->vp_enter_args.r12)
> - tdvmcall_set_return_code(vcpu, TDVMCALL_STATUS_INVALID_OPERAND);
> - else {
> + switch (tdx->vp_enter_args.r12) {
> + case 1:
> + vcpu->run->tdx.get_tdvmcall_info.leaf = tdx->vp_enter_args.r12;
> + vcpu->run->exit_reason = KVM_EXIT_TDX;
> + vcpu->run->tdx.flags = 0;
> + vcpu->run->tdx.nr = TDVMCALL_GET_TD_VM_CALL_INFO;
> + vcpu->run->tdx.get_tdvmcall_info.ret = TDVMCALL_STATUS_SUCCESS;
> + vcpu->run->tdx.get_tdvmcall_info.r11 = 0;
> + vcpu->run->tdx.get_tdvmcall_info.r12 = 0;
> + vcpu->run->tdx.get_tdvmcall_info.r13 = 0;
> + vcpu->run->tdx.get_tdvmcall_info.r14 = 0;
> + vcpu->arch.complete_userspace_io = tdx_complete_get_td_vm_call_info;
> + return 0;
> + default:
> tdx->vp_enter_args.r11 = 0;
> + tdx->vp_enter_args.r12 = 0;
> tdx->vp_enter_args.r13 = 0;
> tdx->vp_enter_args.r14 = 0;
> + return 1;
Though it looks OK to return all-0 for r12 == 0 and undefined case of
r12 > 1, I prefer returning TDVMCALL_STATUS_INVALID_OPERAND for
undefined case.
So please make above "case 0:", and make the "default:" return
TDVMCALL_STATUS_INVALID_OPERAND
> }
> - return 1;
> }
>
> static int tdx_complete_simple(struct kvm_vcpu *vcpu)
> diff --git a/include/uapi/linux/kvm.h b/include/uapi/linux/kvm.h
> index 6708bc88ae69..fb3b4cd8d662 100644
> --- a/include/uapi/linux/kvm.h
> +++ b/include/uapi/linux/kvm.h
> @@ -461,6 +461,11 @@ struct kvm_run {
> __u64 gpa;
> __u64 size;
> } get_quote;
> + struct {
> + __u64 ret;
> + __u64 leaf;
> + __u64 r11, r12, r13, r14;
> + } get_tdvmcall_info;
> };
> } tdx;
> /* Fix the size of the union. */
next prev parent reply other threads:[~2025-06-20 1:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 18:01 [PATCH v2 0/3] TDX attestation support and GHCI fixup Paolo Bonzini
2025-06-19 18:01 ` [PATCH 1/3] KVM: TDX: Add new TDVMCALL status code for unsupported subfuncs Paolo Bonzini
2025-06-23 22:42 ` Huang, Kai
2025-06-19 18:01 ` [PATCH 2/3] KVM: TDX: Handle TDG.VP.VMCALL<GetQuote> Paolo Bonzini
2025-06-20 2:57 ` Binbin Wu
2025-06-20 3:05 ` Binbin Wu
2025-06-19 18:01 ` [PATCH 3/3] KVM: TDX: Exit to userspace for GetTdVmCallInfo Paolo Bonzini
2025-06-20 1:20 ` Xiaoyao Li [this message]
2025-06-20 12:03 ` Paolo Bonzini
2025-06-20 12:34 ` Xiaoyao Li
2025-06-20 1:30 ` [PATCH v2 0/3] TDX attestation support and GHCI fixup Xiaoyao Li
2025-06-20 2:10 ` Binbin Wu
2025-06-20 12:03 ` Paolo Bonzini
2025-06-20 12:48 ` Xiaoyao Li
2025-06-20 17:24 ` Paolo Bonzini
2025-06-20 17:47 ` Edgecombe, Rick P
2025-06-20 7:09 ` Binbin Wu
2025-06-20 18:33 [PATCH v3 " Paolo Bonzini
2025-06-20 18:33 ` [PATCH 3/3] KVM: TDX: Exit to userspace for GetTdVmCallInfo Paolo Bonzini
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=cc443335-442d-4ed0-aa01-a6bf5c27b39c@intel.com \
--to=xiaoyao.li@intel.com \
--cc=adrian.hunter@intel.com \
--cc=binbin.wu@linux.intel.com \
--cc=isaku.yamahata@intel.com \
--cc=jiewen.yao@intel.com \
--cc=kai.huang@intel.com \
--cc=kirill.shutemov@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikko.ylinen@linux.intel.com \
--cc=pbonzini@redhat.com \
--cc=reinette.chatre@intel.com \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=tony.lindgren@intel.com \
--cc=yan.y.zhao@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®