On 02/08/2024 14:27, Julien Grall wrote:
Hi,
Hi Julien,
On 02/08/2024 13:14, Ayan Kumar Halder wrote:
From: Penny Zheng <penny.zh...@arm.com>
VMAP is widely used in ALTERNATIVE feature, CPUERRATA feature, etc to
remap a range of memory with new memory attributes. Since this is
highly dependent on virtual address translation, we choose to fold VMAP
in MMU system.
In this patch, we introduce a new Kconfig CONFIG_HAS_VMAP, and make it
only support in MMU system on ARM architecture. And we make features
like ALTERNATIVE, CPUERRATA, etc, now depend on VMAP.
While I agree that alternative should depend on VMAP (for now), I feel
this is incorrect for CPUERRATA. Very likely, you will need to deal
with them on the MPU.
Before making any suggestion, would you be able to clarify how you
envision to deal with errata? Will they be selected at built time or
boot time?
TBH, I hadn't thought that through. I am thinking about selecting them
at built time (like it is been done for Arm64 cpus).
However given that there are lesser number of MPU cpus (only R52 and
R82) compared to MMU ones, could there be a simpler approach.
I am open to any suggestions you have.
Also, can we disable the CPUERRATA on MPU until we add support for the
first errata ?
- Ayan
Cheers,
