aboutsummaryrefslogtreecommitdiff
path: root/target-ppc/kvm_ppc.h
diff options
context:
space:
mode:
authorBill Paul <wpaul@windriver.com>2015-09-30 15:33:29 -0700
committerEduardo Habkost <ehabkost@redhat.com>2015-10-02 16:22:02 -0300
commit2188cc52cb363433751f72b991d8fb05fc60e39d (patch)
treebebb3b6f42ec326040b3d9526caf82e1832df921 /target-ppc/kvm_ppc.h
parentbecb66673ec30cb604926d247ab9449a60ad8b11 (diff)
Correctly re-init EFER state during INIT IPI
When doing a re-initialization of a CPU core, the default state is to _not_ have 64-bit long mode enabled. This means the LME (long mode enable) and LMA (long mode active) bits in the EFER model-specific register should be cleared. However, the EFER state is part of the CPU environment which is preserved by do_cpu_init(), so if EFER.LME and EFER.LMA were set at the time an INIT IPI was received, they will remain set after the init completes. This is contrary to what the Intel architecture manual describes and what happens on real hardware, and it leaves the CPU in a weird state that the guest can't clear. To fix this, the 'efer' member of the CPUX86State structure has been moved to an area outside the region preserved by do_cpu_init(), so that it can be properly re-initialized by x86_cpu_reset(). Signed-off-by: Bill Paul <wpaul@windriver.com> CC: Paolo Bonzini <pbonzini@redhat.com> CC: Richard Henderson <rth@twiddle.net> CC: Eduardo Habkost <ehabkost@redhat.com> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Diffstat (limited to 'target-ppc/kvm_ppc.h')
0 files changed, 0 insertions, 0 deletions