From: Binbin Wu <binbin.wu@linux.intel.com>
To: "Huang, Kai" <kai.huang@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"seanjc@google.com" <seanjc@google.com>
Cc: "Gao, Chao" <chao.gao@intel.com>,
"Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
"mikko.ylinen@linux.intel.com" <mikko.ylinen@linux.intel.com>,
"Li, Xiaoyao" <xiaoyao.li@intel.com>,
"Lindgren, Tony" <tony.lindgren@intel.com>,
"Hunter, Adrian" <adrian.hunter@intel.com>,
"Chatre, Reinette" <reinette.chatre@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Zhao, Yan Y" <yan.y.zhao@intel.com>,
"Yamahata, Isaku" <isaku.yamahata@intel.com>
Subject: Re: [PATCH 1/2] KVM: TDX: Handle TDG.VP.VMCALL<GetQuote>
Date: Wed, 2 Apr 2025 21:16:37 +0800 [thread overview]
Message-ID: <c96f2ed1-1c7f-4b61-85ff-902e08c61fbc@linux.intel.com> (raw)
In-Reply-To: <112c4cdb-4757-4625-ad18-9402340cd47e@linux.intel.com>
On 4/2/2025 8:53 PM, Binbin Wu wrote:
[...]
>>> diff --git a/arch/x86/kvm/vmx/tdx.c b/arch/x86/kvm/vmx/tdx.c
>>> index b952bc673271..535200446c21 100644
>>> --- a/arch/x86/kvm/vmx/tdx.c
>>> +++ b/arch/x86/kvm/vmx/tdx.c
>>> @@ -1463,6 +1463,39 @@ static int tdx_get_td_vm_call_info(struct kvm_vcpu *vcpu)
>>> return 1;
>>> }
>>> +static int tdx_complete_get_quote(struct kvm_vcpu *vcpu)
>>> +{
>>> + tdvmcall_set_return_code(vcpu, vcpu->run->tdx_get_quote.ret);
>>> + return 1;
>>> +}
>>> +
>>> +static int tdx_get_quote(struct kvm_vcpu *vcpu)
>>> +{
>>> + struct vcpu_tdx *tdx = to_tdx(vcpu);
>>> +
>>> + u64 gpa = tdx->vp_enter_args.r12;
>>> + u64 size = tdx->vp_enter_args.r13;
>>> +
>>> + /* The buffer must be shared memory. */
>>> + if (vt_is_tdx_private_gpa(vcpu->kvm, gpa) || size == 0) {
>>> + tdvmcall_set_return_code(vcpu, TDVMCALL_STATUS_INVALID_OPERAND);
>>> + return 1;
>>> + }
>> It is a little bit confusing about the shared buffer check here. There are two
>> perspectives here:
>>
>> 1) the buffer has already been converted to shared, i.e., the attributes are
>> stored in the Xarray.
>> 2) the GPA passed in the GetQuote must have the shared bit set.
>>
>> The key is we need 1) here. From the spec, we need the 2) as well because it
>> *seems* that the spec requires GetQuote to provide the GPA with shared bit set,
>> as it says "Shared GPA as input".
>>
>> The above check only does 2). I think we need to check 1) as well, because once
>> you forward this GetQuote to userspace, userspace is able to access it freely.
>
> Right.
>
> Another discussion is whether KVM should skip the sanity checks for GetQuote
> and let the userspace take the job.
> Considering checking the buffer is shared memory or not, KVM seems to be a
> better place.
A second thought. If the userspace could do the shared memory check, the
whole sanity checks can be done in userspace to keep KVM as small as possible.
>
>>
>> As a result, the comment
>>
>> /* The buffer must be shared memory. */
>>
>> should also be updated to something like:
>>
>> /*
>> * The buffer must be shared. GetQuote requires the GPA to have
>> * shared bit set.
>> */
>
>
next prev parent reply other threads:[~2025-04-02 13:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 0:15 [PATCH 0/2] TDX attestation support Binbin Wu
2025-04-02 0:15 ` [PATCH 1/2] KVM: TDX: Handle TDG.VP.VMCALL<GetQuote> Binbin Wu
2025-04-02 0:53 ` Huang, Kai
2025-04-02 8:58 ` Huang, Kai
2025-04-02 12:53 ` Binbin Wu
2025-04-02 13:16 ` Binbin Wu [this message]
2025-04-02 22:05 ` Huang, Kai
2025-04-02 22:00 ` Huang, Kai
2025-04-08 2:35 ` Binbin Wu
2025-04-09 13:49 ` Sean Christopherson
2025-04-10 0:06 ` Binbin Wu
2025-04-10 0:15 ` Huang, Kai
2025-04-02 22:19 ` Huang, Kai
2025-04-07 1:00 ` Binbin Wu
2025-04-15 1:49 ` Xiaoyao Li
2025-04-15 1:51 ` Edgecombe, Rick P
2025-04-15 1:55 ` Binbin Wu
2025-04-02 0:15 ` [PATCH 2/2] KVM: TDX: Handle TDG.VP.VMCALL<SetupEventNotifyInterrupt> Binbin Wu
2025-04-02 0:20 ` [PATCH 0/2] TDX attestation support Edgecombe, Rick P
2025-04-11 1:42 ` Binbin Wu
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=c96f2ed1-1c7f-4b61-85ff-902e08c61fbc@linux.intel.com \
--to=binbin.wu@linux.intel.com \
--cc=adrian.hunter@intel.com \
--cc=chao.gao@intel.com \
--cc=isaku.yamahata@intel.com \
--cc=kai.huang@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=xiaoyao.li@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