lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 17 May 2022 22:02:23 +0800 From: Chao Gao <chao.gao@...el.com> To: Sean Christopherson <seanjc@...gle.com>, Maxim Levitsky <mlevitsk@...hat.com> Cc: Paolo Bonzini <pbonzini@...hat.com>, Zeng Guang <guang.zeng@...el.com>, Vitaly Kuznetsov <vkuznets@...hat.com>, Wanpeng Li <wanpengli@...cent.com>, Jim Mattson <jmattson@...gle.com>, Joerg Roedel <joro@...tes.org>, "kvm@...r.kernel.org" <kvm@...r.kernel.org>, Dave Hansen <dave.hansen@...ux.intel.com>, "Luck, Tony" <tony.luck@...el.com>, Kan Liang <kan.liang@...ux.intel.com>, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>, "H. Peter Anvin" <hpa@...or.com>, Kim Phillips <kim.phillips@....com>, Jarkko Sakkinen <jarkko@...nel.org>, Jethro Beekman <jethro@...tanix.com>, "Huang, Kai" <kai.huang@...el.com>, "x86@...nel.org" <x86@...nel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "Hu, Robert" <robert.hu@...el.com> Subject: Re: [PATCH v9 0/9] IPI virtualization support for VM + 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? > >We can add a new inhibit to disable APICv if guest attempts to change APIC >ID when IPIv (or AVIC) is enabled. Maxim also thinks using a new inhibit is >the right direction [1]. > >If no objection to this approach and Maxim doesn't have the patch, we can post >one. But we will rely on Maxim to fix APIC ID mess for nested AVIC. > >[1] https://lore.kernel.org/all/6475522c58aec5db3ee0a5ccd3230c63a2f013a9.camel@redhat.com/
Powered by blists - more mailing lists