[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <36f2de4e-43fe-7280-8cac-f44de89b2b98@redhat.com>
Date: Wed, 22 Jun 2022 15:59:18 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Vitaly Kuznetsov <vkuznets@...hat.com>, kvm@...r.kernel.org
Cc: Sean Christopherson <seanjc@...gle.com>,
Maxim Levitsky <mlevitsk@...hat.com>,
Wanpeng Li <wanpengli@...cent.com>,
Jim Mattson <jmattson@...gle.com>,
Michael Kelley <mikelley@...rosoft.com>,
Siddharth Chandrasekaran <sidcha@...zon.de>,
Yuan Yao <yuan.yao@...ux.intel.com>,
linux-hyperv@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v7 10/39] KVM: x86: hyper-v: Don't use
sparse_set_to_vcpu_mask() in kvm_hv_send_ipi()
On 6/21/22 15:17, Vitaly Kuznetsov wrote:
>>
>> Just to be clear, PV IPI does*not* support the VP_ID, right?
> Hm, with Hyper-V PV IPI hypercall vCPUs are also addressed by their
> VP_IDs, not by their APIC ids so similar to Hyper-V PV TLB flush we need
> to convert the supplied set (either flat u64 bitmask of VP_IDs for
> non-EX hypercall or a sparse set for -EX).
>
So this means the series needs a v8, right?
Paolo
Powered by blists - more mailing lists