[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48ab3a81-a353-e6ee-7718-69c260c9ea17@intel.com>
Date: Thu, 7 Apr 2022 19:09:36 +0800
From: Xiaoyao Li <xiaoyao.li@...el.com>
To: Paolo Bonzini <pbonzini@...hat.com>, isaku.yamahata@...el.com,
kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: isaku.yamahata@...il.com, Jim Mattson <jmattson@...gle.com>,
erdemaktas@...gle.com, Connor Kuehl <ckuehl@...hat.com>,
Sean Christopherson <seanjc@...gle.com>,
Tom Lendacky <thomas.lendacky@....com>
Subject: Re: [RFC PATCH v5 101/104] KVM: TDX: Silently ignore INIT/SIPI
On 4/5/2022 11:48 PM, Paolo Bonzini wrote:
> On 3/4/22 20:49, isaku.yamahata@...el.com wrote:
>> + if (kvm_init_sipi_unsupported(vcpu->kvm))
>> + /*
>> + * TDX doesn't support INIT. Ignore INIT event. In the
>> + * case of SIPI, the callback of
>> + * vcpu_deliver_sipi_vector ignores it.
>> + */
>> vcpu->arch.mp_state = KVM_MP_STATE_RUNNABLE;
>> - else
>> - vcpu->arch.mp_state = KVM_MP_STATE_INIT_RECEIVED;
>> + else {
>> + kvm_vcpu_reset(vcpu, true);
>> + if (kvm_vcpu_is_bsp(apic->vcpu))
>> + vcpu->arch.mp_state = KVM_MP_STATE_RUNNABLE;
>> + else
>> + vcpu->arch.mp_state = KVM_MP_STATE_INIT_RECEIVED;
>> + }
>
> Should you check vcpu->arch.guest_state_protected instead of
> special-casing TDX?
We cannot use vcpu->arch.guest_state_protected because TDX supports
debug TD, of which the states are not protected.
At least we need another flag, I think.
> KVM_APIC_INIT is not valid for SEV-ES either, if I
> remember correctly.
>
> Paolo
Powered by blists - more mailing lists