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

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 > bounce buffers for I/O. While support for this was built into the virtio > core, virtio-ccw wasn't changed accordingly. > > Thus what needs to be done to bring virtio-ccw up to speed with respect > to this is: > *

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 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

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 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 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 linux.ibm.com> wrote: > > > As virtio-ccw devices are channel devices, we need to use the dma area > > for any communication with the hypervisor. > > > > This patch addresses the most basic stuff (mostly what is

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 linux.ibm.com> wrote: > > > > > As virtio-ccw devices are channel devices, we need to use the dma area > >

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 linux.ibm.com> wrote: > > > > > As virtio-ccw devices are channel devices, we need to use the dma area > >

On Mon, 13 May 2019 15:29:24 +0200 Cornelia Huck <cohuck at redhat.com> wrote: > On Sun, 12 May 2019 20:22:56 +0200 > Halil Pasic <pasic at linux.ibm.com> wrote: > > > On Fri, 10 May 2019 16:10:13 +0200 > > Cornelia Huck <cohuck at redhat.com> wrote: > > > > > On Fri, 10 May 2019 00:11:12 +0200 > > > Halil Pasic <pasic at

On 03.06.19 14:06, Cornelia Huck wrote: > On Wed, 29 May 2019 14:26:52 +0200 > Michael Mueller <mimu at linux.ibm.com> wrote: > >> From: Halil Pasic <pasic at linux.ibm.com> >> >> As virtio-ccw devices are channel devices, we need to use the dma area >> for any communication with the hypervisor. > > "we need to use the dma area within the

On Fri, 10 May 2019 16:10:13 +0200 Cornelia Huck <cohuck at redhat.com> wrote: > On Fri, 10 May 2019 00:11:12 +0200 > Halil Pasic <pasic at linux.ibm.com> wrote: > > > On Thu, 9 May 2019 12:11:06 +0200 > > Cornelia Huck <cohuck at redhat.com> wrote: > > > > > On Wed, 8 May 2019 23:22:10 +0200 > > > Halil Pasic <pasic at

On Wed, 29 May 2019 14:26:52 +0200 Michael Mueller <mimu at linux.ibm.com> wrote: > From: Halil Pasic <pasic at linux.ibm.com> > > As virtio-ccw devices are channel devices, we need to use the dma area > for any communication with the hypervisor. "we need to use the dma area within the common I/O layer for any communication with the hypervisor. Note that we do not

On Wed, 29 May 2019 14:26:52 +0200 Michael Mueller <mimu at linux.ibm.com> wrote: > From: Halil Pasic <pasic at linux.ibm.com> > > As virtio-ccw devices are channel devices, we need to use the dma area > for any communication with the hypervisor. "we need to use the dma area within the common I/O layer for any communication with the hypervisor. Note that we do not

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: >>> >>>>

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

On Sun, 12 May 2019 20:22:56 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > On Fri, 10 May 2019 16:10:13 +0200 > Cornelia Huck <cohuck at redhat.com> wrote: > > > On Fri, 10 May 2019 00:11:12 +0200 > > Halil Pasic <pasic at linux.ibm.com> wrote: > > > > > On Thu, 9 May 2019 12:11:06 +0200 > > > Cornelia Huck <cohuck at

On Sun, 12 May 2019 20:22:56 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > On Fri, 10 May 2019 16:10:13 +0200 > Cornelia Huck <cohuck at redhat.com> wrote: > > > On Fri, 10 May 2019 00:11:12 +0200 > > Halil Pasic <pasic at linux.ibm.com> wrote: > > > > > On Thu, 9 May 2019 12:11:06 +0200 > > > Cornelia Huck <cohuck at