diff options
| author |   Sean Christopherson <sean.j.christopherson@intel.com> | 2019-02-05 13:01:15 -0800 |
|---|---|---|
| committer |   Paolo Bonzini <pbonzini@redhat.com> | 2019-02-20 22:48:35 +0100 |
| commit | 5192f9b976f9687569a90602b8a6c053da4498f6 (patch) | |
| tree | 13152edf16a5627d5ca9ade3704e01b6120a6c7a /net/bluetooth/hci_request.c | |
| parent | KVM: Explicitly define the "memslot update in-progress" bit (diff) | |
| download | wireguard-linux-5192f9b976f9687569a90602b8a6c053da4498f6.tar.xz wireguard-linux-5192f9b976f9687569a90602b8a6c053da4498f6.zip | |
KVM: x86: Use a u64 when passing the MMIO gen around
KVM currently uses an 'unsigned int' for the MMIO generation number
despite it being derived from the 64-bit memslots generation and
being propagated to (potentially) 64-bit sptes. There is no hidden
agenda behind using an 'unsigned int', it's done simply because the
MMIO generation will never set bits above bit 19.
Passing a u64 will allow the "update in-progress" flag to be relocated
from bit 0 to bit 63 and removes the need to cast the generation back
to a u64 when propagating it to a spte.
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