search for: 891cf83a2d9a

Displaying 15 results from an estimated 15 matches for "891cf83a2d9a".

2019 Sep 26
2
[PATCH V2 5/8] mdev: introduce device specific ops
...adcom.com> wrote: > > > > On Tue, 24 Sep 2019 21:53:29 +0800 > > > > Jason Wang <jasowang at redhat.com> wrote: > > > > > diff --git a/drivers/vfio/mdev/vfio_mdev.c > > > > b/drivers/vfio/mdev/vfio_mdev.c > > > > > index 891cf83a2d9a..95efa054442f 100644 > > > > > --- a/drivers/vfio/mdev/vfio_mdev.c > > > > > +++ b/drivers/vfio/mdev/vfio_mdev.c > > > > > @@ -14,6 +14,7 @@ > > > > > #include <linux/slab.h> > > > > > #include <linux/vfio.h> &...
2019 Sep 26
2
[PATCH V2 5/8] mdev: introduce device specific ops
...adcom.com> wrote: > > > > On Tue, 24 Sep 2019 21:53:29 +0800 > > > > Jason Wang <jasowang at redhat.com> wrote: > > > > > diff --git a/drivers/vfio/mdev/vfio_mdev.c > > > > b/drivers/vfio/mdev/vfio_mdev.c > > > > > index 891cf83a2d9a..95efa054442f 100644 > > > > > --- a/drivers/vfio/mdev/vfio_mdev.c > > > > > +++ b/drivers/vfio/mdev/vfio_mdev.c > > > > > @@ -14,6 +14,7 @@ > > > > > #include <linux/slab.h> > > > > > #include <linux/vfio.h> &...
2019 Sep 25
0
[PATCH V2 5/8] mdev: introduce device specific ops
...ler <rob.miller at broadcom.com> wrote: > > > On Tue, 24 Sep 2019 21:53:29 +0800 > > > Jason Wang <jasowang at redhat.com> wrote: > > > > diff --git a/drivers/vfio/mdev/vfio_mdev.c > > > b/drivers/vfio/mdev/vfio_mdev.c > > > > index 891cf83a2d9a..95efa054442f 100644 > > > > --- a/drivers/vfio/mdev/vfio_mdev.c > > > > +++ b/drivers/vfio/mdev/vfio_mdev.c > > > > @@ -14,6 +14,7 @@ > > > > #include <linux/slab.h> > > > > #include <linux/vfio.h> > > > > #incl...
2019 Sep 26
0
[PATCH V2 5/8] mdev: introduce device specific ops
...> > > On Tue, 24 Sep 2019 21:53:29 +0800 > > > > > Jason Wang <jasowang at redhat.com> wrote: > > > > > > diff --git a/drivers/vfio/mdev/vfio_mdev.c > > > > > b/drivers/vfio/mdev/vfio_mdev.c > > > > > > index 891cf83a2d9a..95efa054442f 100644 > > > > > > --- a/drivers/vfio/mdev/vfio_mdev.c > > > > > > +++ b/drivers/vfio/mdev/vfio_mdev.c > > > > > > @@ -14,6 +14,7 @@ > > > > > > #include <linux/slab.h> > > > > > > #inclu...
2019 Sep 25
3
[PATCH V2 5/8] mdev: introduce device specific ops
...t; > > + const void *device_ops; > > > }; > > > > > > #define to_mdev_device(dev) container_of(dev, struct > > mdev_device, dev) > > > diff --git a/drivers/vfio/mdev/vfio_mdev.c > > b/drivers/vfio/mdev/vfio_mdev.c > > > index 891cf83a2d9a..95efa054442f 100644 > > > --- a/drivers/vfio/mdev/vfio_mdev.c > > > +++ b/drivers/vfio/mdev/vfio_mdev.c > > > @@ -14,6 +14,7 @@ > > > #include <linux/slab.h> > > > #include <linux/vfio.h> > > > #include <linux/mdev.h> >...
2019 Sep 25
3
[PATCH V2 5/8] mdev: introduce device specific ops
...t; > > + const void *device_ops; > > > }; > > > > > > #define to_mdev_device(dev) container_of(dev, struct > > mdev_device, dev) > > > diff --git a/drivers/vfio/mdev/vfio_mdev.c > > b/drivers/vfio/mdev/vfio_mdev.c > > > index 891cf83a2d9a..95efa054442f 100644 > > > --- a/drivers/vfio/mdev/vfio_mdev.c > > > +++ b/drivers/vfio/mdev/vfio_mdev.c > > > @@ -14,6 +14,7 @@ > > > #include <linux/slab.h> > > > #include <linux/vfio.h> > > > #include <linux/mdev.h> >...
2019 Sep 24
3
[PATCH V2 5/8] mdev: introduce device specific ops
...evice { > struct device *iommu_device; > bool active; > u16 class_id; > + const void *device_ops; > }; > > #define to_mdev_device(dev) container_of(dev, struct mdev_device, dev) > diff --git a/drivers/vfio/mdev/vfio_mdev.c b/drivers/vfio/mdev/vfio_mdev.c > index 891cf83a2d9a..95efa054442f 100644 > --- a/drivers/vfio/mdev/vfio_mdev.c > +++ b/drivers/vfio/mdev/vfio_mdev.c > @@ -14,6 +14,7 @@ > #include <linux/slab.h> > #include <linux/vfio.h> > #include <linux/mdev.h> > +#include <linux/vfio_mdev.h> > > #include &q...
2019 Sep 24
3
[PATCH V2 5/8] mdev: introduce device specific ops
...evice { > struct device *iommu_device; > bool active; > u16 class_id; > + const void *device_ops; > }; > > #define to_mdev_device(dev) container_of(dev, struct mdev_device, dev) > diff --git a/drivers/vfio/mdev/vfio_mdev.c b/drivers/vfio/mdev/vfio_mdev.c > index 891cf83a2d9a..95efa054442f 100644 > --- a/drivers/vfio/mdev/vfio_mdev.c > +++ b/drivers/vfio/mdev/vfio_mdev.c > @@ -14,6 +14,7 @@ > #include <linux/slab.h> > #include <linux/vfio.h> > #include <linux/mdev.h> > +#include <linux/vfio_mdev.h> > > #include &q...
2019 Sep 24
0
[PATCH V2 5/8] mdev: introduce device specific ops
...dev_private.h @@ -34,6 +34,7 @@ struct mdev_device { struct device *iommu_device; bool active; u16 class_id; + const void *device_ops; }; #define to_mdev_device(dev) container_of(dev, struct mdev_device, dev) diff --git a/drivers/vfio/mdev/vfio_mdev.c b/drivers/vfio/mdev/vfio_mdev.c index 891cf83a2d9a..95efa054442f 100644 --- a/drivers/vfio/mdev/vfio_mdev.c +++ b/drivers/vfio/mdev/vfio_mdev.c @@ -14,6 +14,7 @@ #include <linux/slab.h> #include <linux/vfio.h> #include <linux/mdev.h> +#include <linux/vfio_mdev.h> #include "mdev_private.h" @@ -24,16 +25,16 @...
2019 Oct 11
0
[PATCH V3 4/7] mdev: introduce device specific ops
...dev_private.h @@ -34,6 +34,7 @@ struct mdev_device { struct device *iommu_device; bool active; u16 class_id; + const void *device_ops; }; #define to_mdev_device(dev) container_of(dev, struct mdev_device, dev) diff --git a/drivers/vfio/mdev/vfio_mdev.c b/drivers/vfio/mdev/vfio_mdev.c index 891cf83a2d9a..95efa054442f 100644 --- a/drivers/vfio/mdev/vfio_mdev.c +++ b/drivers/vfio/mdev/vfio_mdev.c @@ -14,6 +14,7 @@ #include <linux/slab.h> #include <linux/vfio.h> #include <linux/mdev.h> +#include <linux/vfio_mdev.h> #include "mdev_private.h" @@ -24,16 +25,16 @...
2019 Sep 25
0
[PATCH V2 5/8] mdev: introduce device specific ops
...> bool active; > > u16 class_id; > > + const void *device_ops; > > }; > > > > #define to_mdev_device(dev) container_of(dev, struct > mdev_device, dev) > > diff --git a/drivers/vfio/mdev/vfio_mdev.c > b/drivers/vfio/mdev/vfio_mdev.c > > index 891cf83a2d9a..95efa054442f 100644 > > --- a/drivers/vfio/mdev/vfio_mdev.c > > +++ b/drivers/vfio/mdev/vfio_mdev.c > > @@ -14,6 +14,7 @@ > > #include <linux/slab.h> > > #include <linux/vfio.h> > > #include <linux/mdev.h> > > +#include <linux/vfio_...
2019 Sep 24
17
[PATCH V2 0/8] 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 Sep 24
17
[PATCH V2 0/8] 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
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