diff options
| author | David Hildenbrand <dahi@linux.vnet.ibm.com> | 2015-11-06 12:08:48 +0100 |
|---|---|---|
| committer | Christian Borntraeger <borntraeger@de.ibm.com> | 2015-11-19 11:08:16 +0100 |
| commit | 5967c17b118a2bd1dd1d554cc4eee16233e52bec (patch) | |
| tree | 33126aa1bae62f2be5bcc754c5c4a0536e0eda30 /arch/s390/kvm/priv.c | |
| parent | 8005c49d9aea74d382f474ce11afbbc7d7130bec (diff) | |
KVM: s390: enable SIMD only when no VCPUs were created
We should never allow to enable/disable any facilities for the guest
when other VCPUs were already created.
kvm_arch_vcpu_(load|put) relies on SIMD not changing during runtime.
If somebody would create and run VCPUs and then decides to enable
SIMD, undefined behaviour could be possible (e.g. vector save area
not being set up).
Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
Acked-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Signed-off-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: stable@vger.kernel.org # 4.1+
Diffstat (limited to 'arch/s390/kvm/priv.c')
0 files changed, 0 insertions, 0 deletions