Re: [PATCH 08/15] x86/PVH: split pvh_setup_acpi()

[Roger Pau Monné <roger@xxxxxxxxxxxxxx>]

On Mon, Oct 12, 2026 at 10:23:16AM +0200, Jan Beulich wrote:
> All E820 manipulations want to happen before the initrd is placed, or else
> pvh_steal_ram() may steal from the tail part of it. As a second step,
> split placing ACPI data from actually populating it.

Would it be less intrusive to duplicate the memory map (like it's done
in a change ahead of this one), and subtract the kernel and initrd
region from that memory map, then use it as the basis for
pvh_steal_ram()?

We could adjust/replace pvh_add_mem_range() so it allows changing
regions from RAM to other types.  That would seem to be less churn
overall.  Maybe you did already consider this and found further
problem with this approach that I'm failing to see?

Thanks, Roger.