search for: virtio_vdpa_prob

...type) can not work on > vdpa_device.dev. Then it seems device drivers need to implement a wrap > of dma_ops of parent devices. Can this work be done in the vdpa > framework since it looks like a common task? Can > "vd_dev->vdev.dev.parent = vdpa->dev->parent;" in virtio_vdpa_probe() > do the work? > > Thanks, > BR > Zhu Lingshan Good catch. I think we can. Thanks

...type) can not work on > vdpa_device.dev. Then it seems device drivers need to implement a wrap > of dma_ops of parent devices. Can this work be done in the vdpa > framework since it looks like a common task? Can > "vd_dev->vdev.dev.parent = vdpa->dev->parent;" in virtio_vdpa_probe() > do the work? > > Thanks, > BR > Zhu Lingshan Good catch. I think we can. Thanks

...dpa_bus_name, +}; + +static void virtio_vdpa_release_dev(struct device *_d) +{ + struct virtio_device *vdev = + container_of(_d, struct virtio_device, dev); + struct virtio_vdpa_device *vd_dev = + container_of(vdev, struct virtio_vdpa_device, vdev); + + kfree(vd_dev); +} + +static int virtio_vdpa_probe(struct vdpa_device *vdpa) +{ + const struct vdpa_config_ops *ops = vdpa->config; + struct virtio_vdpa_device *vd_dev; + int ret = -EINVAL; + + vd_dev = kzalloc(sizeof(*vd_dev), GFP_KERNEL); + if (!vd_dev) + return -ENOMEM; + + vd_dev->vdev.dev.parent = vdpa_get_dma_dev(vdpa); + vd_dev->v...

...dpa_bus_name, +}; + +static void virtio_vdpa_release_dev(struct device *_d) +{ + struct virtio_device *vdev = + container_of(_d, struct virtio_device, dev); + struct virtio_vdpa_device *vd_dev = + container_of(vdev, struct virtio_vdpa_device, vdev); + + kfree(vd_dev); +} + +static int virtio_vdpa_probe(struct vdpa_device *vdpa) +{ + const struct vdpa_config_ops *ops = vdpa->config; + struct virtio_vdpa_device *vd_dev; + int ret = -EINVAL; + + vd_dev = kzalloc(sizeof(*vd_dev), GFP_KERNEL); + if (!vd_dev) + return -ENOMEM; + + vd_dev->vdev.dev.parent = vdpa_get_dma_dev(vdpa); + vd_dev->v...

...ork on vdpa_device.dev. Then > > it seems device drivers need to implement a wrap of dma_ops of parent > > devices. Can this work be done in the vdpa framework since it looks like > > a common task? Can "vd_dev->vdev.dev.parent = vdpa->dev->parent;" in > > virtio_vdpa_probe() do the work? > > > > Thanks, > > BR > > Zhu Lingshan > > > Good catch. > > I think we can. IMHO you need to specify some 'dma_device', not try and play tricks with dma_ops, or assuming the parent is always the device used for dma. Jason

...; diff --git a/drivers/virtio/virtio_vdpa.c b/drivers/virtio/virtio_vdpa.c > index c30eb55..1e8acb9 100644 > --- a/drivers/virtio/virtio_vdpa.c > +++ b/drivers/virtio/virtio_vdpa.c > @@ -386,6 +386,8 @@ static void virtio_vdpa_remove(struct vdpa_device *vdpa) > }, > .probe = virtio_vdpa_probe, > .remove = virtio_vdpa_remove, > + .setup_vq_irq = NULL, > + .unsetup_vq_irq = NULL, > }; Is this really needed consider the it's static? Thanks > > module_vdpa_driver(virtio_vdpa_driver);

...a.c >>> index c30eb55..1e8acb9 100644 >>> --- a/drivers/virtio/virtio_vdpa.c >>> +++ b/drivers/virtio/virtio_vdpa.c >>> @@ -386,6 +386,8 @@ static void virtio_vdpa_remove(struct >>> vdpa_device *vdpa) >>> ????? }, >>> ????? .probe??? = virtio_vdpa_probe, >>> ????? .remove = virtio_vdpa_remove, >>> +??? .setup_vq_irq = NULL, >>> +??? .unsetup_vq_irq = NULL, >>> ? }; >> >> >> Is this really needed consider the it's static? >> >> Thanks > This is for readability, to show they a...

Hi all: This is an update version of vDPA support in kernel. vDPA device is a device that uses a datapath which complies with the virtio specifications with vendor specific control path. vDPA devices can be both physically located on the hardware or emulated by software. vDPA hardware devices are usually implemented through PCIE with the following types: - PF (Physical Function) - A single

Hi all: This is an update version of vDPA support in kernel. vDPA device is a device that uses a datapath which complies with the virtio specifications with vendor specific control path. vDPA devices can be both physically located on the hardware or emulated by software. vDPA hardware devices are usually implemented through PCIE with the following types: - PF (Physical Function) - A single

Hi all: This is an updated version of kernel support for vDPA device. Various changes were made based on the feedback since last verion. One major change is to drop the sysfs API and leave the management interface for future development, and introudce the incremental DMA bus operations. Please see changelog for more information. The work on vhost, IFCVF (intel VF driver for vDPA) and qemu is