search for: 298581e7ad45

Displaying 3 results from an estimated 3 matches for "298581e7ad45".

2019 Oct 11
0
[PATCH V3 5/7] mdev: introduce virtio device and its device ops
...sowang at redhat.com> --- include/linux/mdev.h | 1 + include/linux/virtio_mdev.h | 148 ++++++++++++++++++++++++++++++++++++ 2 files changed, 149 insertions(+) create mode 100644 include/linux/virtio_mdev.h diff --git a/include/linux/mdev.h b/include/linux/mdev.h index f491308674e5..298581e7ad45 100644 --- a/include/linux/mdev.h +++ b/include/linux/mdev.h @@ -124,6 +124,7 @@ struct mdev_device *mdev_from_dev(struct device *dev); enum { MDEV_ID_VFIO = 1, + MDEV_ID_VIRTIO = 2, /* New entries must be added here */ }; diff --git a/include/linux/virtio_mdev.h b/include/linux/virtio_md...
2019 Oct 11
17
[PATCH V3 0/7] mdev based hardware virtio offloading support
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
2019 Oct 11
17
[PATCH V3 0/7] mdev based hardware virtio offloading support
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