search for: vq_info_block_legaci

The CCW_CMD_SET_VQ command has a different format for revision 1+ devices, allowing to specify a more complex virtqueue layout. For now, we stay however with the old layout and simply use the new command format for virtio-1 devices. Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com> --- drivers/s390/kvm/virtio_ccw.c | 54 ++++++++++++++++++++++++++++++++--------- 1 file changed,

On 26/04/2019 20:32, Halil Pasic wrote: > This will come in handy soon when we pull out the indicators from > virtio_ccw_device to a memory area that is shared with the hypervisor > (in particular for protected virtualization guests). > > Signed-off-by: Halil Pasic <pasic at linux.ibm.com> > --- > drivers/s390/virtio/virtio_ccw.c | 40

On 26/04/2019 20:32, Halil Pasic wrote: > This will come in handy soon when we pull out the indicators from > virtio_ccw_device to a memory area that is shared with the hypervisor > (in particular for protected virtualization guests). > > Signed-off-by: Halil Pasic <pasic at linux.ibm.com> > --- > drivers/s390/virtio/virtio_ccw.c | 40

On 09/05/2019 20:26, Halil Pasic wrote: > On Thu, 9 May 2019 14:01:01 +0200 > Pierre Morel <pmorel at linux.ibm.com> wrote: > >> On 08/05/2019 16:31, Pierre Morel wrote: >>> On 26/04/2019 20:32, Halil Pasic wrote: >>>> This will come in handy soon when we pull out the indicators from >>>> virtio_ccw_device to a memory area that is shared with

On 09/05/2019 20:26, Halil Pasic wrote: > On Thu, 9 May 2019 14:01:01 +0200 > Pierre Morel <pmorel at linux.ibm.com> wrote: > >> On 08/05/2019 16:31, Pierre Morel wrote: >>> On 26/04/2019 20:32, Halil Pasic wrote: >>>> This will come in handy soon when we pull out the indicators from >>>> virtio_ccw_device to a memory area that is shared with

On 08/05/2019 16:31, Pierre Morel wrote: > On 26/04/2019 20:32, Halil Pasic wrote: >> This will come in handy soon when we pull out the indicators from >> virtio_ccw_device to a memory area that is shared with the hypervisor >> (in particular for protected virtualization guests). >> >> Signed-off-by: Halil Pasic <pasic at linux.ibm.com> >> --- >>

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 required for > virtio-ccw), and does take care of QDIO or any devices. "does not take care of QDIO",

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 required for > virtio-ccw), and does take care of QDIO or any devices. "does not take care of QDIO",

On 10/05/2019 13:54, Halil Pasic wrote: > On Fri, 10 May 2019 09:43:08 +0200 > Pierre Morel <pmorel at linux.ibm.com> wrote: > >> On 09/05/2019 20:26, Halil Pasic wrote: >>> On Thu, 9 May 2019 14:01:01 +0200 >>> Pierre Morel <pmorel at linux.ibm.com> wrote: >>> >>>> On 08/05/2019 16:31, Pierre Morel wrote: >>>>> On

On 10/05/2019 13:54, Halil Pasic wrote: > On Fri, 10 May 2019 09:43:08 +0200 > Pierre Morel <pmorel at linux.ibm.com> wrote: > >> On 09/05/2019 20:26, Halil Pasic wrote: >>> On Thu, 9 May 2019 14:01:01 +0200 >>> Pierre Morel <pmorel at linux.ibm.com> wrote: >>> >>>> On 08/05/2019 16:31, Pierre Morel wrote: >>>>> On

On Fri, 5 Apr 2019 01:16:12 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > Currently we have a problem if a virtio-ccw device has > VIRTIO_F_IOMMU_PLATFORM. Can you please describe what the actual problem is? > In future we do want to support DMA API with > virtio-ccw. > > Let us do the plumbing, so the feature VIRTIO_F_IOMMU_PLATFORM works > with virtio-ccw.

The commit 2a2d1382fe9d ("virtio: Add improved queue allocation API") establishes a new way of allocating virtqueues (as a part of the effort that taught DMA to virtio rings). In the future we will want virtio-ccw to use the DMA API as well. Let us switch from the legacy method of allocating virtqueues to vring_create_virtqueue() as the first step into that direction. Signed-off-by:

This will come in handy soon when we pull out the indicators from virtio_ccw_device to a memory area that is shared with the hypervisor (in particular for protected virtualization guests). Signed-off-by: Halil Pasic <pasic at linux.ibm.com> --- drivers/s390/virtio/virtio_ccw.c | 40 +++++++++++++++++++++++++--------------- 1 file changed, 25 insertions(+), 15 deletions(-) diff --git

On Fri, 10 May 2019 09:43:08 +0200 Pierre Morel <pmorel at linux.ibm.com> wrote: > On 09/05/2019 20:26, Halil Pasic wrote: > > On Thu, 9 May 2019 14:01:01 +0200 > > Pierre Morel <pmorel at linux.ibm.com> wrote: > > > >> On 08/05/2019 16:31, Pierre Morel wrote: > >>> On 26/04/2019 20:32, Halil Pasic wrote: > >>>> This will come

Currently virtio-ccw devices do not work if the device has VIRTIO_F_IOMMU_PLATFORM. In future we do want to support DMA API with virtio-ccw. Let us do the plumbing, so the feature VIRTIO_F_IOMMU_PLATFORM works with virtio-ccw. Let us also switch from legacy avail/used accessors to the DMA aware ones (even if it isn't strictly necessary), and remove the legacy accessors (we were the last

From: Halil Pasic <pasic at linux.ibm.com> This will come in handy soon when we pull out the indicators from virtio_ccw_device to a memory area that is shared with the hypervisor (in particular for protected virtualization guests). Signed-off-by: Halil Pasic <pasic at linux.ibm.com> Reviewed-by: Pierre Morel <pmorel at linux.ibm.com> --- drivers/s390/virtio/virtio_ccw.c | 40

This will come in handy soon when we pull out the indicators from virtio_ccw_device to a memory area that is shared with the hypervisor (in particular for protected virtualization guests). Signed-off-by: Halil Pasic <pasic at linux.ibm.com> Reviewed-by: Pierre Morel <pmorel at linux.ibm.com> Reviewed-by: Cornelia Huck <cohuck at redhat.com> --- drivers/s390/virtio/virtio_ccw.c

From: Halil Pasic <pasic at linux.ibm.com> This will come in handy soon when we pull out the indicators from virtio_ccw_device to a memory area that is shared with the hypervisor (in particular for protected virtualization guests). Signed-off-by: Halil Pasic <pasic at linux.ibm.com> Reviewed-by: Pierre Morel <pmorel at linux.ibm.com> Signed-off-by: Michael Mueller <mimu at

On Thu, 9 May 2019 14:01:01 +0200 Pierre Morel <pmorel at linux.ibm.com> wrote: > On 08/05/2019 16:31, Pierre Morel wrote: > > On 26/04/2019 20:32, Halil Pasic wrote: > >> This will come in handy soon when we pull out the indicators from > >> virtio_ccw_device to a memory area that is shared with the hypervisor > >> (in particular for protected

On Tue, 14 May 2019 10:47:34 -0400 "Jason J. Herne" <jjherne at linux.ibm.com> wrote: > On 5/13/19 5:41 AM, Cornelia Huck 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