From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel@nongnu.org, xiaoyao.li@intel.com
Subject: [PATCH 0/4] TDX: Update the handling of <GetTdVmCallInfo> and implement <SetupEventNotifyInterrupt>
Date: Thu, 3 Jul 2025 10:40:16 +0800 [thread overview]
Message-ID: <20250703024021.3559286-1-xiaoyao.li@intel.com> (raw)
It ends up as <GetQuote> is one of the base TDG.VP.VMCALL leaf, and it's
not enumerated via bit 0 of out R11 (the bit 0 becomes reserved).[1]
So patch 1 updates the handling of tdx_handle_get_tdvmcall_info().
[1] https://cdrdv2.intel.com/v1/dl/getContent/858626
Paolo,
Patch 2-4, enables <SetupEventNotifyInterrupt> in QEMU. They based on
the KVM patches you put in KVM tree master.
Xiaoyao Li (4):
i386/tdx: Remove enumeration of GetQuote in
tdx_handle_get_tdvmcall_info()
update Linux headers to KVM tree master
i386/tdx: Set value of <GetTdVmCallInfo> based on capabilities of both
KVM and QEMU
i386/tdx: handle TDVMCALL_SETUP_EVENT_NOTIFY_INTERRUPT
linux-headers/asm-x86/kvm.h | 8 ++++-
linux-headers/linux/kvm.h | 4 +++
target/i386/kvm/kvm.c | 3 ++
target/i386/kvm/tdx-stub.c | 4 +++
target/i386/kvm/tdx.c | 61 +++++++++++++++++++++++++++++++++++--
target/i386/kvm/tdx.h | 7 ++++-
6 files changed, 82 insertions(+), 5 deletions(-)
--
2.43.0
next reply other threads:[~2025-07-03 2:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 2:40 Xiaoyao Li [this message]
2025-07-03 2:40 ` [PATCH 1/4] i386/tdx: Remove enumeration of GetQuote in tdx_handle_get_tdvmcall_info() Xiaoyao Li
2025-07-03 2:40 ` [PATCH 2/4] update Linux headers to KVM tree master Xiaoyao Li
2025-07-03 2:40 ` [PATCH 3/4] i386/tdx: Set value of <GetTdVmCallInfo> based on capabilities of both KVM and QEMU Xiaoyao Li
2025-07-03 2:40 ` [PATCH 4/4] i386/tdx: handle TDVMCALL_SETUP_EVENT_NOTIFY_INTERRUPT Xiaoyao Li
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=20250703024021.3559286-1-xiaoyao.li@intel.com \
--to=xiaoyao.li@intel.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).