diff options
| author | Sean Christopherson <seanjc@google.com> | 2022-02-04 21:41:59 +0000 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2022-03-01 08:50:46 -0500 |
| commit | b51818afdc1d3c7cc269e295953685558d3af71c (patch) | |
| tree | af7dc8fcf64e7e84c37f05064196d4cec9c3f235 /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | KVM: SVM: Use common kvm_apic_write_nodecode() for AVIC write traps (diff) | |
| download | linux-b51818afdc1d3c7cc269e295953685558d3af71c.tar.gz linux-b51818afdc1d3c7cc269e295953685558d3af71c.zip | |
KVM: SVM: Don't rewrite guest ICR on AVIC IPI virtualization failure
Don't bother rewriting the ICR value into the vAPIC page on an AVIC IPI
virtualization failure, the access is a trap, i.e. the value has already
been written to the vAPIC page. The one caveat is if hardware left the
BUSY flag set (which appears to happen somewhat arbitrarily), in which
case go through the "nodecode" APIC-write path in order to clear the BUSY
flag.
Signed-off-by: Sean Christopherson <seanjc@google.com>
Message-Id: <20220204214205.3306634-6-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions