diff options
| author |   Sean Christopherson <sean.j.christopherson@intel.com> | 2020-09-23 13:13:46 -0700 |
|---|---|---|
| committer |   Paolo Bonzini <pbonzini@redhat.com> | 2020-09-28 07:57:51 -0400 |
| commit | 235ba74f008d2e0936b29f77f68d4e2f73ffd24a (patch) | |
| tree | 04e9a17a4e1278a27eaf47b480160c9b681c38ea /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | KVM: VMX: Add a helper to test for a valid error code given an intr info (diff) | |
| download | wireguard-linux-235ba74f008d2e0936b29f77f68d4e2f73ffd24a.tar.xz wireguard-linux-235ba74f008d2e0936b29f77f68d4e2f73ffd24a.zip | |
KVM: x86: Add intr/vectoring info and error code to kvm_exit tracepoint
Extend the kvm_exit tracepoint to align it with kvm_nested_vmexit in
terms of what information is captured. On SVM, add interrupt info and
error code, while on VMX it add IDT vectoring and error code. This
sets the stage for macrofying the kvm_exit tracepoint definition so that
it can be reused for kvm_nested_vmexit without loss of information.
Opportunistically stuff a zero for VM_EXIT_INTR_INFO if the VM-Enter
failed, as the field is guaranteed to be invalid. Note, it'd be
possible to further filter the interrupt/exception fields based on the
VM-Exit reason, but the helper is intended only for tracepoints, i.e.
an extra VMREAD or two is a non-issue, the failed VM-Enter case is just
low hanging fruit.
Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com>
Message-Id: <20200923201349.16097-5-sean.j.christopherson@intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions