search for: virtio_ccw_device

Displaying 20 results from an estimated 293 matches for "virtio_ccw_device".

2019 Apr 26
0
[PATCH 09/10] virtio/s390: use DMA memory for ccw I/O and classic notifiers
...s 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 at linux.ibm.com> --- drivers/s390/virtio/virtio_ccw.c | 177 ++++++++++++++...
2019 May 23
0
[PATCH v2 7/8] virtio/s390: use DMA memory for ccw I/O and classic notifiers
...s 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 at linux.ibm.com> Reviewed-by: Pierre Morel <pmorel at linux.ibm.com>...
2019 May 29
0
[PATCH v3 7/8] virtio/s390: use DMA memory for ccw I/O and classic notifiers
...s 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 at linux.ibm.com> Reviewed-by: Pierre Morel <pmorel at linux.ibm.com>...
2014 Apr 25
0
[PATCH 1/1] virtio_ccw: introduce device_lost in virtio_ccw_device
....c +++ b/drivers/s390/kvm/virtio_ccw.c @@ -27,6 +27,7 @@ #include <linux/module.h> #include <linux/io.h> #include <linux/kvm_para.h> +#include <linux/notifier.h> #include <asm/setup.h> #include <asm/irq.h> #include <asm/cio.h> @@ -62,6 +63,7 @@ struct virtio_ccw_device { struct vq_config_block *config_block; bool is_thinint; bool going_away; + bool device_lost; void *airq_info; }; @@ -1010,11 +1012,14 @@ static void virtio_ccw_remove(struct ccw_device *cdev) unsigned long flags; struct virtio_ccw_device *vcdev = virtio_grab_drvdata(cdev); - if (v...
2019 May 08
2
[PATCH 08/10] virtio/s390: add indirection to indicators access
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 +++++++++++++++++++++++++--------------- > 1 file changed, 25...
2019 May 08
2
[PATCH 08/10] virtio/s390: add indirection to indicators access
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 +++++++++++++++++++++++++--------------- > 1 file changed, 25...
2019 Jun 06
0
[PATCH v4 7/8] virtio/s390: use DMA memory for ccw I/O and classic notifiers
...s 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 at linux.ibm.com> Reviewed-by: Pierre Morel <pmorel at linux.ibm.com>...
2019 Jun 12
0
[PATCH v5 7/8] virtio/s390: use DMA memory for ccw I/O and classic notifiers
...s 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 at linux.ibm.com> Reviewed-by: Pierre Morel <pmorel at linux.ibm.com>...
2019 May 10
2
[PATCH 08/10] virtio/s390: add indirection to indicators access
...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 virtualization guests). >>>> >>>> Signed-off-by: Halil Pasic <pasic at linux.ibm.com> >>>> --- >>>> ? drivers/s390/virtio/virtio_ccw.c | 40 >&g...
2019 May 10
2
[PATCH 08/10] virtio/s390: add indirection to indicators access
...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 virtualization guests). >>>> >>>> Signed-off-by: Halil Pasic <pasic at linux.ibm.com> >>>> --- >>>> ? drivers/s390/virtio/virtio_ccw.c | 40 >&g...
2019 May 09
1
[PATCH 08/10] virtio/s390: add indirection to indicators access
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> >> --- >> ? drivers/s390/virtio/virtio_ccw.c | 40 >> +++++++++++++++++++++++++------------...
2019 May 08
2
[PATCH 09/10] virtio/s390: use DMA memory for ccw I/O and classic notifiers
.... > > 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 at linux.ibm.com> > --- > drivers/s390...
2019 May 08
2
[PATCH 09/10] virtio/s390: use DMA memory for ccw I/O and classic notifiers
.... > > 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 at linux.ibm.com> > --- > drivers/s390...
2013 Dec 13
0
[PATCH v4 RFC 1/3] virtio_ccw: fix vcdev pointer handling issues
...eue *vq; struct virtio_driver *drv; + if (!vcdev) + return; /* Check if it's a notification from the host. */ if ((intparm == 0) && (scsw_stctl(&irb->scsw) == @@ -985,23 +987,37 @@ static int virtio_ccw_probe(struct ccw_device *cdev) return 0; } +static struct virtio_ccw_device *virtio_grab_drvdata(struct ccw_device *cdev) +{ + unsigned long flags; + struct virtio_ccw_device *vcdev; + + spin_lock_irqsave(get_ccwdev_lock(cdev), flags); + vcdev = dev_get_drvdata(&cdev->dev); + if (!vcdev) { + spin_unlock_irqrestore(get_ccwdev_lock(cdev), flags); + return NULL; + }...
2019 May 10
2
[PATCH 08/10] virtio/s390: add indirection to indicators access
...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 virtualization guests). >>>>>> >>>>>> Signed-off-by: Halil Pasic <pasic at linux.ibm.com> >>>>>> --- >>>>>> ? dri...
2019 May 10
2
[PATCH 08/10] virtio/s390: add indirection to indicators access
...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 virtualization guests). >>>>>> >>>>>> Signed-off-by: Halil Pasic <pasic at linux.ibm.com> >>>>>> --- >>>>>> ? dri...
2019 Jun 03
2
[PATCH v3 7/8] virtio/s390: use DMA memory for ccw I/O and classic notifiers
.... > > 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 at linux.ibm.com> > Reviewed-by: Pierre Mor...
2019 Jun 03
2
[PATCH v3 7/8] virtio/s390: use DMA memory for ccw I/O and classic notifiers
.... > > 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 at linux.ibm.com> > Reviewed-by: Pierre Mor...
2020 May 26
3
[PATCH] s390/virtio: remove unused pm callbacks
...rtio_ccw.c index 957889a42d2e..5730572b52cd 100644 --- a/drivers/s390/virtio/virtio_ccw.c +++ b/drivers/s390/virtio/virtio_ccw.c @@ -1372,27 +1372,6 @@ static struct ccw_device_id virtio_ids[] = { {}, }; -#ifdef CONFIG_PM_SLEEP -static int virtio_ccw_freeze(struct ccw_device *cdev) -{ - struct virtio_ccw_device *vcdev = dev_get_drvdata(&cdev->dev); - - return virtio_device_freeze(&vcdev->vdev); -} - -static int virtio_ccw_restore(struct ccw_device *cdev) -{ - struct virtio_ccw_device *vcdev = dev_get_drvdata(&cdev->dev); - int ret; - - ret = virtio_ccw_set_transport_rev(vcdev); - if (...
2020 May 26
3
[PATCH] s390/virtio: remove unused pm callbacks
...rtio_ccw.c index 957889a42d2e..5730572b52cd 100644 --- a/drivers/s390/virtio/virtio_ccw.c +++ b/drivers/s390/virtio/virtio_ccw.c @@ -1372,27 +1372,6 @@ static struct ccw_device_id virtio_ids[] = { {}, }; -#ifdef CONFIG_PM_SLEEP -static int virtio_ccw_freeze(struct ccw_device *cdev) -{ - struct virtio_ccw_device *vcdev = dev_get_drvdata(&cdev->dev); - - return virtio_device_freeze(&vcdev->vdev); -} - -static int virtio_ccw_restore(struct ccw_device *cdev) -{ - struct virtio_ccw_device *vcdev = dev_get_drvdata(&cdev->dev); - int ret; - - ret = virtio_ccw_set_transport_rev(vcdev); - if (...