diff options
| author |   Sean Christopherson <sean.j.christopherson@intel.com> | 2020-07-02 19:35:31 -0700 |
|---|---|---|
| committer |   Paolo Bonzini <pbonzini@redhat.com> | 2020-07-09 13:29:39 -0400 |
| commit | f3747a5a9e5a26934da8c956ceef42639cbc623c (patch) | |
| tree | 3ef7a5b0da95d3f69d207f8bebb6cb5d3236acca /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | KVM: x86/mmu: Move fast_page_fault() call above mmu_topup_memory_caches() (diff) | |
| download | linux-dev-f3747a5a9e5a26934da8c956ceef42639cbc623c.tar.xz linux-dev-f3747a5a9e5a26934da8c956ceef42639cbc623c.zip | |
KVM: x86/mmu: Topup memory caches after walking GVA->GPA
Topup memory caches after walking the GVA->GPA translation during a
shadow page fault, there is no need to ensure the caches are full when
walking the GVA. As of commit f5a1e9f89504f ("KVM: MMU: remove call
to kvm_mmu_pte_write from walk_addr"), the FNAME(walk_addr) flow no
longer add rmaps via kvm_mmu_pte_write().
This avoids allocating memory in the case that the GVA is unmapped in
the guest, and also provides a paper trail of why/when the memory caches
need to be filled.
Reviewed-by: Ben Gardon <bgardon@google.com>
Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com>
Message-Id: <20200703023545.8771-8-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