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 v2 0/3] TDX attestation support and GHCI fixup
Date: Fri, 20 Jun 2025 09:30:30 +0800 [thread overview]
Message-ID: <3133d5e9-18d3-499a-a24d-170be7fb8357@intel.com> (raw)
In-Reply-To: <20250619180159.187358-1-pbonzini@redhat.com>
On 6/20/2025 2:01 AM, Paolo Bonzini wrote:
> This is a refresh of Binbin's patches with a change to the userspace
> API. I am consolidating everything into a single KVM_EXIT_TDX and
> adding to the contract that userspace is free to ignore it *except*
> for having to reenter the guest with KVM_RUN.
>
> If in the future this does not work, it should be possible to introduce
> an opt-in interface. Hopefully that will not be necessary.
For <GetTdVmCallInfo> exit, I think KVM still needs to report which
TDVMCALL leaf will exit to userspace, to differentiate between different
KVMs.
But it's not a must for current <GetQuote> since it exits to userspace
from day 0. So that we can leave the report interface until KVM needs to
support user exit of another TDVMCALL leaf.
> Paolo
>
> Binbin Wu (3):
> KVM: TDX: Add new TDVMCALL status code for unsupported subfuncs
> KVM: TDX: Handle TDG.VP.VMCALL<GetQuote>
> KVM: TDX: Exit to userspace for GetTdVmCallInfo
>
> Documentation/virt/kvm/api.rst | 62 ++++++++++++++++++++++++-
> arch/x86/include/asm/shared/tdx.h | 1 +
> arch/x86/kvm/vmx/tdx.c | 77 ++++++++++++++++++++++++++++---
> include/uapi/linux/kvm.h | 22 +++++++++
> 4 files changed, 154 insertions(+), 8 deletions(-)
>
next prev parent reply other threads:[~2025-06-20 1:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 18:01 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
2025-06-20 12:03 ` Paolo Bonzini
2025-06-20 12:34 ` Xiaoyao Li
2025-06-20 1:30 ` Xiaoyao Li [this message]
2025-06-20 2:10 ` [PATCH v2 0/3] TDX attestation support and GHCI fixup 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
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=3133d5e9-18d3-499a-a24d-170be7fb8357@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®