diff options
author | Roman Bolshakov | 2020-06-30 12:28:16 +0200 |
---|---|---|
committer | Paolo Bonzini | 2020-07-11 00:02:18 +0200 |
commit | b8d864f64341eb5825aed28aa9a6d1c98316b3e9 (patch) | |
tree | 996e2b075d3239308d6e50f3befaacfe2caa5ab4 /include | |
parent | coverity: provide Coverity-friendly MIN_CONST and MAX_CONST (diff) | |
download | qemu-b8d864f64341eb5825aed28aa9a6d1c98316b3e9.tar.gz qemu-b8d864f64341eb5825aed28aa9a6d1c98316b3e9.tar.xz qemu-b8d864f64341eb5825aed28aa9a6d1c98316b3e9.zip |
i386: hvf: Set env->eip in macvm_set_rip()
cpu_synchronize_state() is currently no-op for hvf but BIOS will hang in
vAPIC option ROM when cpu_synchronize_state() is wired to
hvf_cpu_synchronize_state().
cpu_synchronize_state() state is called from vapic_write() during option
ROM initialization. It sets dirty flag on the cpu. macvm_set_rip() is
then invoked to advance IP after the I/O write to vAPIC port.
macvm_set_rip() only modifies VMCS, it doesn't change env->eip.
Therefore on the next iteration of vCPU loop, vcpu_dirty flag is checked
and hvf_put_registers() overwrites correct RIP in VMCS with the value of
env->eip that points to the I/O write instruction. Execution of the CPU
gets stuck on the instruction.
The issue can be avoided if eip doesn't contain stale value when dirty
flag is set on cpu.
Cc: Cameron Esfahani <dirty@apple.com>
Signed-off-by: Roman Bolshakov <r.bolshakov@yadro.com>
Message-Id: <20200630102824.77604-2-r.bolshakov@yadro.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions