All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Shubhang Kaushik OS <Shubhang@os.amperecomputing.com>
Cc: linux-riscv@lists.infradead.org,
	ampere-linux-kernel@lists.amperecomputing.com, urezki@gmail.com,
	linux-arm-kernel@lists.infradead.org, cl@linux.com,
	corbet@lwn.net, akpm@linux-foundation.org, linux-mm@kvack.org,
	guoren@kernel.org, linux-doc@vger.kernel.org,
	xiongwei.song@windriver.com, linux-csky@vger.kernel.org,
	willy@infradead.org
Subject: Re: [PATCH v5] vmalloc: Modify the alloc_vmap_area() error message for better diagnostics
Date: Mon, 29 Jul 2024 16:39:39 +0000	[thread overview]
Message-ID: <172227117987.3603.11842142446691677565.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <CH2PR01MB5894B0182EA0B28DF2EFB916F5C72@CH2PR01MB5894.prod.exchangelabs.com>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Andrew Morton <akpm@linux-foundation.org>:

On Tue, 11 Jun 2024 19:38:44 +0000 you wrote:
> 'vmap allocation for size %lu failed: use vmalloc=<size> to increase size'
> The above warning is seen in the kernel functionality for allocation of the restricted virtual memory range till exhaustion.
> 
> This message is misleading because 'vmalloc=' is supported on arm32, x86 platforms and is not a valid kernel parameter on a number of other platforms (in particular its not supported on arm64, alpha, loongarch, arc, csky, hexagon, microblaze, mips, nios2, openrisc, parisc, m64k, powerpc, riscv, sh, um, xtensa, s390, sparc). With the update, the output gets modified to include the function parameters along with the start and end of the virtual memory range allowed.
> 
> The warning message after fix on kernel version 6.10.0-rc1+:
> 
> [...]

Here is the summary with links:
  - [v5] vmalloc: Modify the alloc_vmap_area() error message for better diagnostics
    https://git.kernel.org/riscv/c/55ccad6fc1a0

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Shubhang Kaushik OS <Shubhang@os.amperecomputing.com>
Cc: linux-riscv@lists.infradead.org,
	ampere-linux-kernel@lists.amperecomputing.com, urezki@gmail.com,
	linux-arm-kernel@lists.infradead.org, cl@linux.com,
	corbet@lwn.net, akpm@linux-foundation.org, linux-mm@kvack.org,
	guoren@kernel.org, linux-doc@vger.kernel.org,
	xiongwei.song@windriver.com, linux-csky@vger.kernel.org,
	willy@infradead.org
Subject: Re: [PATCH v5] vmalloc: Modify the alloc_vmap_area() error message for better diagnostics
Date: Mon, 29 Jul 2024 16:39:39 +0000	[thread overview]
Message-ID: <172227117987.3603.11842142446691677565.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <CH2PR01MB5894B0182EA0B28DF2EFB916F5C72@CH2PR01MB5894.prod.exchangelabs.com>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Andrew Morton <akpm@linux-foundation.org>:

On Tue, 11 Jun 2024 19:38:44 +0000 you wrote:
> 'vmap allocation for size %lu failed: use vmalloc=<size> to increase size'
> The above warning is seen in the kernel functionality for allocation of the restricted virtual memory range till exhaustion.
> 
> This message is misleading because 'vmalloc=' is supported on arm32, x86 platforms and is not a valid kernel parameter on a number of other platforms (in particular its not supported on arm64, alpha, loongarch, arc, csky, hexagon, microblaze, mips, nios2, openrisc, parisc, m64k, powerpc, riscv, sh, um, xtensa, s390, sparc). With the update, the output gets modified to include the function parameters along with the start and end of the virtual memory range allowed.
> 
> The warning message after fix on kernel version 6.10.0-rc1+:
> 
> [...]

Here is the summary with links:
  - [v5] vmalloc: Modify the alloc_vmap_area() error message for better diagnostics
    https://git.kernel.org/riscv/c/55ccad6fc1a0

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  parent reply	other threads:[~2024-07-29 16:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11 19:38 [PATCH v5] vmalloc: Modify the alloc_vmap_area() error message for better diagnostics Shubhang Kaushik OS
2024-06-11 19:38 ` Shubhang Kaushik OS
2024-06-11 19:57 ` Andrew Morton
2024-06-11 19:57   ` Andrew Morton
2024-06-11 21:23   ` Shubhang Kaushik OS
2024-06-11 21:23     ` Shubhang Kaushik OS
2024-07-29 16:39 ` patchwork-bot+linux-riscv [this message]
2024-07-29 16:39   ` patchwork-bot+linux-riscv

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=172227117987.3603.11842142446691677565.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=Shubhang@os.amperecomputing.com \
    --cc=akpm@linux-foundation.org \
    --cc=ampere-linux-kernel@lists.amperecomputing.com \
    --cc=cl@linux.com \
    --cc=corbet@lwn.net \
    --cc=guoren@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-csky@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=urezki@gmail.com \
    --cc=willy@infradead.org \
    --cc=xiongwei.song@windriver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.