summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorSean Christopherson <seanjc@google.com>2022-12-01 02:08:49 +0300
committerPaolo Bonzini <pbonzini@redhat.com>2022-12-29 23:40:48 +0300
commitb801ef42149fe5cba21bb6fe80c6d8e4c031f990 (patch)
tree5f0f5e3c015447e45ff934036f672a8411443a67 /tools/perf/scripts/python/stackcollapse.py
parent73b8dc04132c1f8d4f9250a39f1fc9878ba2ee13 (diff)
downloadlinux-b801ef42149fe5cba21bb6fe80c6d8e4c031f990.tar.xz
KVM: s390: Unwind kvm_arch_init() piece-by-piece() if a step fails
In preparation for folding kvm_arch_hardware_setup() into kvm_arch_init(), unwind initialization one step at a time instead of simply calling kvm_arch_exit(). Using kvm_arch_exit() regardless of which initialization step failed relies on all affected state playing nice with being undone even if said state wasn't first setup. That holds true for state that is currently configured by kvm_arch_init(), but not for state that's handled by kvm_arch_hardware_setup(), e.g. calling gmap_unregister_pte_notifier() without first registering a notifier would result in list corruption due to attempting to delete an entry that was never added to the list. Signed-off-by: Sean Christopherson <seanjc@google.com> Reviewed-by: Eric Farman <farman@linux.ibm.com> Message-Id: <20221130230934.1014142-6-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