search for: shamay

...t; > farman at linux.ibm.com; pasic at linux.ibm.com; sebott at linux.ibm.com; > > oberpar at linux.ibm.com; heiko.carstens at de.ibm.com; gor at linux.ibm.com; > > borntraeger at de.ibm.com; akrowiak at linux.ibm.com; freude at linux.ibm.com; > > lingshan.zhu at intel.com; Ido Shamay <idos at mellanox.com>; > > eperezma at redhat.com; lulu at redhat.com; christophe.de.dinechin at gmail.com; > > kevin.tian at intel.com > > Subject: Re: [PATCH V3 4/7] mdev: introduce device specific ops > > > > On Wed, 16 Oct 2019 05:50:08 +0000 > > Para...

...arman at linux.ibm.com; pasic at linux.ibm.com; sebott at linux.ibm.com; >>> oberpar at linux.ibm.com; heiko.carstens at de.ibm.com; gor at linux.ibm.com; >>> borntraeger at de.ibm.com; akrowiak at linux.ibm.com; freude at linux.ibm.com; >>> lingshan.zhu at intel.com; Ido Shamay <idos at mellanox.com>; >>> eperezma at redhat.com; lulu at redhat.com; christophe.de.dinechin at gmail.com; >>> kevin.tian at intel.com >>> Subject: Re: [PATCH V3 4/7] mdev: introduce device specific ops >>> >>> On Wed, 16 Oct 2019 05:50:08 +0000...

...arman at linux.ibm.com; pasic at linux.ibm.com; sebott at linux.ibm.com; >>> oberpar at linux.ibm.com; heiko.carstens at de.ibm.com; gor at linux.ibm.com; >>> borntraeger at de.ibm.com; akrowiak at linux.ibm.com; freude at linux.ibm.com; >>> lingshan.zhu at intel.com; Ido Shamay <idos at mellanox.com>; >>> eperezma at redhat.com; lulu at redhat.com; christophe.de.dinechin at gmail.com; >>> kevin.tian at intel.com >>> Subject: Re: [PATCH V3 4/7] mdev: introduce device specific ops >>> >>> On Wed, 16 Oct 2019 05:50:08 +0000...

...; >> farman at linux.ibm.com; pasic at linux.ibm.com; sebott at linux.ibm.com; >> oberpar at linux.ibm.com; heiko.carstens at de.ibm.com; gor at linux.ibm.com; >> borntraeger at de.ibm.com; akrowiak at linux.ibm.com; freude at linux.ibm.com; >> lingshan.zhu at intel.com; Ido Shamay <idos at mellanox.com>; >> eperezma at redhat.com; lulu at redhat.com; Parav Pandit >> <parav at mellanox.com>; christophe.de.dinechin at gmail.com; >> kevin.tian at intel.com; stefanha at redhat.com; Jason Wang >> <jasowang at redhat.com> >> Subject:...

...; >> farman at linux.ibm.com; pasic at linux.ibm.com; sebott at linux.ibm.com; >> oberpar at linux.ibm.com; heiko.carstens at de.ibm.com; gor at linux.ibm.com; >> borntraeger at de.ibm.com; akrowiak at linux.ibm.com; freude at linux.ibm.com; >> lingshan.zhu at intel.com; Ido Shamay <idos at mellanox.com>; >> eperezma at redhat.com; lulu at redhat.com; Parav Pandit >> <parav at mellanox.com>; Jason Wang <jasowang at redhat.com> >> Subject: [PATCH 1/6] mdev: class id support >> >> Mdev bus only supports vfio driver right now, so i...

...t; > farman at linux.ibm.com; pasic at linux.ibm.com; sebott at linux.ibm.com; > > oberpar at linux.ibm.com; heiko.carstens at de.ibm.com; gor at linux.ibm.com; > > borntraeger at de.ibm.com; akrowiak at linux.ibm.com; freude at linux.ibm.com; > > lingshan.zhu at intel.com; Ido Shamay <idos at mellanox.com>; > > eperezma at redhat.com; lulu at redhat.com; Parav Pandit > > <parav at mellanox.com>; christophe.de.dinechin at gmail.com; > > kevin.tian at intel.com > > Subject: Re: [PATCH V2 6/8] mdev: introduce virtio device and its device ops &gt...

On Fri, 11 Oct 2019 16:15:54 +0800 Jason Wang <jasowang at redhat.com> wrote: > Currently, except for the create and remove, the rest of > mdev_parent_ops is designed for vfio-mdev driver only and may not help > for kernel mdev driver. With the help of class id, this patch > introduces device specific callbacks inside mdev_device > structure. This allows different set of

On Fri, 11 Oct 2019 16:15:54 +0800 Jason Wang <jasowang at redhat.com> wrote: > Currently, except for the create and remove, the rest of > mdev_parent_ops is designed for vfio-mdev driver only and may not help > for kernel mdev driver. With the help of class id, this patch > introduces device specific callbacks inside mdev_device > structure. This allows different set of

...t; > farman at linux.ibm.com; pasic at linux.ibm.com; sebott at linux.ibm.com; > > oberpar at linux.ibm.com; heiko.carstens at de.ibm.com; gor at linux.ibm.com; > > borntraeger at de.ibm.com; akrowiak at linux.ibm.com; freude at linux.ibm.com; > > lingshan.zhu at intel.com; Ido Shamay <idos at mellanox.com>; > > eperezma at redhat.com; lulu at redhat.com; Parav Pandit > > <parav at mellanox.com>; christophe.de.dinechin at gmail.com; > > kevin.tian at intel.com > > Subject: Re: [PATCH V3 4/7] mdev: introduce device specific ops > > >...

...; >> farman at linux.ibm.com; pasic at linux.ibm.com; sebott at linux.ibm.com; >> oberpar at linux.ibm.com; heiko.carstens at de.ibm.com; gor at linux.ibm.com; >> borntraeger at de.ibm.com; akrowiak at linux.ibm.com; freude at linux.ibm.com; >> lingshan.zhu at intel.com; Ido Shamay <idos at mellanox.com>; >> eperezma at redhat.com; lulu at redhat.com; Parav Pandit >> <parav at mellanox.com>; christophe.de.dinechin at gmail.com; >> kevin.tian at intel.com; Jason Wang <jasowang at redhat.com> >> Subject: [PATCH V3 1/7] mdev: class id su...

...; >> farman at linux.ibm.com; pasic at linux.ibm.com; sebott at linux.ibm.com; >> oberpar at linux.ibm.com; heiko.carstens at de.ibm.com; gor at linux.ibm.com; >> borntraeger at de.ibm.com; akrowiak at linux.ibm.com; freude at linux.ibm.com; >> lingshan.zhu at intel.com; Ido Shamay <idos at mellanox.com>; >> eperezma at redhat.com; lulu at redhat.com; Parav Pandit >> <parav at mellanox.com>; Jason Wang <jasowang at redhat.com> >> Subject: [PATCH 1/6] mdev: class id support >> >> Mdev bus only supports vfio driver right now, so i...

...; >> farman at linux.ibm.com; pasic at linux.ibm.com; sebott at linux.ibm.com; >> oberpar at linux.ibm.com; heiko.carstens at de.ibm.com; gor at linux.ibm.com; >> borntraeger at de.ibm.com; akrowiak at linux.ibm.com; freude at linux.ibm.com; >> lingshan.zhu at intel.com; Ido Shamay <idos at mellanox.com>; >> eperezma at redhat.com; lulu at redhat.com; Parav Pandit >> <parav at mellanox.com>; Jason Wang <jasowang at redhat.com> >> Subject: [PATCH 4/6] virtio: introduce a mdev based transport >> >> This patch introduces a new mdev...

...; >> farman at linux.ibm.com; pasic at linux.ibm.com; sebott at linux.ibm.com; >> oberpar at linux.ibm.com; heiko.carstens at de.ibm.com; gor at linux.ibm.com; >> borntraeger at de.ibm.com; akrowiak at linux.ibm.com; freude at linux.ibm.com; >> lingshan.zhu at intel.com; Ido Shamay <idos at mellanox.com>; >> eperezma at redhat.com; lulu at redhat.com; Parav Pandit >> <parav at mellanox.com>; Jason Wang <jasowang at redhat.com> >> Subject: [PATCH 2/6] mdev: introduce device specific ops >> >> Currently, except for the create and...

...; >> farman at linux.ibm.com; pasic at linux.ibm.com; sebott at linux.ibm.com; >> oberpar at linux.ibm.com; heiko.carstens at de.ibm.com; gor at linux.ibm.com; >> borntraeger at de.ibm.com; akrowiak at linux.ibm.com; freude at linux.ibm.com; >> lingshan.zhu at intel.com; Ido Shamay <idos at mellanox.com>; >> eperezma at redhat.com; lulu at redhat.com; Parav Pandit >> <parav at mellanox.com>; christophe.de.dinechin at gmail.com; >> kevin.tian at intel.com; stefanha at redhat.com; Jason Wang >> <jasowang at redhat.com> >> Subject:...

Hi all: There are hardware that can do virtio datapath offloading while having its own control path. This path tries to implement a mdev based unified API to support using kernel virtio driver to drive those devices. This is done by introducing a new mdev transport for virtio (virtio_mdev) and register itself as a new kind of mdev driver. Then it provides a unified way for kernel virtio driver to

Hi all: There are hardware that can do virtio datapath offloading while having its own control path. This path tries to implement a mdev based unified API to support using kernel virtio driver to drive those devices. This is done by introducing a new mdev transport for virtio (virtio_mdev) and register itself as a new kind of mdev driver. Then it provides a unified way for kernel virtio driver to

Hi all: There are hardware that can do virtio datapath offloading while having its own control path. This path tries to implement a mdev based unified API to support using kernel virtio driver to drive those devices. This is done by introducing a new mdev transport for virtio (virtio_mdev) and register itself as a new kind of mdev driver. Then it provides a unified way for kernel virtio driver to

Hi all: There are hardware that can do virtio datapath offloading while having its own control path. This path tries to implement a mdev based unified API to support using kernel virtio driver to drive those devices. This is done by introducing a new mdev transport for virtio (virtio_mdev) and register itself as a new kind of mdev driver. Then it provides a unified way for kernel virtio driver to

Hi all: There are hardwares that can do virtio datapath offloading while having its own control path. This path tries to implement a mdev based unified API to support using kernel virtio driver to drive those devices. This is done by introducing a new mdev transport for virtio (virtio_mdev) and register itself as a new kind of mdev driver. Then it provides a unified way for kernel virtio driver

Hi all: There are hardware that can do virtio datapath offloading while having its own control path. This path tries to implement a mdev based unified API to support using kernel virtio driver to drive those devices. This is done by introducing a new mdev transport for virtio (virtio_mdev) and register itself as a new kind of mdev driver. Then it provides a unified way for kernel virtio driver to