diff options
| author | David Hildenbrand <dahi@linux.vnet.ibm.com> | 2015-05-12 08:41:40 +0200 |
|---|---|---|
| committer | Christian Borntraeger <borntraeger@de.ibm.com> | 2015-06-02 09:38:01 +0200 |
| commit | 61a6df54b64913defc64c87a05d5d258a2020fb5 (patch) | |
| tree | 7ea9c20fc83b663729d8427924df48e4064aa81a /crypto/proc.c | |
| parent | 06b36753a6466239fc945b6756e12d635621ae5f (diff) | |
KVM: s390: call exit_sie() directly on vcpu block/request
Thinking about it, I can't find a real use case where we want
to block a VCPU and not kick it out of SIE. (except if we want
to do the same in batch for multiple VCPUs - but that's a micro
optimization)
So let's simply perform the exit_sie() calls directly when setting
the other magic block bits in the SIE.
Otherwise e.g. kvm_s390_set_tod_low() still has other VCPUs running
after that call, working with a wrong epoch.
Fixes: 27406cd50c ("KVM: s390: provide functions for blocking all CPUs")
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 'crypto/proc.c')
0 files changed, 0 insertions, 0 deletions