> On 13 Jan 2023, at 10:11, Julien Grall <jul...@xen.org> wrote: > > From: Julien Grall <jgr...@amazon.com> > > At the moment, the temporary mapping is only used when the virtual > runtime region of Xen is clashing with the physical region. > > In follow-up patches, we will rework how secondary CPU bring-up works > and it will be convenient to use the fixmap area for accessing > the root page-table (it is per-cpu). > > Rework the code to use temporary mapping when the Xen physical address > is not overlapping with the temporary mapping. > > This also has the advantage to simplify the logic to identity map > Xen. > > Signed-off-by: Julien Grall <jgr...@amazon.com> > > ----
Reviewed-by: Luca Fancellu <luca.fance...@arm.com> I’ve also built for arm32 and test this patch on fvp aarch32 mode, booting Dom0 and creating/running/destroying some guests Tested-by: Luca Fancellu <luca.fance...@arm.com>
