search for: mdev_vfio_ops_h

...gt;> +#ifndef VFIO_MDEV_H >> +#define VFIO_MDEV_H >> + > I should have noticed this before. :-( > APIs exposed are by the mdev module and named with mdev_ prefix. > And file name is _ops.h, > > We should name this file as mdev_vfio_ops.h > > And #define should be MDEV_VFIO_OPS_H > >> +#include <linux/mdev.h> >> + >> +/** >> + * struct vfio_mdev_device_ops - Structure to be registered for each > s/vfio_mdev_device_ops/mdev_vfio_device_ops/ > > Similarly for virtio in future patches. > Will fix in V7. > static void mtty_de...

...diff --git a/include/linux/mdev_vfio_ops.h b/include/linux/mdev_vfio_ops.h new file mode 100644 index 000000000000..317518f30621 --- /dev/null +++ b/include/linux/mdev_vfio_ops.h @@ -0,0 +1,52 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +/* + * VFIO Mediated device definition + */ + +#ifndef MDEV_VFIO_OPS_H +#define MDEV_VFIO_OPS_H + +#include <linux/mdev.h> + +/** + * struct mdev_vfio_device_ops - Structure to be registered for each + * mdev device to register the device to vfio-mdev module. + * + * @open: Open mediated device. + * @mdev: mediated device. + * Returns integer: success (0) o...

...diff --git a/include/linux/mdev_vfio_ops.h b/include/linux/mdev_vfio_ops.h new file mode 100644 index 000000000000..317518f30621 --- /dev/null +++ b/include/linux/mdev_vfio_ops.h @@ -0,0 +1,52 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +/* + * VFIO Mediated device definition + */ + +#ifndef MDEV_VFIO_OPS_H +#define MDEV_VFIO_OPS_H + +#include <linux/mdev.h> + +/** + * struct mdev_vfio_device_ops - Structure to be registered for each + * mdev device to register the device to vfio-mdev module. + * + * @open: Open mediated device. + * @mdev: mediated device. + * Returns integer: success (0) o...

...diff --git a/include/linux/mdev_vfio_ops.h b/include/linux/mdev_vfio_ops.h new file mode 100644 index 000000000000..317518f30621 --- /dev/null +++ b/include/linux/mdev_vfio_ops.h @@ -0,0 +1,52 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +/* + * VFIO Mediated device definition + */ + +#ifndef MDEV_VFIO_OPS_H +#define MDEV_VFIO_OPS_H + +#include <linux/mdev.h> + +/** + * struct mdev_vfio_device_ops - Structure to be registered for each + * mdev device to register the device to vfio-mdev module. + * + * @open: Open mediated device. + * @mdev: mediated device. + * Returns integer: success (0) o...

...diff --git a/include/linux/mdev_vfio_ops.h b/include/linux/mdev_vfio_ops.h new file mode 100644 index 000000000000..317518f30621 --- /dev/null +++ b/include/linux/mdev_vfio_ops.h @@ -0,0 +1,52 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +/* + * VFIO Mediated device definition + */ + +#ifndef MDEV_VFIO_OPS_H +#define MDEV_VFIO_OPS_H + +#include <linux/mdev.h> + +/** + * struct mdev_vfio_device_ops - Structure to be registered for each + * mdev device to register the device to vfio-mdev module. + * + * @open: Open mediated device. + * @mdev: mediated device. + * Returns integer: success (0) o...

.../linux/mdev_vfio_ops.h > new file mode 100644 > index 000000000000..317518f30621 > --- /dev/null > +++ b/include/linux/mdev_vfio_ops.h > @@ -0,0 +1,52 @@ > +/* SPDX-License-Identifier: GPL-2.0-only */ > +/* > + * VFIO Mediated device definition > + */ > + > +#ifndef MDEV_VFIO_OPS_H > +#define MDEV_VFIO_OPS_H > + > +#include <linux/mdev.h> > + > +/** > + * struct mdev_vfio_device_ops - Structure to be registered for each > + * mdev device to register the device to vfio-mdev module. > + * > + * @open: Open mediated device. > + * @mdev: med...

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 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 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 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 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 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 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