aboutsummaryrefslogtreecommitdiffstats
path: root/tools
diff options
context:
space:
mode:
authorHalil Pasic <pasic@linux.ibm.com>2018-10-01 19:01:58 +0200
committerHeiko Carstens <heiko.carstens@de.ibm.com>2019-06-15 12:25:37 +0200
commit48720ba56891570e3b750b271d80efb631478630 (patch)
treed627142b215c82aed80c2513564f1040bda21370 /tools
parentvirtio/s390: add indirection to indicators access (diff)
downloadlinux-dev-48720ba56891570e3b750b271d80efb631478630.tar.xz
linux-dev-48720ba56891570e3b750b271d80efb631478630.zip
virtio/s390: use DMA memory for ccw I/O and classic notifiers
Before virtio-ccw could get away with not using DMA API for the pieces of memory it does ccw I/O with. With protected virtualization this has to change, since the hypervisor needs to read and sometimes also write these pieces of memory. The hypervisor is supposed to poke the classic notifiers, if these are used, out of band with regards to ccw I/O. So these need to be allocated as DMA memory (which is shared memory for protected virtualization guests). Let us factor out everything from struct virtio_ccw_device that needs to be DMA memory in a satellite that is allocated as such. Note: The control blocks of I/O instructions do not need to be shared. These are marshalled by the ultravisor. Signed-off-by: Halil Pasic <pasic@linux.ibm.com> Reviewed-by: Pierre Morel <pmorel@linux.ibm.com> Reviewed-by: Cornelia Huck <cohuck@redhat.com> Reviewed-by: Michael Mueller <mimu@linux.ibm.com> Tested-by: Michael Mueller <mimu@linux.ibm.com> Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions