diff options
author | Carsten Otte <cotte@de.ibm.com> | 2011-10-18 12:27:14 +0200 |
---|---|---|
committer | Avi Kivity <avi@redhat.com> | 2011-10-30 12:24:00 +0200 |
commit | 7eef87dc99e419b1cc051e4417c37e4744d7b661 (patch) | |
tree | 70a611c3a92fb663c5da4ffae115e06c28e71b70 /include/linux/kvm.h | |
parent | b290411a1321dd937dce4aaa812e5d8fae8a14a5 (diff) | |
download | linux-3.10-7eef87dc99e419b1cc051e4417c37e4744d7b661.tar.gz linux-3.10-7eef87dc99e419b1cc051e4417c37e4744d7b661.tar.bz2 linux-3.10-7eef87dc99e419b1cc051e4417c37e4744d7b661.zip |
KVM: s390: fix register setting
KVM common code does vcpu_load prior to calling our arch ioctls and
vcpu_put after we're done here. Via the kvm_arch_vcpu_load/put
callbacks we do load the fpu and access register state into the
processor, which saves us moving the state on every SIE exit the
kernel handles. However this breaks register setting from userspace,
because of the following sequence:
1a. vcpu load stores userspace register content
1b. vcpu load loads guest register content
2. kvm_arch_vcpu_ioctl_set_fpu/sregs updates saved guest register content
3a. vcpu put stores the guest registers and overwrites the new content
3b. vcpu put loads the userspace register set again
This patch loads the new guest register state into the cpu, so that the correct
(new) set of guest registers will be stored in step 3a.
Signed-off-by: Carsten Otte <cotte@de.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Diffstat (limited to 'include/linux/kvm.h')
0 files changed, 0 insertions, 0 deletions