aboutsummaryrefslogtreecommitdiff
path: root/arch/x86/kvm/svm/nested.c
diff options
context:
space:
mode:
authorSean Christopherson <seanjc@google.com>2022-05-02 00:07:31 +0200
committerPaolo Bonzini <pbonzini@redhat.com>2022-06-08 04:46:55 -0400
commita61d7c5432ac5a953bbcec17af031661c2bd201d (patch)
tree5ff495c8c434744dea1eff9e5262f4bd30e230a6 /arch/x86/kvm/svm/nested.c
parent7e5b5ef8dca3229a5226eabf53bdc7b67ebd07ad (diff)
downloadlinux-a61d7c5432ac5a953bbcec17af031661c2bd201d.tar.gz
linux-a61d7c5432ac5a953bbcec17af031661c2bd201d.tar.bz2
linux-a61d7c5432ac5a953bbcec17af031661c2bd201d.zip
KVM: x86: Trace re-injected exceptions
Trace exceptions that are re-injected, not just those that KVM is injecting for the first time. Debugging re-injection bugs is painful enough as is, not having visibility into what KVM is doing only makes things worse. Delay propagating pending=>injected in the non-reinjection path so that the tracing can properly identify reinjected exceptions. Signed-off-by: Sean Christopherson <seanjc@google.com> Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com> Signed-off-by: Maciej S. Szmigiero <maciej.szmigiero@oracle.com> Message-Id: <25470690a38b4d2b32b6204875dd35676c65c9f2.1651440202.git.maciej.szmigiero@oracle.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'arch/x86/kvm/svm/nested.c')
0 files changed, 0 insertions, 0 deletions