In fact "vmalloc=<size>" cmdline option is not available on many platforms.When the user encounters this error, add the correct hint to prevent misleading.
Signed-off-by: Tian Tao <[email protected]> v2: Add appropriate hints and let users decide if they can increase the size of the vmalloc by vmalloc=<size> depending on their platform v3: change the patch name and commit messages. --- mm/vmalloc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mm/vmalloc.c b/mm/vmalloc.c index 89e83d3..c6ae7e6 100644 --- a/mm/vmalloc.c +++ b/mm/vmalloc.c @@ -1238,8 +1238,8 @@ static struct vmap_area *alloc_vmap_area(unsigned long size, } if (!(gfp_mask & __GFP_NOWARN) && printk_ratelimit()) - pr_warn("vmap allocation for size %lu failed: use vmalloc=<size> to increase size\n", - size); + pr_warn("vmap allocation for size %lu failed: use vmalloc=<size> to increase size, + if your ARCH supports it\n", size); kmem_cache_free(vmap_area_cachep, va); return ERR_PTR(-EBUSY); -- 2.7.4
