From: "Roger Pau Monné" <roger@xenproject.org>
To: Jan Beulich <jbeulich@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Teddy Astie <teddy.astie@vates.tech>
Subject: Re: [PATCH 06/15] x86/PVH: keep a copy of Dom0's initial E820 map
Date: Tue, 13 Oct 2026 15:48:10 +0200 [thread overview]
Message-ID: <as42mhs42tvU9XIL@Mac.lan> (raw)
In-Reply-To: <575ec1bc-764c-4016-a584-a79e57817d9a@suse.com>
On Mon, Oct 12, 2026 at 10:21:55AM +0200, Jan Beulich wrote:
> pvh_populate_p2m() needs to populate RAM according to the initial map
> established, prior to any stealing by pvh_steal_ram(). Subsequently the
> invocations of those functions will (need to) move ahead of
> pvh_populate_p2m(), so what to act on is no longer Dom0's memory map at
> the time of invocation.
But (most of?) the uses of pvh_steal_ram() expect to access the stolen
RAM, and hence using pvh_steal_ram() ahead of pvh_populate_p2m() is
not a present use-case?
I assume you have a further use-case for pvh_steal_ram() that wants to
steal a range before it's populated, which might be worth mentioning
here, to add a bit more context?
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> --- a/xen/arch/x86/hvm/dom0_build.c
> +++ b/xen/arch/x86/hvm/dom0_build.c
> @@ -13,6 +13,7 @@
> #include <xen/multiboot.h>
> #include <xen/pci.h>
> #include <xen/softirq.h>
> +#include <xen/xvmalloc.h>
>
> #include <acpi/actables.h>
>
> @@ -413,7 +414,10 @@ static void __init pvh_init_p2m(struct d
> } while ( preempted );
> }
>
> -static int __init pvh_populate_p2m(struct domain *d)
> +static int __init pvh_populate_p2m(
> + struct domain *d,
> + const struct e820entry *e820,
> + unsigned int nr_e820)
> {
> struct vcpu *v = d->vcpu[0];
> unsigned int i;
> @@ -421,15 +425,15 @@ static int __init pvh_populate_p2m(struc
> #define MB1_PAGES PFN_DOWN(MB(1))
>
> /* Populate memory map. */
> - for ( i = 0; i < d->arch.nr_e820; i++ )
> + for ( i = 0; i < nr_e820; i++ )
> {
> unsigned long addr, size;
>
> - if ( d->arch.e820[i].type != E820_RAM )
> + if ( e820[i].type != E820_RAM )
> continue;
>
> - addr = PFN_DOWN(d->arch.e820[i].addr);
> - size = PFN_DOWN(d->arch.e820[i].size);
> + addr = PFN_DOWN(e820[i].addr);
> + size = PFN_DOWN(e820[i].size);
>
> rc = pvh_populate_memory_range(d, addr, size);
> if ( rc )
> @@ -438,11 +442,11 @@ static int __init pvh_populate_p2m(struc
> if ( addr < MB1_PAGES )
> {
> uint64_t end = min_t(uint64_t, MB(1),
> - d->arch.e820[i].addr + d->arch.e820[i].size);
> + e820[i].addr + e820[i].size);
> enum hvm_translation_result res =
> hvm_copy_to_guest_phys(mfn_to_maddr(_mfn(addr)),
> mfn_to_virt(addr),
> - end - d->arch.e820[i].addr,
> + end - e820[i].addr,
> v);
>
> if ( res != HVMTRANS_okay )
> @@ -1352,6 +1356,8 @@ int __init dom0_construct_pvh(const stru
> paddr_t entry, start_info;
> struct domain *d = bd->d;
> struct elf_binary elf;
> + struct e820entry *orig_e820;
> + unsigned int nr_orig_e820;
> int rc;
>
> printk(XENLOG_INFO "*** Building a PVH Dom%d ***\n", d->domain_id);
> @@ -1389,6 +1395,15 @@ int __init dom0_construct_pvh(const stru
>
> iommu_hwdom_init(d);
>
> + nr_orig_e820 = d->arch.nr_e820;
> + orig_e820 = xvmalloc_array(struct e820entry, nr_orig_e820);
> + if ( !orig_e820 )
> + {
> + printk("No memory for copy of E820 map (%u entries)\n", nr_orig_e820);
For some of the printks during dom0 PVH construction we already print
the domain (%pd), and I think it would be good to print it here also.
Some not-yet-upstream uses (hyperlaunch) create several domains using
this logic, it would be good to easily spot which domain triggered the
errors.
Thanks, Roger.
next prev parent reply other threads:[~2026-10-13 13:48 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 8:17 [PATCH 00/15] x86: PVH Dom0 loading rework Jan Beulich
2026-10-12 8:19 ` [PATCH 01/15] x86/EFI: guard against oversized modules Jan Beulich
2026-10-12 10:12 ` George Dunlap
2026-10-12 8:19 ` [PATCH 02/15] x86/PV: make better use of assign_pages() Jan Beulich
2026-10-12 10:16 ` George Dunlap
2026-10-12 8:20 ` [PATCH 03/15] x86/setup: break out E820_RAM accumulation Jan Beulich
2026-10-12 10:20 ` George Dunlap
2026-10-12 10:23 ` Jan Beulich
2026-10-12 11:24 ` George Dunlap
2026-10-13 11:05 ` Roger Pau Monné
2026-10-13 11:39 ` Jan Beulich
2026-10-12 8:20 ` [PATCH 04/15] x86/setup: special treatment of initrd for PVH Dom0 Jan Beulich
2026-10-12 11:23 ` George Dunlap
2026-10-12 11:51 ` Jan Beulich
2026-10-12 18:58 ` George Dunlap
2026-10-12 8:21 ` [PATCH 05/15] x86/PVH: split pvh_load_kernel() Jan Beulich
2026-10-13 6:45 ` Teddy Astie
2026-10-12 8:21 ` [PATCH 06/15] x86/PVH: keep a copy of Dom0's initial E820 map Jan Beulich
2026-10-13 6:57 ` Teddy Astie
2026-10-13 7:56 ` Jan Beulich
2026-10-13 13:48 ` Roger Pau Monné [this message]
2026-10-13 14:53 ` Jan Beulich
2026-10-13 15:08 ` Roger Pau Monné
2026-10-12 8:22 ` [PATCH 07/15] x86/PVH: lift E820 alignment requirement Jan Beulich
2026-10-13 14:59 ` Roger Pau Monné
2026-10-13 15:13 ` Jan Beulich
2026-10-12 8:23 ` [PATCH 08/15] x86/PVH: split pvh_setup_acpi() Jan Beulich
2026-10-13 15:52 ` Roger Pau Monné
2026-10-13 16:04 ` Jan Beulich
2026-10-12 8:24 ` [PATCH 09/15] x86/PVH: split pvh_setup_vmx_realmode_helpers() Jan Beulich
2026-10-12 8:24 ` [PATCH 10/15] x86/PVH: convert find_memory() to using a rangeset Jan Beulich
2026-10-12 8:25 ` [PATCH 11/15] x86/PVH: try to map initrd directly into Dom0 Jan Beulich
2026-10-12 8:25 ` [PATCH 12/15] x86/PVH: heed the kernel in pvh_steal_ram() Jan Beulich
2026-10-12 8:26 ` [PATCH 13/15] x86/PVH: prefer smaller E820 regions for stealing from Jan Beulich
2026-10-12 8:26 ` [PATCH 14/15] x86/PVH: log Dom0's E820 map earlier Jan Beulich
2026-10-12 8:26 ` [PATCH 15/15] x86/PVH: simplify writing of Dom0's RSDP Jan Beulich
2026-10-12 8:29 ` [PATCH 00/15] x86: PVH Dom0 loading rework Jan Beulich
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=as42mhs42tvU9XIL@Mac.lan \
--to=roger@xenproject.org \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=teddy.astie@vates.tech \
--cc=xen-devel@lists.xenproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.