From: Andreas Schwab <schwab@suse.de>
To: Sughosh Ganu <sughosh.ganu@linaro.org>
Cc: u-boot@lists.denx.de, Heinrich Schuchardt <xypron.glpk@gmx.de>,
E Shattow <lucent@gmail.com>, Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH] lmb: prohibit allocations above ram_top even from same bank
Date: Mon, 02 Dec 2024 12:58:04 +0100 [thread overview]
Message-ID: <mvmfrn6mh4j.fsf@suse.de> (raw)
In-Reply-To: <20241202070624.1295497-1-sughosh.ganu@linaro.org> (Sughosh Ganu's message of "Mon, 2 Dec 2024 12:36:24 +0530")
On Dez 02 2024, Sughosh Ganu wrote:
> There are platforms which set the value of ram_top based on certain
> restrictions that the platform might have in accessing memory above
> ram_top, even when the memory region is in the same DRAM bank. So,
> even though the LMB allocator works as expected, when trying to
> allocate memory above ram_top, prohibit this by marking all memory
> above ram_top as reserved, even if the said memory region is from the
> same bank.
This fixes the boot failure on the VisionFive2 board as reported in
<mvm8qtnv310.fsf@suse.de>.
Tested-by: Andreas Schwab <schwab@suse.de>
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2024-12-02 11:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 7:06 [PATCH] lmb: prohibit allocations above ram_top even from same bank Sughosh Ganu
2024-12-02 11:58 ` Andreas Schwab [this message]
[not found] ` <CANV2PTNmUp013xDT1bqKYcyo=aP4NXtLN_u01pXmdNM417RygQ@mail.gmail.com>
2024-12-02 16:48 ` Sughosh Ganu
2024-12-07 15:57 ` Tom Rini
2024-12-11 16:18 ` Patrice CHOTARD
2024-12-11 16:27 ` Sughosh Ganu
2024-12-11 16:44 ` Patrice CHOTARD
2024-12-11 18:16 ` Sughosh Ganu
2024-12-12 8:23 ` Patrice CHOTARD
2024-12-12 12:33 ` Mark Kettenis
2024-12-12 13:32 ` Sughosh Ganu
2024-12-12 14:38 ` Mark Kettenis
2024-12-12 14:54 ` Sughosh Ganu
2024-12-12 23:21 ` Mark Kettenis
2024-12-12 13:23 ` Sughosh Ganu
2024-12-12 19:18 ` Tom Rini
2024-12-12 19:50 ` Sughosh Ganu
2024-12-13 9:13 ` Patrice CHOTARD
2024-12-13 9:54 ` Sughosh Ganu
2024-12-13 10:06 ` Patrice CHOTARD
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=mvmfrn6mh4j.fsf@suse.de \
--to=schwab@suse.de \
--cc=lucent@gmail.com \
--cc=sughosh.ganu@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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.