diff options
| author | Sean Christopherson <seanjc@google.com> | 2021-06-22 20:56:57 +0300 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2021-06-25 01:00:38 +0300 |
| commit | 479a1efc8119d8699cca73d00625b28003d0a1f8 (patch) | |
| tree | 2020f2e0455185f23cdec2e66bc287f809f6708a /tools/perf/scripts/python/stackcollapse.py | |
| parent | 07dc4f35a44c8f85ba7262b56b70c3fcbc3b74fd (diff) | |
| download | linux-479a1efc8119d8699cca73d00625b28003d0a1f8.tar.xz | |
KVM: x86/mmu: Drop the intermediate "transient" __kvm_sync_page()
Nove the kvm_unlink_unsync_page() call out of kvm_sync_page() and into
it's sole caller, and fold __kvm_sync_page() into kvm_sync_page() since
the latter becomes a pure pass-through. There really should be no reason
for code to do a complete sync of a shadow page outside of the full
kvm_mmu_sync_roots(), e.g. the one use case that creeped in turned out to
be flawed and counter-productive.
Drop the stale comment about @sp->gfn needing to be write-protected, as
it directly contradicts the kvm_mmu_get_page() usage.
No functional change intended.
Signed-off-by: Sean Christopherson <seanjc@google.com>
Message-Id: <20210622175739.3610207-13-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions
