summaryrefslogtreecommitdiffstats
path: root/arch/s390/kvm/interrupt.c
diff options
context:
space:
mode:
authorDavid Hildenbrand <dahi@linux.vnet.ibm.com>2016-01-18 14:46:34 +0100
committerChristian Borntraeger <borntraeger@de.ibm.com>2016-02-10 13:12:49 +0100
commit6fd8e67dd83437118cf46a4a9c224142004c3d51 (patch)
tree99b5feb06cbeb2fd6dbd0fd3a6adbac54dbe37fd /arch/s390/kvm/interrupt.c
parentf6aa6dc44948739be39c20bbcbbe8cff5d77fe18 (diff)
downloadop-kernel-dev-6fd8e67dd83437118cf46a4a9c224142004c3d51.zip
op-kernel-dev-6fd8e67dd83437118cf46a4a9c224142004c3d51.tar.gz
KVM: s390: sync of fp registers via kvm_run
As we already store the floating point registers in the vector save area in floating point register format when we don't have MACHINE_HAS_VX, we can directly expose them to user space using a new sync flag. The floating point registers will be valid when KVM_SYNC_FPRS is set. The fpc will also be valid when KVM_SYNC_FPRS is set. Either KVM_SYNC_FPRS or KVM_SYNC_VRS will be enabled, never both. Let's also change two positions where we access vrs, making the code easier to read and one comment superfluous. Suggested-by: Christian Borntraeger <borntraeger@de.ibm.com> Signed-off-by: David Hildenbrand <dahi@linux.vnet.ibm.com> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Diffstat (limited to 'arch/s390/kvm/interrupt.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud