diff options
| author | David Hildenbrand <dahi@linux.vnet.ibm.com> | 2015-11-25 11:08:32 +0100 |
|---|---|---|
| committer | Christian Borntraeger <borntraeger@de.ibm.com> | 2016-06-21 09:43:38 +0200 |
| commit | c9bc1eabe5ee49f1be68550cc0bd907b55d9da8d (patch) | |
| tree | 3ddfcece05fb1b667ac4cf7fbe34557970411770 /virt | |
| parent | 166ecb3d3cfecb62c31fdeab9949d70e84cd75cd (diff) | |
KVM: s390: vsie: support vectory facility (SIMD)
As soon as guest 2 is allowed to use the vector facility (indicated via
STFLE), it can also enable it for guest 3. We have to take care of the
sattellite block that might be used when not relying on lazy vector
copying (not the case for KVM).
Acked-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 'virt')
0 files changed, 0 insertions, 0 deletions