qemu call kvm_get_vcpu_events, and kernel return sipi_vector always 0,
never valid when reporting to user space. But qemu call 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.h...@zte.com.cn>
Reviewed-by: Wang Yechao <wang.yechao...@zte.com.cn>
---
target/i386/kvm.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/target/i386/kvm.c b/target/i386/kvm.c
index f84a49d..bbbd696 100644
--- a/target/i386/kvm.c
+++ b/target/i386/kvm.c
@@ -2417,7 +2417,6 @@ static int kvm_put_vcpu_events(X86CPU *cpu, int level)
events.nmi.masked = !!(env->hflags2 & HF2_NMI_MASK);
events.nmi.pad = 0;
- events.sipi_vector = env->sipi_vector;
events.flags = 0;
if (has_msr_smbase) {
@@ -2506,8 +2505,6 @@ static int kvm_get_vcpu_events(X86CPU *cpu)
}
}
- env->sipi_vector = events.sipi_vector;
-
return 0;
}
--
1.8.3.1
