From: Sriram Nambakam <snambakam@linux.microsoft.com>
To: kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [RFC PATCH v2 3/4] KVM: x86: add VTL-call state to struct kvm_vcpu_common
Date: Mon, 10 Aug 2026 17:31:13 -0700 [thread overview]
Message-ID: <20260811003114.30107-4-snambakam@linux.microsoft.com> (raw)
In-Reply-To: <20260811003114.30107-1-snambakam@linux.microsoft.com>
Add the shared state used by the in-kernel VBS VTL call/return handlers:
vtl_call_ca - guest-physical address of the shared calling area
vtl_call_pending - a call arrived while the secure plane was booting
vtl_plane_ready - the secure plane has parked in its VTL return
The fields live in struct kvm_vcpu_common so they are shared across a
logical CPU's plane vCPUs.
---
include/linux/kvm_host.h | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
index a61524ab0d94..61bb59c50ae6 100644
--- a/include/linux/kvm_host.h
+++ b/include/linux/kvm_host.h
@@ -386,6 +386,11 @@ struct kvm_vcpu_common {
bool plane_switch;
+ /* VBS VTL-call state, shared across this CPU's plane vCPUs. */
+ gpa_t vtl_call_ca;
+ bool vtl_call_pending;
+ bool vtl_plane_ready;
+
struct kvm_vcpu_arch_common arch;
};
--
2.55.0
next prev parent reply other threads:[~2026-08-11 0:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 0:31 [RFC PATCH v2 0/4] KVM: VM Planes host support for VBS Sriram Nambakam
2026-08-11 0:31 ` [RFC PATCH v2 1/4] kvm: uapi: reserve VM-plane and VBS hypercall numbers Sriram Nambakam
2026-08-11 0:31 ` [RFC PATCH v2 2/4] KVM: x86: exit VM-plane config/activate hypercalls to userspace Sriram Nambakam
2026-08-11 0:31 ` Sriram Nambakam [this message]
2026-08-11 0:31 ` [RFC PATCH v2 4/4] KVM: x86: handle VBS VTL call/return via in-kernel plane switch Sriram Nambakam
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=20260811003114.30107-4-snambakam@linux.microsoft.com \
--to=snambakam@linux.microsoft.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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