From: "Pierre-Clément Tosi" <ptosi@google.com>
To: Chris Packham <judge.packham@gmail.com>
Cc: u-boot@lists.denx.de, Bin Meng <bmeng.cn@gmail.com>,
Marc Zyngier <maz@kernel.org>, Peng Fan <peng.fan@nxp.com>,
Simon Glass <sjg@chromium.org>,
Will Deacon <willdeacon@google.com>, Ye Li <ye.li@nxp.com>,
"Ying-Chun Liu (PaulLiu)" <paul.liu@linaro.org>,
meitao <meitaogao@asrmicro.com>,
Alistair Delva <adelva@google.com>
Subject: Re: [PATCH 0/3] Revert HAFDBS changes
Date: Fri, 27 Oct 2023 10:49:47 +0100 [thread overview]
Message-ID: <20231027094947.bhtwngq26e3loya5@google.com> (raw)
In-Reply-To: <20231027002409.430285-1-judge.packham@gmail.com>
Hi Chris,
On Fri, Oct 27, 2023 at 01:23:51PM +1300, Chris Packham wrote:
> As discussed this series reverts the HAFDBS changes that caused an issue
> on AC5/AC5X. I think there are some improvements that can be made to the
> initial memory map for the AC5/AC5X but so far nothing I've found makes
> it compatible with the HAFDBS changes.
Would you mind briefly explaining what those issues are and/or point me to the
discussion where it was decided to revert these patches?
The feature is quite useful for users of CONFIG_CMO_BY_VA_ONLY, to speed up the
boot sequence: instead of reverting these patches altogether, would a reasonable
alternative be to put them behind a build option?
Also, could you confirm that the "initial memory map" you are referring to above
only describes actual memory as, IIRC, some boards were using mappings **much**
larger than their DRAM address space?
>
>
> Chris Packham (3):
> Revert "armv8: enable HAFDBS for other ELx when FEAT_HAFDBS is
> present"
> Revert "arm64: Use level-2 for largest block mappings when FEAT_HAFDBS
> is present"
> Revert "arm64: Use FEAT_HAFDBS to track dirty pages when available"
>
> arch/arm/cpu/armv8/cache_v8.c | 30 +++---------------------------
> arch/arm/include/asm/armv8/mmu.h | 20 ++++----------------
> arch/arm/include/asm/global_data.h | 2 --
> 3 files changed, 7 insertions(+), 45 deletions(-)
>
> --
> 2.42.0
>
--
Pierre
next prev parent reply other threads:[~2023-10-27 9:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 0:23 [PATCH 0/3] Revert HAFDBS changes Chris Packham
2023-10-27 0:23 ` [PATCH 1/3] Revert "armv8: enable HAFDBS for other ELx when FEAT_HAFDBS is present" Chris Packham
2023-11-17 19:42 ` Tom Rini
2023-10-27 0:23 ` [PATCH 2/3] Revert "arm64: Use level-2 for largest block mappings " Chris Packham
2023-11-17 19:42 ` Tom Rini
2023-10-27 0:23 ` [PATCH 3/3] Revert "arm64: Use FEAT_HAFDBS to track dirty pages when available" Chris Packham
2023-11-17 19:42 ` Tom Rini
2023-10-27 9:49 ` Pierre-Clément Tosi [this message]
2023-10-27 17:22 ` [PATCH 0/3] Revert HAFDBS changes Tom Rini
2023-11-09 21:33 ` Tom Rini
2023-11-10 5:38 ` Chris Packham
2023-11-17 19:41 ` 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=20231027094947.bhtwngq26e3loya5@google.com \
--to=ptosi@google.com \
--cc=adelva@google.com \
--cc=bmeng.cn@gmail.com \
--cc=judge.packham@gmail.com \
--cc=maz@kernel.org \
--cc=meitaogao@asrmicro.com \
--cc=paul.liu@linaro.org \
--cc=peng.fan@nxp.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=willdeacon@google.com \
--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