On Tue, Mar 08, 2022 at 11:04:01PM +0000, Sean Christopherson wrote: >On Fri, Feb 25, 2022, Zeng Guang wrote: >> From: Maxim Levitsky <mlevitsk@xxxxxxxxxx> >> >> No normal guest has any reason to change physical APIC IDs, > >I don't think we can reasonably assume this, my analysis in the link (that I just >realized I deleted from context here) shows it's at least plausible that an existing >guest could rely on the APIC ID being writable. And that's just one kernel, who >know what else is out there, especially given that people use KVM to emulate really >old stuff, often on really old hardware. Making xAPIC ID readonly is not only based on your analysis, but also Intel SDM clearly saying writable xAPIC ID is processor model specific and ***software should avoid writing to xAPIC ID***. If writable xAPIC ID support should be retained and is tied to a module param, live migration would depend on KVM's module params: e.g., migrate a VM with modified xAPIC ID (apic_id_readonly off on this system) to one with xapic_id_readonly on would fail, right? Is this failure desired? if not, we need to have a VM-scope control. e.g., add an inhibitor of APICv (XAPIC_ID_MODIFIED) and disable APICv forever for this VM if its vCPUs or QEMU modifies xAPIC ID. > >Practically speaking, anyone that wants to deploy IPIv is going to have to make >the switch at some point, but that doesn't help people running legacy crud that >don't care about IPIv. > >I was thinking a module param would be trivial, and it is (see below) if the >param is off by default. A module param will also provide a convenient opportunity >to resolve the loophole reported by Maxim[1][2], though it's a bit funky. Could you share the links? > >Anyways, with an off-by-default module param, we can just do: > > if (!enable_apicv || !cpu_has_vmx_ipiv() || !xapic_id_readonly) > enable_ipiv = false; > >Forcing userspace to take advantage of IPIv is rather annoying, but it's not the >end of world. > >Having the param on by default is a mess. Either we break userspace (above), or >we only kinda break userspace by having it on iff IPIv is on, but then we end up >with cyclical dependency hell. E.g. userspace makes xAPIC ID writable and forces >on IPIv, which one "wins"? And if it's on by default, we can't fix the loophole >in KVM_SET_LAPIC. We are fine with having this param off by default.
