diff options
| author | Maxim Levitsky <mlevitsk@redhat.com> | 2021-08-10 23:52:50 +0300 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2021-08-20 16:06:30 -0400 |
| commit | df7e4827c5490a6a0cc41341497f5267712511cf (patch) | |
| tree | c1ba4d2372f98fb0301e21561456a6dcd004f523 /arch/s390/kvm | |
| parent | bf5f6b9d7ad6b88df15d691d9759f9a397488c7e (diff) | |
| download | linux-stable-df7e4827c5490a6a0cc41341497f5267712511cf.tar.gz linux-stable-df7e4827c5490a6a0cc41341497f5267712511cf.tar.bz2 linux-stable-df7e4827c5490a6a0cc41341497f5267712511cf.zip | |
KVM: SVM: call avic_vcpu_load/avic_vcpu_put when enabling/disabling AVIC
Currently it is possible to have the following scenario:
1. AVIC is disabled by svm_refresh_apicv_exec_ctrl
2. svm_vcpu_blocking calls avic_vcpu_put which does nothing
3. svm_vcpu_unblocking enables the AVIC (due to KVM_REQ_APICV_UPDATE)
and then calls avic_vcpu_load
4. warning is triggered in avic_vcpu_load since
AVIC_PHYSICAL_ID_ENTRY_IS_RUNNING_MASK was never cleared
While it is possible to just remove the warning, it seems to be more robust
to fully disable/enable AVIC in svm_refresh_apicv_exec_ctrl by calling the
avic_vcpu_load/avic_vcpu_put
Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
Message-Id: <20210810205251.424103-16-mlevitsk@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'arch/s390/kvm')
0 files changed, 0 insertions, 0 deletions