| commit | 4fadfa00301695a4985e2a229cab857b2ce5c775 | |
| author | Peng Hao <peng.hao2@zte.com.cn> | |
| Fri, 14 Jul 2017 15:47:36 +0000 (14 23:47 +0800) | ||
| committer | Paolo Bonzini <pbonzini@redhat.com> | |
| Tue, 1 Aug 2017 15:27:33 +0000 (1 17:27 +0200) | ||
| tree | 40da96ebfb9c07cb51bd5d62c4a5aaae892e108e | treesnapshot (tar.gz zip) |
| parent | eb22aeca65f3769af33ba559757b42f24f743c18 | commitdiff |
target-i386: kvm_get/put_vcpu_events don't handle sipi_vector
qemu call kvm_get_vcpu_events, and kernel return sipi_vector always
0, never valid when reporting to user space. But when qemu calls
kvm_put_vcpu_events will make sipi_vector in kernel be 0. This will
accidently modify sipi_vector when sipi_vector in kernel is not 0.
Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>
Reviewed-by: Liu Yi <liu.yi24@zte.com.cn>
Message-Id: <1500047256-8911-1-git-send-email-peng.hao2@zte.com.cn>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
qemu call kvm_get_vcpu_events, and kernel return sipi_vector always
0, never valid when reporting to user space. But when qemu calls
kvm_put_vcpu_events will make sipi_vector in kernel be 0. This will
accidently modify sipi_vector when sipi_vector in kernel is not 0.
Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>
Reviewed-by: Liu Yi <liu.yi24@zte.com.cn>
Message-Id: <1500047256-8911-1-git-send-email-peng.hao2@zte.com.cn>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
| target/i386/kvm.c | diffblobblamehistory |