From: Matthew Wilcox <willy@infradead.org>
To: Shubhang Kaushik OS <Shubhang@os.amperecomputing.com>
Cc: "ampere-linux-kernel@lists.amperecomputing.com"
<ampere-linux-kernel@lists.amperecomputing.com>,
"cl@linux.com" <cl@linux.com>,
Andrew Morton <akpm@linux-foundation.org>,
Uladzislau Rezki <urezki@gmail.com>,
Christoph Hellwig <hch@infradead.org>,
Lorenzo Stoakes <lstoakes@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH v2] vmalloc: Modify the alloc_vmap_area() error message for better diagnostics
Date: Tue, 4 Jun 2024 00:35:37 +0100 [thread overview]
Message-ID: <Zl5TSbHZJbtM4xIX@casper.infradead.org> (raw)
In-Reply-To: <MN2PR01MB5902582BA403FB9FA12816A6F5FF2@MN2PR01MB5902.prod.exchangelabs.com>
On Mon, Jun 03, 2024 at 09:30:54PM +0000, Shubhang Kaushik OS 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 not a valid kernel
> parameter on a number of platforms, in particular it is not supported
> on arm64. With the update, the output gets modified to include the function
Why not fix arm64?
next prev parent reply other threads:[~2024-06-03 23:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 21:30 Shubhang Kaushik OS
2024-06-03 23:35 ` Matthew Wilcox [this message]
[not found] ` <3329c844-509b-8769-01b6-a191b60bee35@linux.com>
2024-06-04 2:30 ` Anshuman Khandual
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=Zl5TSbHZJbtM4xIX@casper.infradead.org \
--to=willy@infradead.org \
--cc=Shubhang@os.amperecomputing.com \
--cc=akpm@linux-foundation.org \
--cc=ampere-linux-kernel@lists.amperecomputing.com \
--cc=cl@linux.com \
--cc=hch@infradead.org \
--cc=linux-mm@kvack.org \
--cc=lstoakes@gmail.com \
--cc=urezki@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox