similar to: [RFC PATCH 00/12] s390: virtio: support protected virtualization

On 05.04.19 01:16, Halil Pasic wrote: > Enhanced virtualization protection technology may require the use of > bounce buffers for I/O. While support for this was built into the virtio > core, virtio-ccw wasn't changed accordingly. Can you elaborate some more about the general approach (Enhanced virtualization protection technology, ultravisor, concept, issues, how to squeeze it into

On Fri, 26 Apr 2019 20:32:35 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > Enhanced virtualization protection technology may require the use of > bounce buffers for I/O. While support for this was built into the virtio > core, virtio-ccw wasn't changed accordingly. > > Some background on technology (not part of this series) and the > terminology used. > >

Halil, I just ran my toleration tests successfully on current HW for this series. Michael On 12.06.19 13:12, Halil Pasic wrote: > Enhanced virtualization protection technology may require the use of > bounce buffers for I/O. While support for this was built into the virtio > core, virtio-ccw wasn't changed accordingly. > > Some background on technology (not part of this

On Thu, 13 Jun 2019 11:11:13 +0200 Michael Mueller <mimu at linux.ibm.com> wrote: > Halil, > > I just ran my toleration tests successfully on current HW for > this series. > > Michael Thanks Michael! May I add a Tested-by: Michael Mueller <mimu at linux.ibm.com> for each patch? > > On 12.06.19 13:12, Halil Pasic wrote: > > Enhanced virtualization

On Wed, 10 Apr 2019 17:57:50 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > On Wed, 10 Apr 2019 11:20:48 +0200 > Cornelia Huck <cohuck at redhat.com> wrote: > > > On Fri, 5 Apr 2019 01:16:10 +0200 > > Halil Pasic <pasic at linux.ibm.com> wrote: > > > > > Enhanced virtualization protection technology may require the use of > >

On Wed, 10 Apr 2019 02:10:44 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > On Tue, 9 Apr 2019 19:55:48 +0200 > Cornelia Huck <cohuck at redhat.com> wrote: > > > On Fri, 5 Apr 2019 01:16:15 +0200 > > Halil Pasic <pasic at linux.ibm.com> wrote: > > > Thus we need to make sure any memory that is used for communication with > > > the

On 16.04.19 13:10, Halil Pasic wrote: > On Fri, 12 Apr 2019 15:47:50 +0200 > David Hildenbrand <david at redhat.com> wrote: > >> On 05.04.19 01:16, Halil Pasic wrote: >>> Enhanced virtualization protection technology may require the use of >>> bounce buffers for I/O. While support for this was built into the virtio >>> core, virtio-ccw wasn't

On Fri, 5 Apr 2019 01:16:17 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > 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. > > Let us make sure all ccw I/O is done through

On Fri, 5 Apr 2019 01:16:13 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > On s390 protected virtualization guests also have to use bounce I/O > buffers. That requires some plumbing. > > Let us make sure any device using DMA API accordingly is spared from the > problems that hypervisor attempting I/O to a non-shared secure page would > bring. I have problems

> Subject: [PATCH 04/10] s390/mm: force swiotlb for protected virtualization > Date: Fri, 26 Apr 2019 20:32:39 +0200 > From: Halil Pasic <pasic at linux.ibm.com> > To: kvm at vger.kernel.org, linux-s390 at vger.kernel.org, Cornelia Huck <cohuck at redhat.com>, > Martin Schwidefsky <schwidefsky at de.ibm.com>, Sebastian Ott <sebott at linux.ibm.com> > CC:

On Tue, 9 Apr 2019 12:54:16 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > On Tue, 9 Apr 2019 12:16:47 +0200 > Cornelia Huck <cohuck at redhat.com> wrote: > > > On Fri, 5 Apr 2019 01:16:13 +0200 > > Halil Pasic <pasic at linux.ibm.com> wrote: > > > > > On s390 protected virtualization guests also have to use bounce I/O > > >

Enhanced virtualization protection technology may require the use of bounce buffers for I/O. While support for this was built into the virtio core, virtio-ccw wasn't changed accordingly. Some background on technology (not part of this series) and the terminology used. * Protected Virtualization (PV): Protected Virtualization guarantees, that non-shared memory of a guest that operates in PV

Enhanced virtualization protection technology may require the use of bounce buffers for I/O. While support for this was built into the virtio core, virtio-ccw wasn't changed accordingly. Some background on technology (not part of this series) and the terminology used. * Protected Virtualization (PV): Protected Virtualization guarantees, that non-shared memory of a guest that operates in PV

On Mon, 20 May 2019 12:21:43 +0200 Cornelia Huck <cohuck at redhat.com> wrote: > On Sat, 18 May 2019 20:11:00 +0200 > Halil Pasic <pasic at linux.ibm.com> wrote: > > > On Thu, 16 May 2019 08:29:28 +0200 > > Cornelia Huck <cohuck at redhat.com> wrote: > > > > > On Wed, 15 May 2019 22:51:58 +0200 > > > Halil Pasic <pasic at

Enhanced virtualization protection technology may require the use of bounce buffers for I/O. While support for this was built into the virtio core, virtio-ccw wasn't changed accordingly. Some background on technology (not part of this series) and the terminology used. * Protected Virtualization (PV): Protected Virtualization guarantees, that non-shared memory of a guest that operates in PV

On Fri, 5 Apr 2019 01:16:15 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > Virtio-ccw relies on cio mechanisms for bootstrapping the ccw device. Well, a ccw device is, by definition, using cio mechanisms ;) Better say: "As virtio-ccw devices are channel devices, we need to use the dma area for any communication with the hypervisor." Or something like that. > Thus we

Enhanced virtualization protection technology may require the use of bounce buffers for I/O. While support for this was built into the virtio core, virtio-ccw wasn't changed accordingly. Some background on technology (not part of this series) and the terminology used. * Protected Virtualization (PV): Protected Virtualization guarantees, that non-shared memory of a guest that operates in PV

On Thu, 16 May 2019 08:29:28 +0200 Cornelia Huck <cohuck at redhat.com> wrote: > On Wed, 15 May 2019 22:51:58 +0200 > Halil Pasic <pasic at linux.ibm.com> wrote: > > > On Mon, 13 May 2019 11:41:36 +0200 > > Cornelia Huck <cohuck at redhat.com> wrote: > > > > > On Fri, 26 Apr 2019 20:32:41 +0200 > > > Halil Pasic <pasic at

On Mon, 3 Jun 2019 18:17:16 +0200 Cornelia Huck <cohuck at redhat.com> wrote: > On Wed, 29 May 2019 14:26:56 +0200 > Michael Mueller <mimu at linux.ibm.com> wrote: > > > From: Halil Pasic <pasic at linux.ibm.com> > > > > Before virtio-ccw could get away with not using DMA API for the pieces of > > memory it does ccw I/O with. With protected

On 27.05.19 15:31, Cornelia Huck wrote: > On Mon, 27 May 2019 14:30:14 +0200 > Halil Pasic <pasic at linux.ibm.com> wrote: > >> On Mon, 27 May 2019 12:38:02 +0200 >> Cornelia Huck <cohuck at redhat.com> wrote: >> >>> On Thu, 23 May 2019 18:22:04 +0200 >>> Michael Mueller <mimu at linux.ibm.com> wrote: >>> >>>>