/openbmc/linux/lib/ |
H A D | test_vmalloc.c | 159 p = vmalloc(n * PAGE_SIZE); in random_size_alloc_test() 178 ptr = vmalloc(sizeof(void *) * 15000); in long_busy_list_alloc_test() 183 ptr[i] = vmalloc(1 * PAGE_SIZE); in long_busy_list_alloc_test() 186 ptr_1 = vmalloc(100 * PAGE_SIZE); in long_busy_list_alloc_test() 190 ptr_2 = vmalloc(1 * PAGE_SIZE); in long_busy_list_alloc_test() 224 ptr = vmalloc(sizeof(void *) * junk_length); in full_fit_alloc_test() 228 junk_ptr = vmalloc(sizeof(void *) * junk_length); in full_fit_alloc_test() 235 ptr[i] = vmalloc(1 * PAGE_SIZE); in full_fit_alloc_test() 236 junk_ptr[i] = vmalloc(1 * PAGE_SIZE); in full_fit_alloc_test() 243 tmp = vmalloc(1 * PAGE_SIZE); in full_fit_alloc_test() [all …]
|
/openbmc/linux/samples/kmemleak/ |
H A D | kmemleak-test.c | 57 pr_info("vmalloc(64) = %p\n", vmalloc(64)); in kmemleak_test_init() 58 pr_info("vmalloc(64) = %p\n", vmalloc(64)); in kmemleak_test_init() 59 pr_info("vmalloc(64) = %p\n", vmalloc(64)); in kmemleak_test_init() 60 pr_info("vmalloc(64) = %p\n", vmalloc(64)); in kmemleak_test_init() 61 pr_info("vmalloc(64) = %p\n", vmalloc(64)); in kmemleak_test_init()
|
/openbmc/linux/Documentation/translations/zh_CN/dev-tools/ |
H A D | kasan.rst | 64 通用KASAN支持在所有的slab、page_alloc、vmap、vmalloc、堆栈和全局内存 67 基于软件标签的KASAN支持slab、page_alloc、vmalloc和堆栈内存。 69 基于硬件标签的KASAN支持slab、page_alloc和不可执行的vmalloc内存。 132 - ``kasan.vmalloc=off`` or ``=on`` 禁用或启用vmalloc分配的标记(默认: ``on`` )。 332 小区域)。对于所有其他区域 —— 例如vmalloc和vmemmap空间 —— 一个只读页面被映射 339 这也造成了与 ``VMAP_STACK`` 的不兼容:如果堆栈位于vmalloc空间中,它将被分配 345 使用 ``CONFIG_KASAN_VMALLOC`` ,KASAN可以以更大的内存使用为代价覆盖vmalloc 348 这通过连接到vmalloc和vmap并动态分配真实的影子内存来支持映射。 350 vmalloc空间中的大多数映射都很小,需要不到一整页的阴影空间。因此,为每个映射 354 相反,KASAN跨多个映射共享后备空间。当vmalloc空间中的映射使用影子区域的特定 [all …]
|
/openbmc/linux/scripts/coccinelle/api/ |
H A D | kfree_mismatch.cocci | 4 /// vmalloc'ed by vfree functions and kvmalloc'ed by kvfree 31 E = \(vmalloc\|vzalloc\|vmalloc_user\|vmalloc_node\| 44 E = \(vmalloc\|vzalloc\|vmalloc_user\|vmalloc_node\| 71 …... when != if (...) { ... E = \(vmalloc\|vzalloc\|vmalloc_user\|vmalloc_node\|vzalloc_node\|vmall… 85 …... when != if (...) { ... E = \(vmalloc\|vzalloc\|vmalloc_user\|vmalloc_node\|vzalloc_node\|vmall… 97 * E = \(vmalloc\|vzalloc\|vmalloc_user\|vmalloc_node\|vzalloc_node\| 110 E = \(vmalloc\|vzalloc\|vmalloc_user\|vmalloc_node\|vzalloc_node\| 185 msg = "WARNING vmalloc is used to allocate this memory at line %s" % (a[0].line) 193 msg = "WARNING vmalloc is used to allocate this memory at line %s" % (a[0].line) 218 msg = "WARNING kmalloc (line %s) && vmalloc (line %s) are used to allocate this memory" % (ka[0].li… [all …]
|
H A D | kvmalloc.cocci | 3 /// Find if/else condition with kmalloc/vmalloc calls. 41 * E = \(vmalloc\|vzalloc\|vmalloc_node\|vzalloc_node\)(..., size, ...) 53 * E = \(vmalloc\|vzalloc\|vmalloc_node\|vzalloc_node\)(..., size, ...) 65 * x = \(vmalloc\|vzalloc\|vmalloc_node\|vzalloc_node\)(..., size, ...) 97 - E = vmalloc(size); 103 - E = vmalloc(size); 108 - E = vmalloc(size); 113 - E = vmalloc(size); 118 - x = vmalloc(size); 123 - x = vmalloc(size);
|
/openbmc/linux/Documentation/translations/zh_CN/core-api/ |
H A D | memory-allocation.rst | 20 系列分配小块内存,使用 `vmalloc` 及其派生产品分配大的几乎连续的区域,或者 123 对于大量的分配,你可以使用vmalloc()和vzalloc(),或者直接向页面分配器请求页面。由vmalloc 127 试用kmalloc分配内存,如果分配失败,将用 `vmalloc` 重新尝试。对于哪些GFP标志可以与 `kvmalloc` 136 当分配的内存不再需要时,它必须被释放。你可以使用kvfree()来处理用 `kmalloc` 、 `vmalloc`
|
H A D | gfp_mask-from-fs-io.rst | 60 vmalloc不支持GFP_NOFS语义,因为在分配器的深处有硬编码的GFP_KERNEL分配,要修 61 复这些分配是相当不容易的。这意味着用GFP_NOFS/GFP_NOIO调用 ``vmalloc`` 几乎 64 在理想的世界中,上层应该已经标记了危险的上下文,因此不需要特别的照顾, ``vmalloc`` 66 推荐的方法是用范围API包装vmalloc,并加上注释来解释问题。
|
/openbmc/linux/scripts/coccinelle/api/alloc/ |
H A D | alloc_cast.cocci | 35 kmem_cache_alloc_node\|kmalloc_node\|kzalloc_node\|vmalloc\|vzalloc\| 58 kmem_cache_alloc_node\|kmalloc_node\|kzalloc_node\|vmalloc\|vzalloc\| 81 kmem_cache_alloc_node\|kmalloc_node\|kzalloc_node\|vmalloc\|vzalloc\| 98 kmem_cache_alloc_node\|kmalloc_node\|kzalloc_node\|vmalloc\|vzalloc\|
|
H A D | zalloc-simple.cocci | 37 * x = (T)\(kmalloc(E1, ...)\|vmalloc(E1)\|dma_alloc_coherent(...,E1,...)\| 64 - x = vmalloc(E1); 67 - x = (T *)vmalloc(E1); 70 - x = (T)vmalloc(E1); 182 x = (T)vmalloc@p(E1); 200 msg="WARNING: vzalloc should be used for %s, instead of vmalloc/memset" % (x)
|
/openbmc/linux/Documentation/core-api/ |
H A D | gfp_mask-from-fs-io.rst | 58 vmalloc doesn't support GFP_NOFS semantic because there are hardcoded 60 to fix up. That means that calling ``vmalloc`` with GFP_NOFS/GFP_NOIO is 65 and so no special care is required and vmalloc should be called without 67 layering violations then the recommended way around that is to wrap ``vmalloc``
|
/openbmc/linux/fs/jffs2/ |
H A D | compr_lzo.c | 32 lzo_mem = vmalloc(LZO1X_MEM_COMPRESS); in alloc_workspace() 33 lzo_compress_buf = vmalloc(lzo1x_worst_compress(PAGE_SIZE)); in alloc_workspace()
|
H A D | compr_zlib.c | 45 def_strm.workspace = vmalloc(zlib_deflate_workspacesize(MAX_WBITS, in alloc_workspaces() 52 inf_strm.workspace = vmalloc(zlib_inflate_workspacesize()); in alloc_workspaces()
|
/openbmc/linux/Documentation/translations/zh_CN/mm/ |
H A D | vmalloced-kernel-stacks.rst | 47 - vmalloc空间必须大到足以容纳许多内核堆栈。这可能排除了许多32位架构。 48 - vmalloc空间的堆栈需要可靠地工作。例如,如果vmap页表是按需创建的,当堆栈指向
|
/openbmc/linux/sound/drivers/opl4/ |
H A D | opl4_proc.c | 46 buf = vmalloc(count); in snd_opl4_mem_proc_read() 67 buf = vmalloc(count); in snd_opl4_mem_proc_write()
|
/openbmc/linux/fs/squashfs/ |
H A D | lzo_wrapper.c | 35 stream->input = vmalloc(block_size); in lzo_init() 38 stream->output = vmalloc(block_size); in lzo_init()
|
H A D | lz4_wrapper.c | 60 stream->input = vmalloc(block_size); in lz4_init() 63 stream->output = vmalloc(block_size); in lz4_init()
|
/openbmc/linux/Documentation/translations/zh_CN/riscv/ |
H A D | vm-layout.rst | 58 ffffffc800000000 | -224 GB | ffffffd7ffffffff | 64 GB | vmalloc/ioremap space 94 ffff8f8000000000 | -112.5 TB | ffffaf7fffffffff | 32 TB | vmalloc/ioremap space
|
/openbmc/linux/Documentation/arch/arm/ |
H A D | porting.rst | 97 Virtual addresses bounding the vmalloc() area. There must not be 98 any static mappings in this area; vmalloc will overwrite them. 100 Normally, the vmalloc() area starts VMALLOC_OFFSET bytes above the 105 between virtual RAM and the vmalloc area. We do this to allow
|
H A D | memory.rst | 57 mapping within the vmalloc space. 59 VMALLOC_START VMALLOC_END-1 vmalloc() / ioremap() space. 60 Memory returned by vmalloc/ioremap will
|
/openbmc/linux/arch/um/include/shared/ |
H A D | um_malloc.h | 14 extern void *vmalloc(unsigned long size);
|
/openbmc/openbmc/meta-facebook/meta-minerva/recipes-bsp/u-boot/u-boot-aspeed-sdk/ |
H A D | minerva.cfg | 2 CONFIG_BOOTARGS="console=ttyS4,57600n8 root=/dev/ram rw vmalloc=768M"
|
/openbmc/openbmc/meta-facebook/recipes-bsp/uboot/files/ |
H A D | yosemite4-common.cfg | 2 CONFIG_BOOTARGS="console=ttyS4,57600n8 root=/dev/ram rw vmalloc=768M"
|
/openbmc/openbmc/meta-facebook/meta-greatlakes/recipes-bsp/u-boot/u-boot-aspeed-sdk/ |
H A D | greatlakes.cfg | 2 CONFIG_BOOTARGS="console=ttyS4,57600n8 root=/dev/ram rw vmalloc=384M"
|
/openbmc/openbmc/meta-facebook/meta-harma/recipes-bsp/u-boot/u-boot-aspeed-sdk/ |
H A D | harma.cfg | 2 CONFIG_BOOTARGS="console=ttyS4,57600n8 root=/dev/ram rw vmalloc=768M"
|
/openbmc/openbmc/meta-facebook/meta-catalina/recipes-bsp/u-boot/u-boot-aspeed-sdk/ |
H A D | catalina.cfg | 2 CONFIG_BOOTARGS="console=ttyS4,57600n8 root=/dev/ram rw vmalloc=768M"
|