search for: 3907c5371c2b

...f callback to be used by vfio- >> mdev and virtio-mdev. >> >> Signed-off-by: Jason Wang <jasowang at redhat.com> >> --- > [ ..] > >> diff --git a/include/linux/vfio_mdev_ops.h b/include/linux/vfio_mdev_ops.h >> new file mode 100644 index 000000000000..3907c5371c2b >> --- /dev/null >> +++ b/include/linux/vfio_mdev_ops.h >> @@ -0,0 +1,52 @@ >> +/* SPDX-License-Identifier: GPL-2.0-only */ >> +/* >> + * VFIO Mediated device definition >> + */ >> + >> +#ifndef VFIO_MDEV_H >> +#define VFIO_MDEV_H >>...

..._ops(struct mdev_device *mdev, const void *ops); > void mdev_set_class_id(struct mdev_device *mdev, u16 id); > const guid_t *mdev_uuid(struct mdev_device *mdev); > > diff --git a/include/linux/vfio_mdev.h b/include/linux/vfio_mdev.h > new file mode 100644 > index 000000000000..3907c5371c2b > --- /dev/null > +++ b/include/linux/vfio_mdev.h > @@ -0,0 +1,52 @@ > +/* SPDX-License-Identifier: GPL-2.0-only */ > +/* > + * VFIO Mediated device definition > + */ > + > +#ifndef VFIO_MDEV_H > +#define VFIO_MDEV_H > + > +#include <linux/mdev.h> > + &g...

..._ops(struct mdev_device *mdev, const void *ops); > void mdev_set_class_id(struct mdev_device *mdev, u16 id); > const guid_t *mdev_uuid(struct mdev_device *mdev); > > diff --git a/include/linux/vfio_mdev.h b/include/linux/vfio_mdev.h > new file mode 100644 > index 000000000000..3907c5371c2b > --- /dev/null > +++ b/include/linux/vfio_mdev.h > @@ -0,0 +1,52 @@ > +/* SPDX-License-Identifier: GPL-2.0-only */ > +/* > + * VFIO Mediated device definition > + */ > + > +#ifndef VFIO_MDEV_H > +#define VFIO_MDEV_H > + > +#include <linux/mdev.h> > + &g...

...ice *mdev); +void mdev_set_dev_ops(struct mdev_device *mdev, const void *ops); void mdev_set_class_id(struct mdev_device *mdev, u16 id); const guid_t *mdev_uuid(struct mdev_device *mdev); diff --git a/include/linux/vfio_mdev.h b/include/linux/vfio_mdev.h new file mode 100644 index 000000000000..3907c5371c2b --- /dev/null +++ b/include/linux/vfio_mdev.h @@ -0,0 +1,52 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +/* + * VFIO Mediated device definition + */ + +#ifndef VFIO_MDEV_H +#define VFIO_MDEV_H + +#include <linux/mdev.h> + +/** + * struct vfio_mdev_device_ops - Structure to be registered f...

...v_device *mdev, u16 id, const void *ops); +const void *mdev_get_dev_ops(struct mdev_device *mdev); const guid_t *mdev_uuid(struct mdev_device *mdev); extern struct bus_type mdev_bus_type; diff --git a/include/linux/vfio_mdev.h b/include/linux/vfio_mdev.h new file mode 100644 index 000000000000..3907c5371c2b --- /dev/null +++ b/include/linux/vfio_mdev.h @@ -0,0 +1,52 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +/* + * VFIO Mediated device definition + */ + +#ifndef VFIO_MDEV_H +#define VFIO_MDEV_H + +#include <linux/mdev.h> + +/** + * struct vfio_mdev_device_ops - Structure to be registered f...

...v, const void *ops); > > void mdev_set_class_id(struct mdev_device *mdev, u16 id); > > const guid_t *mdev_uuid(struct mdev_device *mdev); > > > > diff --git a/include/linux/vfio_mdev.h b/include/linux/vfio_mdev.h > > new file mode 100644 > > index 000000000000..3907c5371c2b > > --- /dev/null > > +++ b/include/linux/vfio_mdev.h > > @@ -0,0 +1,52 @@ > > +/* SPDX-License-Identifier: GPL-2.0-only */ > > +/* > > + * VFIO Mediated device definition > > + */ > > + > > +#ifndef VFIO_MDEV_H > > +#define VFIO_MDEV_H &g...

..._vfio_ops(struct mdev_device *mdev, + const struct vfio_mdev_device_ops *vfio_ops); +const void *mdev_get_dev_ops(struct mdev_device *mdev); extern struct bus_type mdev_bus_type; diff --git a/include/linux/vfio_mdev.h b/include/linux/vfio_mdev.h new file mode 100644 index 000000000000..3907c5371c2b --- /dev/null +++ b/include/linux/vfio_mdev.h @@ -0,0 +1,52 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +/* + * VFIO Mediated device definition + */ + +#ifndef VFIO_MDEV_H +#define VFIO_MDEV_H + +#include <linux/mdev.h> + +/** + * struct vfio_mdev_device_ops - Structure to be registered f...

...> Since you have the set_vfio_ops, its better to have get_vfio_ops() and similarly get_virtio_ops. Ok. > >> extern struct bus_type mdev_bus_type; >> >> diff --git a/include/linux/vfio_mdev.h b/include/linux/vfio_mdev.h new file >> mode 100644 index 000000000000..3907c5371c2b >> --- /dev/null >> +++ b/include/linux/vfio_mdev.h > This file name is confusing. > vfio_mdev_ops.h is more accurate name of what it intends to achieve. > If you see this file expanding scope beyond ops, this file name looks fine. > >> @@ -0,0 +1,52 @@ >> +/* SP...

...> void mdev_set_class_id(struct mdev_device *mdev, u16 id); > > > const guid_t *mdev_uuid(struct mdev_device *mdev); > > > > > > diff --git a/include/linux/vfio_mdev.h b/include/linux/vfio_mdev.h > > > new file mode 100644 > > > index 000000000000..3907c5371c2b > > > --- /dev/null > > > +++ b/include/linux/vfio_mdev.h > > > @@ -0,0 +1,52 @@ > > > +/* SPDX-License-Identifier: GPL-2.0-only */ > > > +/* > > > + * VFIO Mediated device definition > > > + */ > > > + > > > +#ifndef...

...> void mdev_set_class_id(struct mdev_device *mdev, u16 id); > > > const guid_t *mdev_uuid(struct mdev_device *mdev); > > > > > > diff --git a/include/linux/vfio_mdev.h b/include/linux/vfio_mdev.h > > > new file mode 100644 > > > index 000000000000..3907c5371c2b > > > --- /dev/null > > > +++ b/include/linux/vfio_mdev.h > > > @@ -0,0 +1,52 @@ > > > +/* SPDX-License-Identifier: GPL-2.0-only */ > > > +/* > > > + * VFIO Mediated device definition > > > + */ > > > + > > > +#ifndef...

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

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

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

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