On Fri, 3 May 2019 11:55:11 +0200 Cornelia Huck <cohuck@xxxxxxxxxx> wrote: > On Fri, 26 Apr 2019 20:32:35 +0200 > Halil Pasic <pasic@xxxxxxxxxxxxx> wrote: > > > What needs to be done > > ===================== > > > > Thus what needs to be done to bring virtio-ccw up to speed with respect > > to protected virtualization is: > > * use some 'new' common virtio stuff > > Doing this makes sense regardless of the protected virtualization use > case, and I think we should go ahead and merge those patches for 5.2. > > > * make sure that virtio-ccw specific stuff uses shared memory when > > talking to the hypervisor (except control/communication blocks like ORB, > > these are handled by the ultravisor) > > TBH, I'm still a bit hazy on what needs to use shared memory and what > doesn't. > > > * make sure the DMA API does what is necessary to talk through shared > > memory if we are a protected virtualization guest. > > * make sure the common IO layer plays along as well (airqs, sense). I've skimmed some more over the rest of the patches; but I think this needs review by someone else. For example, I'm not sure what the semantics of using the main css device as the dma device are, as I'm not sufficiently familiar with the intricacies of the dma infrastructure. Combine this with a lack of documentation of the hardware architecture, and I think that others can provide much better feedback on this than I am able to.
