From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Kai Huang <kai.huang@intel.com>,
Rick Edgecombe <rick.p.edgecombe@intel.com>
Subject: Re: [PATCH] KVM: VMX: Inject #UD if guest tries to execute SEAMCALL or TDCALL
Date: Wed, 15 Oct 2025 22:45:21 +0800 [thread overview]
Message-ID: <456146b7-e4f3-46d4-8b30-8b0ccb250f08@intel.com> (raw)
In-Reply-To: <aO-oTw_l9mU1blRo@google.com>
On 10/15/2025 9:57 PM, Sean Christopherson wrote:
> On Wed, Oct 15, 2025, Xiaoyao Li wrote:
>> On 10/15/2025 7:10 AM, Sean Christopherson wrote:
>>> diff --git a/arch/x86/kvm/vmx/nested.c b/arch/x86/kvm/vmx/nested.c
>>> index 76271962cb70..f64a1eb241b6 100644
>>> --- a/arch/x86/kvm/vmx/nested.c
>>> +++ b/arch/x86/kvm/vmx/nested.c
>>> @@ -6728,6 +6728,14 @@ static bool nested_vmx_l1_wants_exit(struct kvm_vcpu *vcpu,
>>> case EXIT_REASON_NOTIFY:
>>> /* Notify VM exit is not exposed to L1 */
>>> return false;
>>> + case EXIT_REASON_SEAMCALL:
>>> + case EXIT_REASON_TDCALL:
>>> + /*
>>> + * SEAMCALL and TDCALL unconditionally VM-Exit, but aren't
>>> + * virtualized by KVM for L1 hypervisors, i.e. L1 should
>>> + * never want or expect such an exit.
>>> + */
>>
>> The i.e. part is confusing? It is exactly forwarding the EXITs to L1, while
>> it says L1 should never want or expect such an exit.
>
> Gah, the comment is right, the code is wrong.
So the intent was to return false here? to let L0 handle the exit?
Then I have a question, why not implement it in
nested_vmx_l0_wants_exit()? what's the reason and rule here?
> /facepalm
>
> I even tried to explicitly test this, but I put the TDCALL and SEAMCALL in L1
> instead of L2.
>
> diff --git a/tools/testing/selftests/kvm/x86/vmx_invalid_nested_guest_state.c b/tools/testing/selftests/kvm/x86/vmx_invalid_nested_guest_state.c
> index a100ee5f0009..1d7ef7d2d381 100644
> --- a/tools/testing/selftests/kvm/x86/vmx_invalid_nested_guest_state.c
> +++ b/tools/testing/selftests/kvm/x86/vmx_invalid_nested_guest_state.c
> @@ -23,11 +23,17 @@ static void l2_guest_code(void)
> : : [port] "d" (ARBITRARY_IO_PORT) : "rax");
> }
>
> +#define tdcall ".byte 0x66,0x0f,0x01,0xcc"
> +#define seamcall ".byte 0x66,0x0f,0x01,0xcf"
> +
> static void l1_guest_code(struct vmx_pages *vmx_pages)
> {
> #define L2_GUEST_STACK_SIZE 64
> unsigned long l2_guest_stack[L2_GUEST_STACK_SIZE];
>
> + TEST_ASSERT_EQ(kvm_asm_safe(tdcall), UD_VECTOR);
> + TEST_ASSERT_EQ(kvm_asm_safe(seamcall), UD_VECTOR);
> +
> GUEST_ASSERT(prepare_for_vmx_operation(vmx_pages));
> GUEST_ASSERT(load_vmcs(vmx_pages));
>
next prev parent reply other threads:[~2025-10-15 14:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 23:10 [PATCH] KVM: VMX: Inject #UD if guest tries to execute SEAMCALL or TDCALL Sean Christopherson
2025-10-15 0:22 ` dan.j.williams
2025-10-15 13:56 ` Sean Christopherson
2025-10-15 15:49 ` dan.j.williams
2025-10-15 1:13 ` Chao Gao
2025-10-15 3:11 ` Xiaoyao Li
2025-10-15 13:20 ` Sean Christopherson
2025-10-15 10:36 ` Xiaoyao Li
2025-10-15 13:57 ` Sean Christopherson
2025-10-15 14:45 ` Xiaoyao Li [this message]
2025-10-16 18:28 ` Sean Christopherson
2025-10-15 13:38 ` 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=456146b7-e4f3-46d4-8b30-8b0ccb250f08@intel.com \
--to=xiaoyao.li@intel.com \
--cc=kai.huang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox