diff options
| author |   Liran Alon <liran.alon@oracle.com> | 2019-11-11 14:16:05 +0200 |
|---|---|---|
| committer |   Paolo Bonzini <pbonzini@redhat.com> | 2019-11-15 11:44:01 +0100 |
| commit | e64a8508234afb17a15d1aa98e8c1434fc207755 (patch) | |
| tree | b872ded857ec66c80b2b9d9e42a411d9a82a8948 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | KVM: x86: Prevent set vCPU into INIT/SIPI_RECEIVED state when INIT are latched (diff) | |
| download | linux-dev-e64a8508234afb17a15d1aa98e8c1434fc207755.tar.xz linux-dev-e64a8508234afb17a15d1aa98e8c1434fc207755.zip | |
KVM: VMX: Consume pending LAPIC INIT event when exit on INIT_SIGNAL
Intel SDM section 25.2 OTHER CAUSES OF VM EXITS specifies the following
on INIT signals: "Such exits do not modify register state or clear pending
events as they would outside of VMX operation."
When commit 4b9852f4f389 ("KVM: x86: Fix INIT signal handling in various CPU states")
was applied, I interepted above Intel SDM statement such that
INIT_SIGNAL exit don’t consume the LAPIC INIT pending event.
However, when Nadav Amit run matching kvm-unit-test on a bare-metal
machine, it turned out my interpetation was wrong. i.e. INIT_SIGNAL
exit does consume the LAPIC INIT pending event.
(See: https://www.spinics.net/lists/kvm/msg196757.html)
Therefore, fix KVM code to behave as observed on bare-metal.
Fixes: 4b9852f4f389 ("KVM: x86: Fix INIT signal handling in various CPU states")
Reported-by: Nadav Amit <nadav.amit@gmail.com>
Reviewed-by: Mihai Carabas <mihai.carabas@oracle.com>
Reviewed-by: Joao Martins <joao.m.martins@oracle.com>
Signed-off-by: Liran Alon <liran.alon@oracle.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