Messages in this thread | | | Date | Thu, 19 May 2022 17:29:12 +0800 | From | Chao Gao <> | Subject | Re: [PATCH v9 0/9] IPI virtualization support for VM |
| |
On Tue, May 17, 2022 at 10:02:23PM +0800, Chao Gao wrote: >+ Maxim > >On Tue, May 17, 2022 at 09:53:26PM +0800, Chao Gao wrote: >>On Mon, May 16, 2022 at 08:49:52PM +0000, Sean Christopherson wrote: >>>On Tue, May 03, 2022, Paolo Bonzini wrote: >>>> On 5/3/22 09:32, Zeng Guang wrote: >>>> > >>>> > I don't see "[PATCH v9 4/9] KVM: VMX: Report tertiary_exec_control field in >>>> > dump_vmcs()" in kvm/queue. Does it not need ? >>>> >>>> Added now (somehow the patches were not threaded, so I had to catch them one >>>> by one from lore). >>>> >>>> > Selftests for KVM_CAP_MAX_VCPU_ID is posted in V2 which is revised on top of >>>> > kvm/queue. >>>> > ([PATCH v2] kvm: selftests: Add KVM_CAP_MAX_VCPU_ID cap test - Zeng >>>> > Guang (kernel.org) <https://lore.kernel.org/lkml/20220503064037.10822-1-guang.zeng@intel.com/>) >>>> >>>> Queued, thanks. >>> >>>Shouldn't we have a solution for the read-only APIC_ID mess before this is merged?
Paolo & Sean,
If a solution for read-only APIC ID mess is needed before merging IPIv series, do you think the Maxim's patch [1] after some improvement will suffice? Let us know if there is any gap.
[1]: https://lore.kernel.org/all/20220427200314.276673-3-mlevitsk@redhat.com/
| |