Super nit: can I convince you to use "KVM: VMX:" instead of "KVM: x86: VMX:"? $ glo | grep -e "KVM: x86: nVMX" -e "KVM: x86: VMX:" | wc -l 8 $ glo | grep -e "KVM: nVMX" -e "KVM: VMX:" | wc -l 1032 I'm very conditioned to scan for "KVM: *VMX:", e.g. I was about to complain that this used the wrong scope :-) And in the event that Intel adds a new technology I'd like to be able to use "KVM: Intel:" and "KVM: ***X:" instead of "KVM: x86: Intel:" and "KVM: x86: Intel: ***X:" for code that is common to Intel versus specific to a technology. On Thu, Mar 05, 2020 at 11:01:22AM +0100, Vitaly Kuznetsov wrote: > The name 'kvm_area' is misleading (as we have way too many areas which are > KVM related), what alloc_kvm_area()/free_kvm_area() functions really do is > allocate/free VMXON region for all CPUs. Rename accordingly. > > No functional change intended. > > Signed-off-by: Vitaly Kuznetsov <vkuznets@xxxxxxxxxx> > --- +1000 Reviewed-by: Sean Christopherson <sean.j.christopherson@xxxxxxxxx>
