diff options
author | 2019-02-05 13:01:12 -0800 | |
---|---|---|
committer | 2019-02-20 22:48:33 +0100 | |
commit | e1359e2beb8b0a1188abc997273acbaedc8ee791 (patch) | |
tree | 6580d940b09ba1237ea00be4ddfe9fa09ebda312 /net/bluetooth/hci_request.c | |
parent | KVM: Call kvm_arch_memslots_updated() before updating memslots (diff) | |
download | wireguard-linux-e1359e2beb8b0a1188abc997273acbaedc8ee791.tar.xz wireguard-linux-e1359e2beb8b0a1188abc997273acbaedc8ee791.zip |
KVM: x86/mmu: Detect MMIO generation wrap in any address space
The check to detect a wrap of the MMIO generation explicitly looks for a
generation number of zero. Now that unique memslots generation numbers
are assigned to each address space, only address space 0 will get a
generation number of exactly zero when wrapping. E.g. when address
space 1 goes from 0x7fffe to 0x80002, the MMIO generation number will
wrap to 0x2. Adjust the MMIO generation to strip the address space
modifier prior to checking for a wrap.
Fixes: 4bd518f1598d ("KVM: use separate generations for each address space")
Cc: <stable@vger.kernel.org>
Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'net/bluetooth/hci_request.c')
0 files changed, 0 insertions, 0 deletions