diff options
author | Sean Christopherson <sean.j.christopherson@intel.com> | 2020-01-08 23:24:46 +0300 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2020-01-27 22:00:08 +0300 |
commit | 293e306e7faac4eafaefb9518a1cd6eaecad88e9 (patch) | |
tree | 5f602370c71d3ed81ef44618078f55c870e108f3 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | d32ec81bab670e599e645e1d1d5231d62de7d0d6 (diff) | |
download | linux-293e306e7faac4eafaefb9518a1cd6eaecad88e9.tar.xz |
KVM: x86/mmu: Fold max_mapping_level() into kvm_mmu_hugepage_adjust()
Fold max_mapping_level() into kvm_mmu_hugepage_adjust() now that HugeTLB
mappings are handled in kvm_mmu_hugepage_adjust(), i.e. there isn't a
need to pre-calculate the max mapping level. Co-locating all hugepage
checks eliminates a memslot lookup, at the cost of performing the
__mmu_gfn_lpage_is_disallowed() checks while holding mmu_lock.
The latency of lpage_is_disallowed() is likely negligible relative to
the rest of the code run while holding mmu_lock, and can be offset to
some extent by eliminating the mmu_gfn_lpage_is_disallowed() check in
set_spte() in a future patch. Eliminating the check in set_spte() is
made possible by performing the initial lpage_is_disallowed() checks
while holding mmu_lock.
Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions