search for: adm_max

Displaying 20 results from an estimated 29 matches for "adm_max".

Did you mean: addrmax
2019 Sep 24
3
[PATCH V2 5/8] mdev: introduce device specific ops
...> #include <linux/kvm_host.h> > #include <linux/module.h> > +#include <linux/vfio_mdev.h> > #include <asm/kvm.h> > #include <asm/zcrypt.h> > > @@ -321,6 +322,8 @@ static void vfio_ap_matrix_init(struct ap_config_info *info, > matrix->adm_max = info->apxa ? info->Nd : 15; > } > > +static const struct vfio_mdev_device_ops vfio_mdev_ops; > + > static int vfio_ap_mdev_create(struct kobject *kobj, struct mdev_device *mdev) > { > struct ap_matrix_mdev *matrix_mdev; > @@ -344,6 +347,7 @@ static int vfio_ap...
2019 Sep 24
3
[PATCH V2 5/8] mdev: introduce device specific ops
...> #include <linux/kvm_host.h> > #include <linux/module.h> > +#include <linux/vfio_mdev.h> > #include <asm/kvm.h> > #include <asm/zcrypt.h> > > @@ -321,6 +322,8 @@ static void vfio_ap_matrix_init(struct ap_config_info *info, > matrix->adm_max = info->apxa ? info->Nd : 15; > } > > +static const struct vfio_mdev_device_ops vfio_mdev_ops; > + > static int vfio_ap_mdev_create(struct kobject *kobj, struct mdev_device *mdev) > { > struct ap_matrix_mdev *matrix_mdev; > @@ -344,6 +347,7 @@ static int vfio_ap...
2019 Sep 24
0
[PATCH V2 5/8] mdev: introduce device specific ops
...16,7 @@ #include <linux/bitops.h> #include <linux/kvm_host.h> #include <linux/module.h> +#include <linux/vfio_mdev.h> #include <asm/kvm.h> #include <asm/zcrypt.h> @@ -321,6 +322,8 @@ static void vfio_ap_matrix_init(struct ap_config_info *info, matrix->adm_max = info->apxa ? info->Nd : 15; } +static const struct vfio_mdev_device_ops vfio_mdev_ops; + static int vfio_ap_mdev_create(struct kobject *kobj, struct mdev_device *mdev) { struct ap_matrix_mdev *matrix_mdev; @@ -344,6 +347,7 @@ static int vfio_ap_mdev_create(struct kobject *kobj, struc...
2019 Oct 11
0
[PATCH V3 4/7] mdev: introduce device specific ops
...16,7 @@ #include <linux/bitops.h> #include <linux/kvm_host.h> #include <linux/module.h> +#include <linux/vfio_mdev.h> #include <asm/kvm.h> #include <asm/zcrypt.h> @@ -321,6 +322,8 @@ static void vfio_ap_matrix_init(struct ap_config_info *info, matrix->adm_max = info->apxa ? info->Nd : 15; } +static const struct vfio_mdev_device_ops vfio_mdev_ops; + static int vfio_ap_mdev_create(struct kobject *kobj, struct mdev_device *mdev) { struct ap_matrix_mdev *matrix_mdev; @@ -343,7 +346,7 @@ static int vfio_ap_mdev_create(struct kobject *kobj, struc...
2019 Sep 25
0
[PATCH V2 5/8] mdev: introduce device specific ops
...t; > > #include <linux/module.h> > > +#include <linux/vfio_mdev.h> > > #include <asm/kvm.h> > > #include <asm/zcrypt.h> > > > > @@ -321,6 +322,8 @@ static void vfio_ap_matrix_init(struct > ap_config_info *info, > > matrix->adm_max = info->apxa ? info->Nd : 15; > > } > > > > +static const struct vfio_mdev_device_ops vfio_mdev_ops; > > + > > static int vfio_ap_mdev_create(struct kobject *kobj, struct mdev_device > *mdev) > > { > > struct ap_matrix_mdev *matrix_mdev; >...
2019 Oct 17
0
[PATCH V4 3/6] mdev: introduce device specific ops
...16,7 @@ #include <linux/bitops.h> #include <linux/kvm_host.h> #include <linux/module.h> +#include <linux/vfio_mdev.h> #include <asm/kvm.h> #include <asm/zcrypt.h> @@ -321,6 +322,8 @@ static void vfio_ap_matrix_init(struct ap_config_info *info, matrix->adm_max = info->apxa ? info->Nd : 15; } +static const struct vfio_mdev_device_ops vfio_mdev_ops; + static int vfio_ap_mdev_create(struct kobject *kobj, struct mdev_device *mdev) { struct ap_matrix_mdev *matrix_mdev; @@ -343,7 +346,7 @@ static int vfio_ap_mdev_create(struct kobject *kobj, struc...
2019 Nov 06
0
[PATCH V9 3/6] mdev: introduce device specific ops
...@@ #include <linux/bitops.h> #include <linux/kvm_host.h> #include <linux/module.h> +#include <linux/mdev_vfio_ops.h> #include <asm/kvm.h> #include <asm/zcrypt.h> @@ -321,6 +322,8 @@ static void vfio_ap_matrix_init(struct ap_config_info *info, matrix->adm_max = info->apxa ? info->Nd : 15; } +static const struct mdev_vfio_device_ops mdev_vfio_ops; + static int vfio_ap_mdev_create(struct kobject *kobj, struct mdev_device *mdev) { struct ap_matrix_mdev *matrix_mdev; @@ -343,7 +346,7 @@ static int vfio_ap_mdev_create(struct kobject *kobj, struc...
2019 Nov 07
0
[PATCH V11 3/6] mdev: introduce device specific ops
...@@ #include <linux/bitops.h> #include <linux/kvm_host.h> #include <linux/module.h> +#include <linux/mdev_vfio_ops.h> #include <asm/kvm.h> #include <asm/zcrypt.h> @@ -321,6 +322,8 @@ static void vfio_ap_matrix_init(struct ap_config_info *info, matrix->adm_max = info->apxa ? info->Nd : 15; } +static const struct mdev_vfio_device_ops mdev_vfio_ops; + static int vfio_ap_mdev_create(struct kobject *kobj, struct mdev_device *mdev) { struct ap_matrix_mdev *matrix_mdev; @@ -343,7 +346,7 @@ static int vfio_ap_mdev_create(struct kobject *kobj, struc...
2019 Nov 05
0
[PATCH V8 3/6] mdev: introduce device specific ops
...@@ #include <linux/bitops.h> #include <linux/kvm_host.h> #include <linux/module.h> +#include <linux/mdev_vfio_ops.h> #include <asm/kvm.h> #include <asm/zcrypt.h> @@ -321,6 +322,8 @@ static void vfio_ap_matrix_init(struct ap_config_info *info, matrix->adm_max = info->apxa ? info->Nd : 15; } +static const struct mdev_vfio_device_ops mdev_vfio_ops; + static int vfio_ap_mdev_create(struct kobject *kobj, struct mdev_device *mdev) { struct ap_matrix_mdev *matrix_mdev; @@ -343,7 +346,7 @@ static int vfio_ap_mdev_create(struct kobject *kobj, struc...
2019 Nov 04
0
[PATCH V7 3/6] mdev: introduce device specific ops
...@@ #include <linux/bitops.h> #include <linux/kvm_host.h> #include <linux/module.h> +#include <linux/mdev_vfio_ops.h> #include <asm/kvm.h> #include <asm/zcrypt.h> @@ -321,6 +322,8 @@ static void vfio_ap_matrix_init(struct ap_config_info *info, matrix->adm_max = info->apxa ? info->Nd : 15; } +static const struct mdev_vfio_device_ops mdev_vfio_ops; + static int vfio_ap_mdev_create(struct kobject *kobj, struct mdev_device *mdev) { struct ap_matrix_mdev *matrix_mdev; @@ -343,7 +346,7 @@ static int vfio_ap_mdev_create(struct kobject *kobj, struc...
2019 Nov 04
1
[PATCH V7 3/6] mdev: introduce device specific ops
...; #include <linux/kvm_host.h> > #include <linux/module.h> > +#include <linux/mdev_vfio_ops.h> > #include <asm/kvm.h> > #include <asm/zcrypt.h> > > @@ -321,6 +322,8 @@ static void vfio_ap_matrix_init(struct ap_config_info *info, > matrix->adm_max = info->apxa ? info->Nd : 15; > } > > +static const struct mdev_vfio_device_ops mdev_vfio_ops; > + > static int vfio_ap_mdev_create(struct kobject *kobj, struct mdev_device *mdev) > { > struct ap_matrix_mdev *matrix_mdev; > @@ -343,7 +346,7 @@ static int vfio_ap...
2019 Oct 21
0
[PATCH V4 3/6] mdev: introduce device specific ops
...; >> #include <linux/module.h> >> +#include <linux/vfio_mdev.h> >> #include <asm/kvm.h> >> #include <asm/zcrypt.h> >> >> @@ -321,6 +322,8 @@ static void vfio_ap_matrix_init(struct ap_config_info >> *info, >> matrix->adm_max = info->apxa ? info->Nd : 15; } >> >> +static const struct vfio_mdev_device_ops vfio_mdev_ops; >> + >> static int vfio_ap_mdev_create(struct kobject *kobj, struct mdev_device >> *mdev) { >> struct ap_matrix_mdev *matrix_mdev; >> @@ -343,7 +346,...
2019 Sep 25
3
[PATCH V2 5/8] mdev: introduce device specific ops
...le.h> > > > +#include <linux/vfio_mdev.h> > > > #include <asm/kvm.h> > > > #include <asm/zcrypt.h> > > > > > > @@ -321,6 +322,8 @@ static void vfio_ap_matrix_init(struct > > ap_config_info *info, > > > matrix->adm_max = info->apxa ? info->Nd : 15; > > > } > > > > > > +static const struct vfio_mdev_device_ops vfio_mdev_ops; > > > + > > > static int vfio_ap_mdev_create(struct kobject *kobj, struct > mdev_device > > *mdev) > > > { > > &gt...
2019 Sep 25
3
[PATCH V2 5/8] mdev: introduce device specific ops
...le.h> > > > +#include <linux/vfio_mdev.h> > > > #include <asm/kvm.h> > > > #include <asm/zcrypt.h> > > > > > > @@ -321,6 +322,8 @@ static void vfio_ap_matrix_init(struct > > ap_config_info *info, > > > matrix->adm_max = info->apxa ? info->Nd : 15; > > > } > > > > > > +static const struct vfio_mdev_device_ops vfio_mdev_ops; > > > + > > > static int vfio_ap_mdev_create(struct kobject *kobj, struct > mdev_device > > *mdev) > > > { > > &gt...
2019 Nov 04
9
[PATCH V7 0/6] mdev based hardware virtio offloading support
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
2019 Oct 17
12
[PATCH V4 0/6] mdev based hardware virtio offloading support
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
2019 Oct 17
12
[PATCH V4 0/6] mdev based hardware virtio offloading support
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
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 30
8
[PATCH V6 0/6] mdev based hardware virtio offloading support
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