On 12/16/22 20:40, Sean Christopherson wrote:
I was hoping to have a name that communicate_why_ the memslot needs to be inhibited, but it's turning out to be really hard to come up with a name that's descriptive without being ridiculously verbose. The best I've come up with is: allow_apicv_in_x2apic_without_x2apic_virtualization It's heinous, but I'm inclined to go with it unless someone has a better idea.
Can any of you provide a patch to squash on top of this one (or on top of kvm/queue, as you prefer)?
Paolo
