From: Mike Rapoport <rppt@kernel.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: akpm@linux-foundation.org, david@redhat.com,
geert+renesas@glider.be, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH] memblock: check memory total_size
Date: Tue, 28 Sep 2021 09:37:55 -0700 [thread overview]
Message-ID: <YVNE43IBP0iUmng5@kernel.org> (raw)
In-Reply-To: <20210928105057.3406-1-peng.fan@oss.nxp.com>
Hi,
On Tue, Sep 28, 2021 at 06:50:57PM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> mem=[X][G|M] is broken on NXP i.MX ARM64 platform, there is cases that
> even type.cnt is 1, but total_size is not 0 because regions are merged
> into 1. So only check 'cnt' is not enough, total_size also needs to be
> taked into consideration, othersize bootargs 'mem=[X][G|B]' not work
> anymore.
I believe this is issue is not specific to i.MX but rather this could
happen on any arm64 platform. Can you please update the changelog?
> Fixes: e888fa7bb882 ("memblock: Check memory add/cap ordering")
> Cc: Mike Rapoport <rppt@kernel.org>
> Cc: Geert Uytterhoeven <geert+renesas@glider.be>
> Cc: David Hildenbrand <david@redhat.com>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> mm/memblock.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/memblock.c b/mm/memblock.c
> index 184dcd2e5d99..ab67b82a9cce 100644
> --- a/mm/memblock.c
> +++ b/mm/memblock.c
> @@ -1687,7 +1687,7 @@ void __init memblock_cap_memory_range(phys_addr_t base, phys_addr_t size)
> if (!size)
> return;
>
> - if (memblock.memory.cnt <= 1) {
> + if (memblock_memory->cnt <= 1 && !memblock_memory->total_size) {
The test for non-zero total size shold be sufficient here.
> pr_warn("%s: No memory registered yet\n", __func__);
> return;
> }
> --
> 2.30.0
>
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2021-09-28 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 10:50 [PATCH] memblock: check memory total_size Peng Fan (OSS)
2021-09-28 16:37 ` Mike Rapoport [this message]
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=YVNE43IBP0iUmng5@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.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).