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: Mon, 7 Apr 2025 09:00:28 +0800 [thread overview]
Message-ID: <84d44db2-6327-43db-93c9-61823f4d90aa@linux.intel.com> (raw)
In-Reply-To: <2047f2964fa713f70823b9293bf1ffd65ac44fa8.camel@intel.com>
On 4/3/2025 6:19 AM, Huang, Kai wrote:
> On Wed, 2025-04-02 at 08:15 +0800, Binbin Wu wrote:
>> +::
>> +
>> + /* KVM_EXIT_TDX_GET_QUOTE */
>> + struct tdx_get_quote {
>> + __u64 ret;
>> + __u64 gpa;
>> + __u64 size;
>> + };
>> +
> The shared buffer pointed by the @gpa also has a format defined in the GHCI
> spec. E.g., it has a 'status code' field. Does userspace VMM need to setup
> this 'status code' as well?
Yes.
>
> I recall that we used to set the GET_QUOTE_IN_FLIGHT flag in Qemu but not sure
> whether it is still true?
It's still true.
>
> I am thinking if Qemu needs to set it, then we need to expose the structure of
> the shared buffer to userspace too.
For the structure of the shared buffer, since KVM doesn't care about it.
IMHO, it's not necessary to define the structure in KVM and userspace can
define the structure according to GHCI directly.
next prev parent reply other threads:[~2025-04-07 1:00 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
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 [this message]
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=84d44db2-6327-43db-93c9-61823f4d90aa@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;
as well as URLs for NNTP newsgroup(s).