diff options
author | 2020-07-10 16:11:54 +0200 | |
---|---|---|
committer | 2020-07-10 12:56:30 -0400 | |
commit | bf7dea425327c5da12f540a1595f22770597e496 (patch) | |
tree | e0c3fd4b453855af3a8f1e380f85ce11fc92ee75 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | KVM: nSVM: introduce nested_svm_load_cr3()/nested_npt_enabled() (diff) | |
download | wireguard-linux-bf7dea425327c5da12f540a1595f22770597e496.tar.xz wireguard-linux-bf7dea425327c5da12f540a1595f22770597e496.zip |
KVM: nSVM: move kvm_set_cr3() after nested_svm_uninit_mmu_context()
kvm_mmu_new_pgd() refers to arch.mmu and at this point it still references
arch.guest_mmu while arch.root_mmu is expected.
Note, the change is effectively a nop: when !npt_enabled,
nested_svm_uninit_mmu_context() does nothing (as we don't do
nested_svm_init_mmu_context()) and with npt_enabled we don't
do kvm_set_cr3(). However, it will matter when we move the
call to kvm_mmu_new_pgd into nested_svm_load_cr3().
No functional change intended.
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Message-Id: <20200710141157.1640173-7-vkuznets@redhat.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