| Message ID | 20190912094012.29653-1-jasowang@redhat.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | Mdev: support mutiple kinds of devices | expand |
[cc +Parav] On Thu, 12 Sep 2019 17:40:10 +0800 Jason Wang <jasowang@redhat.com> wrote: > 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] https://lkml.org/lkml/2019/9/10/135 I expect Parav must have something similar in the works for their in-kernel networking mdev support. Link to discussion so far: https://lore.kernel.org/kvm/20190912094012.29653-1-jasowang@redhat.com/T/#t Thanks, Alex > Jason Wang (2): > mdev: device id support > mdev: introduce device specific ops > > drivers/gpu/drm/i915/gvt/kvmgt.c | 16 ++++--- > drivers/s390/cio/vfio_ccw_ops.c | 16 ++++--- > drivers/s390/crypto/vfio_ap_ops.c | 13 ++++-- > drivers/vfio/mdev/mdev_core.c | 14 +++++- > drivers/vfio/mdev/mdev_driver.c | 14 ++++++ > drivers/vfio/mdev/mdev_private.h | 1 + > drivers/vfio/mdev/vfio_mdev.c | 36 ++++++++++----- > include/linux/mdev.h | 76 +++++++++++++++++++------------ > include/linux/mod_devicetable.h | 6 +++ > samples/vfio-mdev/mbochs.c | 18 +++++--- > samples/vfio-mdev/mdpy.c | 18 +++++--- > samples/vfio-mdev/mtty.c | 16 ++++--- > 12 files changed, 163 insertions(+), 81 deletions(-) >
> From: Alex Williamson > Sent: Wednesday, September 18, 2019 1:31 AM > > [cc +Parav] > > On Thu, 12 Sep 2019 17:40:10 +0800 > Jason Wang <jasowang@redhat.com> wrote: > > > 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] https://lkml.org/lkml/2019/9/10/135 > > I expect Parav must have something similar in the works for their > in-kernel networking mdev support. Link to discussion so far: > > https://lore.kernel.org/kvm/20190912094012.29653-1- > jasowang@redhat.com/T/#t > It links to the current thread. Is it intended or do you want people to look at another thread driven by Parav? :-) Thanks Kevin
On Wed, 18 Sep 2019 01:54:43 +0000 "Tian, Kevin" <kevin.tian@intel.com> wrote: > > From: Alex Williamson > > Sent: Wednesday, September 18, 2019 1:31 AM > > > > [cc +Parav] > > > > On Thu, 12 Sep 2019 17:40:10 +0800 > > Jason Wang <jasowang@redhat.com> wrote: > > > > > 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] https://lkml.org/lkml/2019/9/10/135 > > > > I expect Parav must have something similar in the works for their > > in-kernel networking mdev support. Link to discussion so far: > > > > https://lore.kernel.org/kvm/20190912094012.29653-1- > > jasowang@redhat.com/T/#t > > > > It links to the current thread. Is it intended or do you want > people to look at another thread driven by Parav? :-) Sorry, the link was provided for Parav since they weren't cc'd. Thanks, Alex