Fix a bug where CR4.TSD isn't correctly marked as being possibly owned by the guest in the common x86 macro, then clean up the mess that made the bug possible by throwing away VMX's mix of duplicate code and open coded tweaks. The lack of a define for the guest-owned CR0 bit has bugged me for a long time, but adding another define always seemed ridiculous. Sean Christopherson (2): KVM: x86: Mark CR4.TSD as being possibly owned by the guest KVM: VMX: Use KVM_POSSIBLE_CR*_GUEST_BITS to initialize guest/host masks arch/x86/kvm/kvm_cache_regs.h | 2 +- arch/x86/kvm/vmx/nested.c | 4 ++-- arch/x86/kvm/vmx/vmx.c | 13 +++++-------- 3 files changed, 8 insertions(+), 11 deletions(-) -- 2.26.0