diff options
| author | Xiaoyao Li <[email protected]> | 2025-07-17 02:20:09 +0000 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2025-07-17 14:24:23 +0000 |
| commit | ed302854d0155e24a3620b92e7e9f591d510c252 (patch) | |
| tree | 86c2cc397b748052202bc85fd44eb787570a0c52 /net/core/dev_api.c | |
| parent | Merge tag 'kvm-riscv-fixes-6.16-2' of https://github.com/kvm-riscv/linux into... (diff) | |
| download | kernel-ed302854d0155e24a3620b92e7e9f591d510c252.tar.gz kernel-ed302854d0155e24a3620b92e7e9f591d510c252.zip | |
KVM: TDX: Don't report base TDVMCALLs
Remove TDVMCALLINFO_GET_QUOTE from user_tdvmcallinfo_1_r11 reported to
userspace to align with the direction of the GHCI spec.
Recently, concern was raised about a gap in the GHCI spec that left
ambiguity in how to expose to the guest that only a subset of GHCI
TDVMCalls were supported. During the back and forth on the spec details[0],
<GetQuote> was moved from an individually enumerable TDVMCall, to one that
is part of the 'base spec', meaning it doesn't have a specific bit in the
<GetTDVMCallInfo> return values. Although the spec[1] is still in draft
form, the GetQoute part has been agreed by the major TDX VMMs.
Unfortunately the commits that were upstreamed still treat <GetQuote> as
individually enumerable. They set bit 0 in the user_tdvmcallinfo_1_r11
which is reported to userspace to tell supported optional TDVMCalls,
intending to say that <GetQuote> is supported.
So stop reporting <GetQute> in user_tdvmcallinfo_1_r11 to align with
the direction of the spec, and allow some future TDVMCall to use that bit.
[0] https://lore.kernel.org/all/[email protected]/
[1] https://cdrdv2.intel.com/v1/dl/getContent/858626
Fixes: 28224ef02b56 ("KVM: TDX: Report supported optional TDVMCALLs in TDX capabilities")
Signed-off-by: Xiaoyao Li <[email protected]>
Message-ID: <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'net/core/dev_api.c')
0 files changed, 0 insertions, 0 deletions