search for: mdev_parent_op

> From: Jason Wang > Sent: Thursday, September 12, 2019 5:40 PM > > Currently, except for the crate and remove. The rest fields of > mdev_parent_ops is just designed for vfio-mdev driver and may not help > for kernel mdev driver. So follow the device id support by previous > patch, this patch introduces device specific ops which points to > device specific ops (e.g vfio ops). This allows the future drivers > like virtio-mdev to imp...

> From: Jason Wang > Sent: Thursday, September 12, 2019 5:40 PM > > Currently, except for the crate and remove. The rest fields of > mdev_parent_ops is just designed for vfio-mdev driver and may not help > for kernel mdev driver. So follow the device id support by previous > patch, this patch introduces device specific ops which points to > device specific ops (e.g vfio ops). This allows the future drivers > like virtio-mdev to imp...

Hi all: During the development of virtio-mdev[1]. I find that mdev needs to be extended to support devices other than vfio mdev device. So this series tries to extend the mdev to be able to differ from different devices by: - device id and matching for mdev bus - device speicfic callbacks and move vfio callbacks there Sent for early reivew, compile test only! Thanks [1]

Hi all: During the development of virtio-mdev[1]. I find that mdev needs to be extended to support devices other than vfio mdev device. So this series tries to extend the mdev to be able to differ from different devices by: - device id and matching for mdev bus - device speicfic callbacks and move vfio callbacks there Sent for early reivew, compile test only! Thanks [1]

Currently, except for the crate and remove. The rest fields of mdev_parent_ops is just designed for vfio-mdev driver and may not help for kernel mdev driver. So follow the device id support by previous patch, this patch introduces device specific ops which points to device specific ops (e.g vfio ops). This allows the future drivers like virtio-mdev to implement its own devic...

On 2019/9/17 ??4:09, Tian, Kevin wrote: >> From: Jason Wang >> Sent: Thursday, September 12, 2019 5:40 PM >> >> Currently, except for the crate and remove. The rest fields of >> mdev_parent_ops is just designed for vfio-mdev driver and may not help >> for kernel mdev driver. So follow the device id support by previous >> patch, this patch introduces device specific ops which points to >> device specific ops (e.g vfio ops). This allows the future drivers >> like vi...

...hat.com] > Sent: Tuesday, September 17, 2019 6:17 PM > > On 2019/9/17 ??4:09, Tian, Kevin wrote: > >> From: Jason Wang > >> Sent: Thursday, September 12, 2019 5:40 PM > >> > >> Currently, except for the crate and remove. The rest fields of > >> mdev_parent_ops is just designed for vfio-mdev driver and may not > help > >> for kernel mdev driver. So follow the device id support by previous > >> patch, this patch introduces device specific ops which points to > >> device specific ops (e.g vfio ops). This allows the future driv...

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. Follow the class id support by previous patch, this patch introduces device specific ops pointer inside parent ops which points to device specific ops (e.g vfio ops). This allows the future drivers like virtio-mdev to i...

On Tue, 24 Sep 2019 21:53:29 +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 callback to be used by > vfio-mdev and virtio-mdev. > > Sign...

On Tue, 24 Sep 2019 21:53:29 +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 callback to be used by > vfio-mdev and virtio-mdev. > > Sign...

...th the core driver: > * Register:: > > extern int mdev_register_driver(struct mdev_driver *drv, > - struct module *owner); > + struct module *owner); > > * Unregister:: > > @@ -163,7 +165,8 @@ A driver should use the mdev_parent_ops structure in the function call to > register itself with the mdev core driver:: > > extern int mdev_register_device(struct device *dev, > - const struct mdev_parent_ops *ops); > + const struct mdev_parent_ops *o...

...x.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 remove. The rest of mdev_parent_ops is >> designed for vfio-mdev driver only and may not help for kernel mdev driver. >> Follow the class id support by previous patch, this patch introduces device >> specific ops pointer inside parent ops which points to device specific ops (e.g >> vfio ops). This allows the...

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 callback to be used by vfio-mdev and virtio-mdev. Signed-off-by: Jason Wang <jaso...

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 callback to be used by vfio-mdev and virtio-mdev. Signed-off-by: Jason Wang <jaso...

> From: Alex Williamson > Sent: Wednesday, September 25, 2019 7:07 AM > > On Tue, 24 Sep 2019 21:53:29 +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 callback to be used by > > vfio-mdev and virtio-m...

...118,7 @@ to register and unregister itself with the core driver: * Register:: extern int mdev_register_driver(struct mdev_driver *drv, - struct module *owner); + struct module *owner); * Unregister:: @@ -163,7 +165,8 @@ A driver should use the mdev_parent_ops structure in the function call to register itself with the mdev core driver:: extern int mdev_register_device(struct device *dev, - const struct mdev_parent_ops *ops); + const struct mdev_parent_ops *ops, +...

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 callback to be used by vfio-mdev and virtio-mdev. Signed-off-by: Jason Wang <jaso...

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 callback to be used by vfio-mdev and virtio-mdev. Reviewed-by: Parav Pandit <para...

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 callback to be used by vfio-mdev and virtio-mdev. Reviewed-by: Parav Pandit <para...

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 callback to be used by vfio-mdev and virtio-mdev. Reviewed-by: Parav Pandit <para...