Home
last modified time | relevance | path

Searched refs:vmalloc (Results 1 – 25 of 346) sorted by relevance

12345678910>>...14

/linux-6.1.9/lib/
Dtest_vmalloc.c155 p = vmalloc(n * PAGE_SIZE); in random_size_alloc_test()
174 ptr = vmalloc(sizeof(void *) * 15000); in long_busy_list_alloc_test()
179 ptr[i] = vmalloc(1 * PAGE_SIZE); in long_busy_list_alloc_test()
182 ptr_1 = vmalloc(100 * PAGE_SIZE); in long_busy_list_alloc_test()
186 ptr_2 = vmalloc(1 * PAGE_SIZE); in long_busy_list_alloc_test()
220 ptr = vmalloc(sizeof(void *) * junk_length); in full_fit_alloc_test()
224 junk_ptr = vmalloc(sizeof(void *) * junk_length); in full_fit_alloc_test()
231 ptr[i] = vmalloc(1 * PAGE_SIZE); in full_fit_alloc_test()
232 junk_ptr[i] = vmalloc(1 * PAGE_SIZE); in full_fit_alloc_test()
239 tmp = vmalloc(1 * PAGE_SIZE); in full_fit_alloc_test()
[all …]
/linux-6.1.9/samples/kmemleak/
Dkmemleak-test.c57 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()
/linux-6.1.9/Documentation/translations/zh_CN/dev-tools/
Dkasan.rst64 通用KASAN支持在所有的slab、page_alloc、vmap、vmalloc、堆栈和全局内存
67 基于软件标签的KASAN支持slab、page_alloc、vmalloc和堆栈内存。
69 基于硬件标签的KASAN支持slab、page_alloc和不可执行的vmalloc内存。
224 - ``kasan.vmalloc=off`` 或 ``=on`` 禁用或启用vmalloc分配的标记（默认：``on`` ）。
324 小区域）。对于所有其他区域 —— 例如vmalloc和vmemmap空间 —— 一个只读页面被映射
331 这也造成了与 ``VMAP_STACK`` 的不兼容：如果堆栈位于vmalloc空间中，它将被分配
337 使用 ``CONFIG_KASAN_VMALLOC`` ，KASAN可以以更大的内存使用为代价覆盖vmalloc
340 这通过连接到vmalloc和vmap并动态分配真实的影子内存来支持映射。
342 vmalloc空间中的大多数映射都很小，需要不到一整页的阴影空间。因此，为每个映射
346 相反，KASAN跨多个映射共享后备空间。当vmalloc空间中的映射使用影子区域的特定
[all …]
/linux-6.1.9/Documentation/translations/zh_CN/core-api/
Dmemory-allocation.rst20 系列分配小块内存，使用 `vmalloc` 及其派生产品分配大的几乎连续的区域，或者
123 对于大量的分配，你可以使用vmalloc()和vzalloc()，或者直接向页面分配器请求页面。由vmalloc
127 试用kmalloc分配内存，如果分配失败，将用 `vmalloc` 重新尝试。对于哪些GFP标志可以与 `kvmalloc`
136 当分配的内存不再需要时，它必须被释放。你可以使用kvfree()来处理用 `kmalloc` 、 `vmalloc`
Dgfp_mask-from-fs-io.rst60 vmalloc不支持GFP_NOFS语义，因为在分配器的深处有硬编码的GFP_KERNEL分配，要修
61 复这些分配是相当不容易的。这意味着用GFP_NOFS/GFP_NOIO调用 ``vmalloc`` 几乎
64 在理想的世界中，上层应该已经标记了危险的上下文，因此不需要特别的照顾， ``vmalloc``
66 推荐的方法是用范围API包装vmalloc，并加上注释来解释问题。
/linux-6.1.9/scripts/coccinelle/api/
Dkfree_mismatch.cocci4 /// 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 …]
Dkvmalloc.cocci3 /// 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);
/linux-6.1.9/scripts/coccinelle/api/alloc/
Dalloc_cast.cocci35 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\|
Dzalloc-simple.cocci37 * 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)
/linux-6.1.9/fs/jffs2/
Dcompr_lzo.c32 lzo_mem = vmalloc(LZO1X_MEM_COMPRESS); in alloc_workspace()
33 lzo_compress_buf = vmalloc(lzo1x_worst_compress(PAGE_SIZE)); in alloc_workspace()
Dcompr_zlib.c45 def_strm.workspace = vmalloc(zlib_deflate_workspacesize(MAX_WBITS, in alloc_workspaces()
52 inf_strm.workspace = vmalloc(zlib_inflate_workspacesize()); in alloc_workspaces()
/linux-6.1.9/Documentation/core-api/
Dgfp_mask-from-fs-io.rst58 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``
/linux-6.1.9/Documentation/translations/zh_CN/mm/
Dvmalloced-kernel-stacks.rst47 - vmalloc空间必须大到足以容纳许多内核堆栈。这可能排除了许多32位架构。
48 - vmalloc空间的堆栈需要可靠地工作。例如，如果vmap页表是按需创建的，当堆栈指向
/linux-6.1.9/sound/drivers/opl4/
Dopl4_proc.c46 buf = vmalloc(count); in snd_opl4_mem_proc_read()
67 buf = vmalloc(count); in snd_opl4_mem_proc_write()
/linux-6.1.9/fs/squashfs/
Dlzo_wrapper.c35 stream->input = vmalloc(block_size); in lzo_init()
38 stream->output = vmalloc(block_size); in lzo_init()
Dlz4_wrapper.c60 stream->input = vmalloc(block_size); in lz4_init()
63 stream->output = vmalloc(block_size); in lz4_init()
/linux-6.1.9/drivers/gpu/drm/vmwgfx/
Dvmwgfx_fb.c43 void *vmalloc; member
239 src_ptr = (u8 *)par->vmalloc + in vmw_fb_dirty_flush()
656 par->vmalloc = NULL; in vmw_fb_init()
672 par->vmalloc = vzalloc(fb_size); in vmw_fb_init()
673 if (unlikely(par->vmalloc == NULL)) { in vmw_fb_init()
695 info->screen_base = (char __iomem *)par->vmalloc; in vmw_fb_init()
751 vfree(par->vmalloc); in vmw_fb_init()
779 vfree(par->vmalloc); in vmw_fb_close()
/linux-6.1.9/Documentation/translations/zh_CN/riscv/
Dvm-layout.rst58 ffffffc800000000 | -224 GB | ffffffd7ffffffff | 64 GB | vmalloc/ioremap space
94 ffff8f8000000000 | -112.5 TB | ffffaf7fffffffff | 32 TB | vmalloc/ioremap space
/linux-6.1.9/drivers/scsi/fnic/
Dfnic_debugfs.c47 fc_trc_flag = vmalloc(sizeof(struct fc_trace_flag_type)); in fnic_debugfs_init()
204 fnic_dbg_prt->buffer = vmalloc(array3_size(3, trace_max_pages, in fnic_trace_debugfs_open()
215 vmalloc(array3_size(3, fnic_fc_trace_max_pages, in fnic_trace_debugfs_open()
590 debug->debug_buffer = vmalloc(buf_size); in fnic_stats_debugfs_open()
/linux-6.1.9/Documentation/arm/
Dporting.rst97 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
Dmemory.rst57 mapping within the vmalloc space.
59 VMALLOC_START VMALLOC_END-1 vmalloc() / ioremap() space.
60 Memory returned by vmalloc/ioremap will
/linux-6.1.9/arch/um/include/shared/
Dum_malloc.h14 extern void *vmalloc(unsigned long size);
/linux-6.1.9/drivers/video/
Dvgastate.c362 saved->vga_cmap = vmalloc(768); in save_vga()
384 saved->attr = vmalloc(total); in save_vga()
421 saved->vga_font0 = vmalloc(4 * 8192); in save_vga()
433 saved->vga_font1 = vmalloc(state->memsize); in save_vga()
444 saved->vga_text = vmalloc(8192 * 2); in save_vga()
/linux-6.1.9/Documentation/dev-tools/
Dkasan.rst67 Generic KASAN supports finding bugs in all of slab, page_alloc, vmap, vmalloc,
70 Software Tag-Based KASAN supports slab, page_alloc, vmalloc, and stack memory.
72 Hardware Tag-Based KASAN supports slab, page_alloc, and non-executable vmalloc
140 - ``kasan.vmalloc=off`` or ``=on`` disables or enables tagging of vmalloc
374 other areas - such as vmalloc and vmemmap space - a single read-only
384 lives in vmalloc space, it will be shadowed by the read-only page, and
391 With ``CONFIG_KASAN_VMALLOC``, KASAN can cover vmalloc space at the
395 This works by hooking into vmalloc and vmap and dynamically
398 Most mappings in vmalloc space are small, requiring less than a full
405 a backing page when a mapping in vmalloc space uses a particular page
[all …]
/linux-6.1.9/drivers/mtd/tests/
Dstresstest.c179 readbuf = vmalloc(bufsize); in mtd_stresstest_init()
180 writebuf = vmalloc(bufsize); in mtd_stresstest_init()

12345678910>>...14