search for: max_mem_region

Displaying 16 results from an estimated 16 matches for "max_mem_region".

Did you mean: max_mem_regions
[PATCH 0992/1285] Replace numeric parameter like 0444 with macro
2016 Aug 02
0
[PATCH 0992/1285] Replace numeric parameter like 0444 with macro
...com> --- drivers/vhost/vhost.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c index 669fef1..bf338d1 100644 --- a/drivers/vhost/vhost.c +++ b/drivers/vhost/vhost.c @@ -31,7 +31,7 @@ #include "vhost.h" static ushort max_mem_regions = 64; -module_param(max_mem_regions, ushort, 0444); +module_param(max_mem_regions, ushort, S_IRUSR | S_IRGRP | S_IROTH); MODULE_PARM_DESC(max_mem_regions, "Maximum number of memory regions in memory map. (default: 64)"); -- 2.9.2
[PATCH 0992/1285] Replace numeric parameter like 0444 with macro
2016 Aug 02
0
[PATCH 0992/1285] Replace numeric parameter like 0444 with macro
...com> --- drivers/vhost/vhost.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c index 669fef1..bf338d1 100644 --- a/drivers/vhost/vhost.c +++ b/drivers/vhost/vhost.c @@ -31,7 +31,7 @@ #include "vhost.h" static ushort max_mem_regions = 64; -module_param(max_mem_regions, ushort, 0444); +module_param(max_mem_regions, ushort, S_IRUSR | S_IRGRP | S_IROTH); MODULE_PARM_DESC(max_mem_regions, "Maximum number of memory regions in memory map. (default: 64)"); -- 2.9.2
[PULL] vhost: cleanups and fixes
2015 Jul 15
1
[PULL] vhost: cleanups and fixes
...d8cc1e75b1ee: virtio-pci: alloc only resources actually used. (2015-06-24 08:15:09 +0200) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus for you to fetch changes up to c9ce42f72fd0ba180fd35539829e4139dca31494: vhost: add max_mem_regions module parameter (2015-07-13 23:17:19 +0300) ---------------------------------------------------------------- virtio/vhost: fixes for 4.2 Bugfixes and documentation fixes. Igor's patch that allows users to tweak memory table size is borderline, but it does fix known crashes, so I merged it....
[PULL] vhost: cleanups and fixes
2015 Jul 15
1
[PULL] vhost: cleanups and fixes
...d8cc1e75b1ee: virtio-pci: alloc only resources actually used. (2015-06-24 08:15:09 +0200) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus for you to fetch changes up to c9ce42f72fd0ba180fd35539829e4139dca31494: vhost: add max_mem_regions module parameter (2015-07-13 23:17:19 +0300) ---------------------------------------------------------------- virtio/vhost: fixes for 4.2 Bugfixes and documentation fixes. Igor's patch that allows users to tweak memory table size is borderline, but it does fix known crashes, so I merged it....
[PULL v2] virtio/vhost: fixes for 4.2
2015 Jul 23
0
[PULL v2] virtio/vhost: fixes for 4.2
...d8cc1e75b1ee: virtio-pci: alloc only resources actually used. (2015-06-24 08:15:09 +0200) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus for you to fetch changes up to c9ce42f72fd0ba180fd35539829e4139dca31494: vhost: add max_mem_regions module parameter (2015-07-13 23:17:19 +0300) ---------------------------------------------------------------- virtio/vhost: fixes for 4.2 Bugfixes and documentation fixes. Igor's patch that allows users to tweak memory table size is borderline, but it does fix known crashes, so I merged it....
[PULL v2] virtio/vhost: fixes for 4.2
2015 Jul 23
0
[PULL v2] virtio/vhost: fixes for 4.2
...d8cc1e75b1ee: virtio-pci: alloc only resources actually used. (2015-06-24 08:15:09 +0200) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus for you to fetch changes up to c9ce42f72fd0ba180fd35539829e4139dca31494: vhost: add max_mem_regions module parameter (2015-07-13 23:17:19 +0300) ---------------------------------------------------------------- virtio/vhost: fixes for 4.2 Bugfixes and documentation fixes. Igor's patch that allows users to tweak memory table size is borderline, but it does fix known crashes, so I merged it....
[PATCH] vhost: Move vhost.h to allow vhost driver out-of-tree compilation
2017 Mar 07
2
[PATCH] vhost: Move vhost.h to allow vhost driver out-of-tree compilation
...hers. */ diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c index 998bed5..d5c5f3c 100644 --- a/drivers/vhost/vhost.c +++ b/drivers/vhost/vhost.c @@ -29,8 +29,6 @@ #include <linux/sort.h> #include <linux/interval_tree_generic.h> -#include "vhost.h" - static ushort max_mem_regions = 64; module_param(max_mem_regions, ushort, 0444); MODULE_PARM_DESC(max_mem_regions, diff --git a/drivers/vhost/vhost.h b/drivers/vhost/vhost.h deleted file mode 100644 index f55671d..0000000 --- a/drivers/vhost/vhost.h +++ /dev/null @@ -1,292 +0,0 @@ -#ifndef _VHOST_H -#define _VHOST_H - -#incl...
[PATCH] vhost: Move vhost.h to allow vhost driver out-of-tree compilation
2017 Mar 07
2
[PATCH] vhost: Move vhost.h to allow vhost driver out-of-tree compilation
...hers. */ diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c index 998bed5..d5c5f3c 100644 --- a/drivers/vhost/vhost.c +++ b/drivers/vhost/vhost.c @@ -29,8 +29,6 @@ #include <linux/sort.h> #include <linux/interval_tree_generic.h> -#include "vhost.h" - static ushort max_mem_regions = 64; module_param(max_mem_regions, ushort, 0444); MODULE_PARM_DESC(max_mem_regions, diff --git a/drivers/vhost/vhost.h b/drivers/vhost/vhost.h deleted file mode 100644 index f55671d..0000000 --- a/drivers/vhost/vhost.h +++ /dev/null @@ -1,292 +0,0 @@ -#ifndef _VHOST_H -#define _VHOST_H - -#incl...
[PATCH] vhost: Move vhost.h to allow vhost driver out-of-tree compilation
2017 Mar 10
0
[PATCH] vhost: Move vhost.h to allow vhost driver out-of-tree compilation
...ers/vhost/vhost.c > index 998bed5..d5c5f3c 100644 > --- a/drivers/vhost/vhost.c > +++ b/drivers/vhost/vhost.c > @@ -29,8 +29,6 @@ > #include <linux/sort.h> > #include <linux/interval_tree_generic.h> > > -#include "vhost.h" > - > static ushort max_mem_regions = 64; > module_param(max_mem_regions, ushort, 0444); > MODULE_PARM_DESC(max_mem_regions, > diff --git a/drivers/vhost/vhost.h b/drivers/vhost/vhost.h > deleted file mode 100644 > index f55671d..0000000 > --- a/drivers/vhost/vhost.h > +++ /dev/null > @@ -1,292 +0,0 @@ >...
[PATCH 3/3] vhost: device IOTLB API
2016 Jun 22
0
[PATCH 3/3] vhost: device IOTLB API
...host_net_chr_poll, .unlocked_ioctl = vhost_net_ioctl, #ifdef CONFIG_COMPAT .compat_ioctl = vhost_net_compat_ioctl, diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c index 166e779..46569fb 100644 --- a/drivers/vhost/vhost.c +++ b/drivers/vhost/vhost.c @@ -35,6 +35,10 @@ static ushort max_mem_regions = 64; module_param(max_mem_regions, ushort, 0444); MODULE_PARM_DESC(max_mem_regions, "Maximum number of memory regions in memory map. (default: 64)"); +static int max_iotlb_entries = 2048; +module_param(max_iotlb_entries, int, 0444); +MODULE_PARM_DESC(max_iotlb_entries, + "Maxim...
[PATCH V2 0/3] basic device IOTLB support for vhost_net
2016 Jun 23
3
[PATCH V2 0/3] basic device IOTLB support for vhost_net
This patch tries to implement an device IOTLB for vhost. This could be used with for co-operation with userspace IOMMU implementation (qemu) for a secure DMA environment (DMAR) in guest. The idea is simple. When vhost meets an IOTLB miss, it will request the assistance of userspace to do the translation, this is done through: - when there's a IOTLB miss, it will notify userspace through
[PATCH V2 0/3] basic device IOTLB support for vhost_net
2016 Jun 23
3
[PATCH V2 0/3] basic device IOTLB support for vhost_net
This patch tries to implement an device IOTLB for vhost. This could be used with for co-operation with userspace IOMMU implementation (qemu) for a secure DMA environment (DMAR) in guest. The idea is simple. When vhost meets an IOTLB miss, it will request the assistance of userspace to do the translation, this is done through: - when there's a IOTLB miss, it will notify userspace through
[RFC PATCH V3 0/3] basic device IOTLB support
2016 May 24
6
[RFC PATCH V3 0/3] basic device IOTLB support
This patch tries to implement an device IOTLB for vhost. This could be used with for co-operation with userspace IOMMU implementation (qemu) for a secure DMA environment (DMAR) in guest. The idea is simple. When vhost meets an IOTLB miss, it will request the assistance of userspace to do the translation, this is done through: - when there's a IOTLB miss, it will notify userspace through
[RFC PATCH V3 0/3] basic device IOTLB support
2016 May 24
6
[RFC PATCH V3 0/3] basic device IOTLB support
This patch tries to implement an device IOTLB for vhost. This could be used with for co-operation with userspace IOMMU implementation (qemu) for a secure DMA environment (DMAR) in guest. The idea is simple. When vhost meets an IOTLB miss, it will request the assistance of userspace to do the translation, this is done through: - when there's a IOTLB miss, it will notify userspace through
[PATCH 0/3] basic device IOTLB support
2016 Jun 22
4
[PATCH 0/3] basic device IOTLB support
This patch tries to implement an device IOTLB for vhost. This could be used with for co-operation with userspace IOMMU implementation (qemu) for a secure DMA environment (DMAR) in guest. The idea is simple. When vhost meets an IOTLB miss, it will request the assistance of userspace to do the translation, this is done through: - when there's a IOTLB miss, it will notify userspace through
[PATCH 0/3] basic device IOTLB support
2016 Jun 22
4
[PATCH 0/3] basic device IOTLB support
This patch tries to implement an device IOTLB for vhost. This could be used with for co-operation with userspace IOMMU implementation (qemu) for a secure DMA environment (DMAR) in guest. The idea is simple. When vhost meets an IOTLB miss, it will request the assistance of userspace to do the translation, this is done through: - when there's a IOTLB miss, it will notify userspace through