From: Xiaoyao Li <xiaoyao.li@intel.com>
To: sashiko-reviews@lists.linux.dev, Lisa Wang <wyihan@google.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH v15 20/23] KVM: selftests: Add a helper to issue TDVMCALLs from the TDX vm
Date: Fri, 9 Oct 2026 16:20:51 +0800 [thread overview]
Message-ID: <abc8e273-90ce-4357-b16d-9d0af88dc654@intel.com> (raw)
In-Reply-To: <20261002091334.3553E1F00893@smtp.kernel.org>
On 10/2/2026 5:13 PM, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] kvm: selftests: __tdvmcall silently masks TDCALL hardware failures
> --
>
> commit 7709c4e900a0fe6433017aebbf708ee2946d3f19
> Author: Erdem Aktas <erdemaktas@google.com>
>
> KVM: selftests: Add a helper to issue TDVMCALLs from the TDX vm
>
> This commit introduces a helper function __tdvmcall() to allow TDX VMs
> to issue TDG.VP.VMCALL with a single function call, abstracting the
> register setup. The function passes the GHCI sub-function and arguments,
> and returns the TDVMCALL status.
>
>> diff --git a/tools/testing/selftests/kvm/lib/x86/tdx/tdx.S b/tools/testing/selftests/kvm/lib/x86/tdx/tdx.S
>> new file mode 100644
>> index 0000000000000..e3f0f7f2232bf
>> --- /dev/null
>> +++ b/tools/testing/selftests/kvm/lib/x86/tdx/tdx.S
>> @@ -0,0 +1,39 @@
> [ ... ]
>> + mov $0, %rax /* TDCALL leaf 0: TDG.VP.VMCALL */
>> + mov $0xFC00, %rcx /* Expose R10-R15 */
>> + mov $0, %r10 /* Standard GHCI call */
>> +
>> + /* TDCALL instruction */
>> + .byte 0x66, 0x0f, 0x01, 0xcc
>> +
>> + /* Extract status */
>> + mov %r10, %rax
>
> [Severity: Medium]
> Does this code inadvertently discard the TDCALL hardware failure status?
>
> The TDCALL instruction returns its module-level execution status in %rax.
> If TDCALL fails (e.g., due to invalid arguments or incorrect VM state), %rax
> contains a non-zero error code and output registers like %r10 are left
> unmodified (which was initialized to 0 prior to the call).
>
> By unconditionally overwriting %rax with %r10, any TDCALL failure status
> appears to be silently masked and converted into a false success. Should
> this code check or preserve the error code in %rax before overwriting it?
This is a wrong comment from Sashiko. RAX returned from TDG.VP.VMCALL is always 0.
>> +
>> + pop %r15
>> + pop %r14
>> + pop %r13
>> + pop %r12
>> + ret
>
next prev parent reply other threads:[~2026-10-09 8:20 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 19:37 [PATCH v15 00/23] TDX KVM selftests Lisa Wang
2026-10-01 19:37 ` [PATCH v15 01/23] KVM: selftests: Add macros to simplify creating VM shapes for non-default types Lisa Wang
2026-10-01 19:37 ` [PATCH v15 02/23] KVM: selftests: Update kvm_init_vm_address_properties() for TDX Lisa Wang
2026-10-01 19:37 ` [PATCH v15 03/23] KVM: selftests: Initialize the TDX VM Lisa Wang
2026-10-02 9:13 ` sashiko-bot
2026-10-05 21:26 ` Lisa Wang
2026-10-09 6:00 ` Xiaoyao Li
2026-10-10 2:05 ` Binbin Wu
2026-10-01 19:37 ` [PATCH v15 04/23] KVM: selftests: Expose segment definitions to assembly files Lisa Wang
2026-10-01 19:37 ` [PATCH v15 05/23] tools: include: Add kbuild.h for assembly structure offsets Lisa Wang
2026-10-09 6:10 ` Xiaoyao Li
2026-10-01 19:37 ` [PATCH v15 06/23] KVM: selftests: Introduce structures for TDX guest boot parameters Lisa Wang
2026-10-09 6:13 ` Xiaoyao Li
2026-10-01 19:37 ` [PATCH v15 07/23] KVM: selftests: Add TDX boot code Lisa Wang
2026-10-02 9:13 ` sashiko-bot
2026-10-05 22:31 ` Lisa Wang
2026-10-01 19:37 ` [PATCH v15 08/23] KVM: selftests: Expose functions to get default sregs values Lisa Wang
2026-10-01 19:37 ` [PATCH v15 09/23] KVM: selftests: Set up TDX boot code region Lisa Wang
2026-10-01 19:37 ` [PATCH v15 10/23] KVM: selftests: Set up TDX boot parameters region Lisa Wang
2026-10-02 9:13 ` sashiko-bot
2026-10-05 22:33 ` Lisa Wang
2026-10-09 7:22 ` Xiaoyao Li
2026-10-10 2:46 ` Binbin Wu
2026-10-01 19:37 ` [PATCH v15 11/23] KVM: selftests: Set shared attributes for ucall guest_memfd pages Lisa Wang
2026-10-09 15:44 ` Xiaoyao Li
2026-10-01 19:37 ` [PATCH v15 12/23] KVM: selftests: Require guest_memfd for TDX VMs Lisa Wang
2026-10-09 7:38 ` Xiaoyao Li
2026-10-01 19:37 ` [PATCH v15 13/23] KVM: selftests: Support guest_memfd in-place conversion Lisa Wang
2026-10-10 3:32 ` Binbin Wu
2026-10-01 19:37 ` [PATCH v15 14/23] KVM: selftests: Expose function to allocate vCPU stack Lisa Wang
2026-10-02 9:13 ` sashiko-bot
2026-10-09 7:56 ` Xiaoyao Li
2026-10-10 3:54 ` Binbin Wu
2026-10-01 19:37 ` [PATCH v15 15/23] KVM: selftests: Call KVM_TDX_INIT_VCPU when creating a new TDX vcpu Lisa Wang
2026-10-09 8:02 ` Xiaoyao Li
2026-10-10 4:31 ` Binbin Wu
2026-10-01 19:37 ` [PATCH v15 16/23] KVM: selftests: Load per-vCPU guest stack in TDX boot parameters Lisa Wang
2026-10-02 9:13 ` sashiko-bot
2026-10-07 19:07 ` Lisa Wang
2026-10-01 19:37 ` [PATCH v15 17/23] KVM: selftests: Set entry point for TDX guest code Lisa Wang
2026-10-02 9:13 ` sashiko-bot
2026-10-01 19:37 ` [PATCH v15 18/23] KVM: selftests: Add helpers to init TDX memory and finalize VM Lisa Wang
2026-10-01 19:37 ` [PATCH v15 19/23] KVM: selftests: Finalize TDX VM in kvm_arch_vm_finalize_vcpus() Lisa Wang
2026-10-09 8:12 ` Xiaoyao Li
2026-10-10 5:57 ` Binbin Wu
2026-10-01 19:37 ` [PATCH v15 20/23] KVM: selftests: Add a helper to issue TDVMCALLs from the TDX vm Lisa Wang
2026-10-02 9:13 ` sashiko-bot
2026-10-09 8:20 ` Xiaoyao Li [this message]
2026-10-09 8:23 ` Xiaoyao Li
2026-10-10 6:34 ` Binbin Wu
2026-10-01 19:37 ` [PATCH v15 21/23] KVM: selftests: Add support for per-VM ucall ops on x86 Lisa Wang
2026-10-02 9:13 ` sashiko-bot
2026-10-10 6:52 ` Binbin Wu
2026-10-01 19:37 ` [PATCH v15 22/23] KVM: selftests: Add support for TDX ucalls, via TDVMCALL_REPORT_FATAL_ERROR Lisa Wang
2026-10-02 9:13 ` sashiko-bot
2026-10-10 7:30 ` Binbin Wu
2026-10-10 7:20 ` Binbin Wu
2026-10-01 19:37 ` [PATCH v15 23/23] KVM: selftests: Add TDX lifecycle test Lisa Wang
2026-10-10 7:40 ` 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=abc8e273-90ce-4357-b16d-9d0af88dc654@intel.com \
--to=xiaoyao.li@intel.com \
--cc=kvm@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wyihan@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.