Julien Grall writes:
> initrd_load() can be called by other domain than dom0. To avoid
> confusion in the log, print the correct domain.
>
> Signed-off-by: Julien Grall <julien.gr...@arm.com>
Reviewed-by: Volodymyr Babchuk <volodymyr_babc...@epam.com>
But why didn't you gathered all those patches into one patch series?
> ---
> xen/arch/arm/domain_build.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c
> index 126374f603..33171081ea 100644
> --- a/xen/arch/arm/domain_build.c
> +++ b/xen/arch/arm/domain_build.c
> @@ -1818,8 +1818,8 @@ static void __init initrd_load(struct kernel_info
> *kinfo)
> paddr = mod->start;
> len = mod->size;
>
> - printk("Loading dom0 initrd from %"PRIpaddr" to
> 0x%"PRIpaddr"-0x%"PRIpaddr"\n",
> - paddr, load_addr, load_addr + len);
> + printk("Loading %pd initrd from %"PRIpaddr" to
> 0x%"PRIpaddr"-0x%"PRIpaddr"\n",
> + kinfo->d, paddr, load_addr, load_addr + len);
>
> /* Fix up linux,initrd-start and linux,initrd-end in /chosen */
> node = fdt_path_offset(kinfo->fdt, "/chosen");
--
Volodymyr Babchuk at EPAM
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
