summaryrefslogtreecommitdiffstats
path: root/arch/s390/kvm/priv.c
diff options
context:
space:
mode:
authorDominik Dingel <dingel@linux.vnet.ibm.com>2014-01-14 18:10:17 +0100
committerChristian Borntraeger <borntraeger@de.ibm.com>2014-04-22 09:36:25 +0200
commit934bc131efc3e4be6a52f7dd6c4dbf99635e381a (patch)
tree67b5df8e42e7db5f1f59f7d851b97923b5336678 /arch/s390/kvm/priv.c
parentd4cb11340be6a1613d40d2b546cb111ea2547066 (diff)
downloadtalos-op-linux-934bc131efc3e4be6a52f7dd6c4dbf99635e381a.tar.gz
talos-op-linux-934bc131efc3e4be6a52f7dd6c4dbf99635e381a.zip
KVM: s390: Allow skeys to be enabled for the current process
Introduce a new function s390_enable_skey(), which enables storage key handling via setting the use_skey flag in the mmu context. This function is only useful within the context of kvm. Note that enabling storage keys will cause a one-time hickup when walking the page table; however, it saves us special effort for cases like clear reset while making it possible for us to be architecture conform. s390_enable_skey() takes the page table lock to prevent reseting storage keys triggered from multiple vcpus. Signed-off-by: Dominik Dingel <dingel@linux.vnet.ibm.com> Acked-by: Martin Schwidefsky <schwidefsky@de.ibm.com> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Diffstat (limited to 'arch/s390/kvm/priv.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud