[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <23189be4-4410-d47e-820c-a3645d5b9e6d@redhat.com>
Date: Thu, 7 Apr 2022 15:14:57 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Kai Huang <kai.huang@...el.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>
Subject: Re: [RFC PATCH v5 089/104] KVM: TDX: Add a placeholder for handler of
TDX hypercalls (TDG.VP.VMCALL)
On 4/7/22 06:15, Kai Huang wrote:
>>
>> +static int handle_tdvmcall(struct kvm_vcpu *vcpu)
>> +{
>> + struct vcpu_tdx *tdx = to_tdx(vcpu);
>> +
>> + if (unlikely(tdx->tdvmcall.xmm_mask))
>> + goto unsupported;
> Put a comment explaining this logic?
>
This only seems to be necessary for Hyper-V hypercalls, which however
are not supported by this series in TDX guests (because the
kvm_hv_hypercall still calls kvm_*_read, likewise for Xen).
So for now this conditional can be dropped.
Since
Powered by blists - more mailing lists