From: Wolfgang Denk <wd@denx.de>
To: Tom Rini <trini@konsulko.com>
Cc: Ye Li <ye.li@nxp.com>, "marex@denx.de" <marex@denx.de>,
"swarren@nvidia.com" <swarren@nvidia.com>,
"hai.pham.ud@renesas.com" <hai.pham.ud@renesas.com>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
"simon.k.r.goldschmidt@gmail.com"
<simon.k.r.goldschmidt@gmail.com>,
"lokeshvutla@ti.com" <lokeshvutla@ti.com>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>
Subject: Re: [EXT] Re: [PATCH] Revert "arm: bootm: Disable LMB reservation for command line and board info on arm64"
Date: Mon, 09 Aug 2021 16:11:36 +0200 [thread overview]
Message-ID: <433360.1628518296@gemini.denx.de> (raw)
In-Reply-To: <20210809131640.GN858@bill-the-cat>
Dear Tom,
In message <20210809131640.GN858@bill-the-cat> you wrote:
>
> Thanks for explaining. It sounds like
> arch/arm/mach-imx/imx8m/soc.c::the=A0ft_system_setup() needs a comment
> that it uses a lot of stack, due to how complex it is, and that
I think this is the wrong approach. It sounds as if we were
discouragin the use of the stack for dynamic buffers etc. We should
not do that. Instead, we should make sure that the stack starts
below any reserved memory locations, and is free to grow downward as
long as there is still memory available.
If U-Boot was an OS, we would probably think about implementing a
more complex memory management utilizing the MMU, but in a boot
loader this is clearly overkill. But please, just let the stack
grow as it wants.
There may be completely legal use cases with unpredictable stack
requirements. Think about recursive shell scripts, for example...
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"Remember, Information is not knowledge; Knowledge is not Wisdom;
Wisdom is not truth; Truth is not beauty; Beauty is not love; Love is
not music; Music is the best." - Frank Zappa
next prev parent reply other threads:[~2021-08-09 14:11 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 7:22 [PATCH] Revert "arm: bootm: Disable LMB reservation for command line and board info on arm64" Jan Kiszka
2021-07-29 15:01 ` Marek Vasut
2021-07-29 15:23 ` Tom Rini
2021-07-29 16:47 ` Marek Vasut
2021-07-29 16:58 ` Tom Rini
2021-08-02 0:54 ` Marek Vasut
2021-08-02 9:37 ` Jan Kiszka
2021-08-02 10:48 ` Marek Vasut
2021-08-02 11:36 ` Jan Kiszka
2021-08-02 11:38 ` Marek Vasut
2021-08-02 11:54 ` Jan Kiszka
2021-08-02 13:04 ` Tom Rini
2021-08-02 14:03 ` Jan Kiszka
2021-08-02 14:27 ` Tom Rini
2021-08-02 14:34 ` Jan Kiszka
2021-08-02 14:44 ` Tom Rini
2021-08-05 21:52 ` Marek Vasut
2021-08-06 16:43 ` Tom Rini
2021-08-02 13:00 ` Tom Rini
2021-08-05 21:53 ` Marek Vasut
2021-08-05 23:31 ` Tom Rini
2021-08-08 13:35 ` Marek Vasut
2021-08-02 21:27 ` Tom Rini
2021-08-03 21:51 ` Tom Rini
2021-08-05 22:22 ` Marek Vasut
2021-08-06 16:49 ` Tom Rini
2021-08-08 13:45 ` Marek Vasut
2021-08-08 14:00 ` Tom Rini
2021-08-08 14:28 ` Marek Vasut
2021-08-08 14:54 ` Tom Rini
2021-08-08 15:25 ` Marek Vasut
2021-08-08 15:57 ` Tom Rini
2021-08-09 7:34 ` [EXT] " Ye Li
2021-08-09 13:16 ` Tom Rini
2021-08-09 14:11 ` Wolfgang Denk [this message]
2021-08-09 14:21 ` Tom Rini
2021-08-09 6:44 ` Wolfgang Denk
2021-08-09 12:53 ` Tom Rini
2021-08-08 18:21 ` Tom Rini
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=433360.1628518296@gemini.denx.de \
--to=wd@denx.de \
--cc=hai.pham.ud@renesas.com \
--cc=jan.kiszka@siemens.com \
--cc=lokeshvutla@ti.com \
--cc=marex@denx.de \
--cc=simon.k.r.goldschmidt@gmail.com \
--cc=swarren@nvidia.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=ye.li@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