From: Uladzislau Rezki <urezki@gmail.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
Tian Tao <tiantao6@hisilicon.com>
Cc: Tian Tao <tiantao6@hisilicon.com>,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linuxarm@huawei.com
Subject: Re: [PATCH] vmalloc: Removing incorrect logs when vmalloc failed
Date: Tue, 7 Jul 2020 15:24:42 +0200 [thread overview]
Message-ID: <20200707132442.GA26493@pc636> (raw)
In-Reply-To: <5e7885ef-081e-0682-7be7-40eb7712d2c7@arm.com>
On Tue, Jul 07, 2020 at 03:18:54PM +0530, Anshuman Khandual wrote:
>
>
> On 07/07/2020 02:43 PM, Tian Tao wrote:
> > It is not possible to increase size with vmalloc=<size> in arm64
> > architecture and it will mislead.however vmalloc return failure
> > is a rare occurrence in 'many architectures including arm64'.
>
> But there is a chance that vmalloc() might work on architectures
> that support 'vmalloc=' command line i.e after a change and this
> information here might be helpful in those cases.
>
Agree. At least i see a few users of it:
<snip>
urezki@pc638:~/data/coding/linux-next.git$ grep -rn early_param ./arch/ | grep vmalloc
./arch/arm/mm/mmu.c:1152:early_param("vmalloc", early_vmalloc);
./arch/unicore32/mm/mmu.c:276:early_param("vmalloc", early_vmalloc);
./arch/x86/mm/pgtable_32.c:86:early_param("vmalloc", parse_vmalloc);
urezki@pc638:~/data/coding/linux-next.git$
<snip>
Thanks!
--
Vlad Rezki
next prev parent reply other threads:[~2020-07-07 13:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 9:13 [PATCH] vmalloc: Removing incorrect logs when vmalloc failed Tian Tao
2020-07-07 9:48 ` Anshuman Khandual
2020-07-07 13:24 ` Uladzislau Rezki [this message]
[not found] ` <3cf13a05-a6b8-aa2f-752d-f9a25a1005f9@huawei.com>
2020-07-08 13:48 ` Uladzislau Rezki
2020-07-09 1:03 ` tiantao (H)
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=20200707132442.GA26493@pc636 \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxarm@huawei.com \
--cc=tiantao6@hisilicon.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;
as well as URLs for NNTP newsgroup(s).