Re: [v2 3/4] xen/arm: Rework the code mapping Xen to avoid relying on the size of Xen

[Julien Grall <julien@xxxxxxx>]

Hi,

On 30/06/2023 07:56, Michal Orzel wrote:
> On 29/06/2023 22:11, Julien Grall wrote:
> > From: Julien Grall <jgrall@xxxxxxxxxx>
> >
> > At the moment, the maximum size of Xen binary we can support is 2MB.
> > This is what we reserved in the virtual address but also what all
> > the code in Xen relies on as we only allocate one L3 page-table.
> >
> > When feature like UBSAN (will be enabled in a follow-up patch) and GCOV
> > are enabled, the binary will be way over 2MB.
> >
> > The code is now reworked so it doesn't rely on a specific size but
> > will instead look at the reversed size and compute the number of
> > page-table to allocate/map.
> >
> > While at it, replace any reference to 4KB mappings with a more
> > generic word because the page-size may change in the future.
> >
> > Also fix the typo s/tlb/tbl/ in code move in arm32/head.S
> as well as in arm64 (can be done on commit)
I have replaced "arm32/head.S" with "arm{32,64}/head.S".

> > Signed-off-by: Julien Grall <jgrall@xxxxxxxxxx>
> Reviewed-by: Michal Orzel <michal.orzel@xxxxxxx>
Thanks!

Cheers,

--
Julien Grall