From: Shawn Guo <shawn.guo@linaro.org>
To: "Marc Zyngier" <maz@kernel.org>,
"Pierre-Clément Tosi" <ptosi@google.com>,
"Ying-Chun Liu" <paul.liu@linaro.org>
Cc: Alexander Graf <agraf@csgraf.de>, Tom Rini <trini@konsulko.com>,
u-boot@lists.denx.de
Subject: Regression caused by "arm64: Reduce PT size estimation complexity"
Date: Fri, 24 Oct 2025 12:15:24 +0800 [thread overview]
Message-ID: <aPr9XCyh62ULrY7U@dragon> (raw)
Hi folks,
While commit 94d30f476fe1 ("arm64: Reduce PT size estimation complexity")
speeds up the PT size calculation, it seems the result size becomes
unnecessarily bigger than before. For example, on my device, the
original count_required_pts() returns 6 for get_page_table_size(),
while count_ranges() returns 14 now. That said, the PT size returned by
get_page_table_size() eventually becomes 64 KiB bigger than before.
This is too much for my device which sets up PT on SRAM, and causing
a regression here.
Could you guys take a look and see whether we can get PT size
calculation speedy *and* compact? :)
Thanks,
Shawn
reply other threads:[~2025-10-24 4:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=aPr9XCyh62ULrY7U@dragon \
--to=shawn.guo@linaro.org \
--cc=agraf@csgraf.de \
--cc=maz@kernel.org \
--cc=paul.liu@linaro.org \
--cc=ptosi@google.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox