All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: Stefano Stabellini <stefanos@xilinx.com>,
	Achin.Gupta@arm.com, andrii_anisov@epam.com,
	xen-devel@lists.xen.org
Subject: Re: [PATCH v5 07/25] xen/arm: don't add duplicate boot modules, introduce domU flag
Date: Tue, 30 Oct 2018 11:50:11 +0000	[thread overview]
Message-ID: <866f291e-ceff-3f43-e101-a146d87f993c@arm.com> (raw)
In-Reply-To: <1540260184-11294-7-git-send-email-sstabellini@kernel.org>

Hi Stefano,

On 23/10/2018 03:02, Stefano Stabellini wrote:
> Don't add duplicate boot modules (same kind and same start address),
> they are freed later, we don't want to introduce double-free errors.
> 
> Introduce a domU flag in struct bootmodule and struct bootcmdline. Set
> it for kernels and ramdisks of "xen,domain" nodes to avoid getting
> confused in kernel_probe, where we try to guess which is the dom0 kernel
> and initrd to be compatible with all versions of the multiboot spec.
> 
> boot_module_find_by_kind and boot_cmdline_find_by_kind automatically
> check for !domU entries (they are only used for non-domU modules).
> 
> Signed-off-by: Stefano Stabellini <stefanos@xilinx.com>
> 
> ---
> Changes in v5:
> - improve commit message
> - add in-code comments
> 
> Changes in v4:
> - use unsigned int
> - better commit message
> - introduce domU flag and usage
> 
> Changes in v2:
> - new patch
> ---
>   xen/arch/arm/bootfdt.c      | 11 +++++++----
>   xen/arch/arm/setup.c        | 30 +++++++++++++++++++++++++-----
>   xen/include/asm-arm/setup.h | 12 ++++++++++--
>   3 files changed, 42 insertions(+), 11 deletions(-)
> 
> diff --git a/xen/arch/arm/bootfdt.c b/xen/arch/arm/bootfdt.c
> index cb6f77d..c325b6e 100644
> --- a/xen/arch/arm/bootfdt.c
> +++ b/xen/arch/arm/bootfdt.c
> @@ -175,6 +175,7 @@ static void __init process_multiboot_node(const void *fdt, int node,
>       int len = sizeof("/chosen");
>       char path[8]; /* sizeof "/chosen" */
>       int parent_node, ret;
> +    bool domU;
>   
>       parent_node = fdt_parent_offset(fdt, node);
>       ASSERT(parent_node >= 0);
> @@ -229,12 +230,14 @@ static void __init process_multiboot_node(const void *fdt, int node,
>               kind = BOOTMOD_XSM;
>       }
>   
> -    add_boot_module(kind, start, size);
> +    domU = fdt_node_check_compatible(fdt, parent_node, "xen,domain") == 0;
> +    add_boot_module(kind, start, size, domU);
>   
>       prop = fdt_get_property(fdt, node, "bootargs", &len);
>       if ( !prop )
>           return;
> -    add_boot_cmdline(fdt_get_name(fdt, parent_node, &len), prop->data, kind);
> +    add_boot_cmdline(fdt_get_name(fdt, parent_node, &len), prop->data,
> +                     kind, domU);
>   }
>   
>   static void __init process_chosen_node(const void *fdt, int node,
> @@ -280,7 +283,7 @@ static void __init process_chosen_node(const void *fdt, int node,
>   
>       printk("Initrd %"PRIpaddr"-%"PRIpaddr"\n", start, end);
>   
> -    add_boot_module(BOOTMOD_RAMDISK, start, end-start);
> +    add_boot_module(BOOTMOD_RAMDISK, start, end-start, false);
>   }
>   
>   static int __init early_scan_node(const void *fdt,
> @@ -351,7 +354,7 @@ size_t __init boot_fdt_info(const void *fdt, paddr_t paddr)
>       if ( ret < 0 )
>           panic("No valid device tree\n");
>   
> -    add_boot_module(BOOTMOD_FDT, paddr, fdt_totalsize(fdt));
> +    add_boot_module(BOOTMOD_FDT, paddr, fdt_totalsize(fdt), false);
>   
>       device_tree_for_each_node((void *)fdt, early_scan_node, NULL);
>       early_print_info();
> diff --git a/xen/arch/arm/setup.c b/xen/arch/arm/setup.c
> index 2098591..72b12f9 100644
> --- a/xen/arch/arm/setup.c
> +++ b/xen/arch/arm/setup.c
> @@ -201,10 +201,12 @@ void __init dt_unreserved_regions(paddr_t s, paddr_t e,
>   }
>   
>   struct bootmodule __init *add_boot_module(bootmodule_kind kind,
> -                                          paddr_t start, paddr_t size)
> +                                          paddr_t start, paddr_t size,
> +                                          bool domU)
>   {
>       struct bootmodules *mods = &bootinfo.modules;
>       struct bootmodule *mod;
> +    unsigned int i;
>   
>       if ( mods->nr_mods == MAX_MODULES )
>       {
> @@ -212,15 +214,29 @@ struct bootmodule __init *add_boot_module(bootmodule_kind kind,
>                  boot_module_kind_as_string(kind), start, start + size);
>           return NULL;
>       }
> +    for ( i = 0 ; i < mods->nr_mods ; i++ )
> +    {
> +        mod = &mods->module[i];
> +        if ( mod->kind == kind && mod->start == start )
> +        {
> +            if ( !domU )
> +                mod->domU = false;
> +            return mod;
> +        }
> +    }
>   
>       mod = &mods->module[mods->nr_mods++];
>       mod->kind = kind;
>       mod->start = start;
>       mod->size = size;
> +    mod->domU = domU;
>   
>       return mod;
>   }
>   
> +/*
> + * This function is only used to find dom0 modules, so check for !mod->domU

This comment is misleading. The function is used not only to find Dom0 Modules 
but also XSM & co.

How about:

"boot_module_find_by_kind can only be used to return Xen modules (e.g XSM, DTB) 
or Dom0 modules. This is not suitable for looking up for guest modules."

> + */
>   struct bootmodule * __init boot_module_find_by_kind(bootmodule_kind kind)
>   {
>       struct bootmodules *mods = &bootinfo.modules;
> @@ -229,14 +245,14 @@ struct bootmodule * __init boot_module_find_by_kind(bootmodule_kind kind)
>       for (i = 0 ; i < mods->nr_mods ; i++ )
>       {
>           mod = &mods->module[i];
> -        if ( mod->kind == kind )
> +        if ( mod->kind == kind && !mod->domU )
>               return mod;
>       }
>       return NULL;
>   }
>   
>   void __init add_boot_cmdline(const char *name, const char *cmdline,
> -                             bootmodule_kind kind)
> +                             bootmodule_kind kind, bool domU)
>   {
>       struct bootcmdlines *cmds = &bootinfo.cmdlines;
>       struct bootcmdline *cmd;
> @@ -249,6 +265,7 @@ void __init add_boot_cmdline(const char *name, const char *cmdline,
>   
>       cmd = &cmds->cmdline[cmds->nr_mods++];
>       cmd->kind = kind;
> +    cmd->domU = domU;
>   
>       ASSERT(strlen(name) <= DT_MAX_NAME);
>       safe_strcpy(cmd->dt_name, name);
> @@ -258,6 +275,9 @@ void __init add_boot_cmdline(const char *name, const char *cmdline,
>       safe_strcpy(cmd->cmdline, cmdline);
>   }
>   
> +/*
> + * This function is only used to find dom0 modules, so check for !mod->domU
> + */

Same here.

>   struct bootcmdline * __init boot_cmdline_find_by_kind(bootmodule_kind kind)
>   {
>       struct bootcmdlines *cmds = &bootinfo.cmdlines;
> @@ -267,7 +287,7 @@ struct bootcmdline * __init boot_cmdline_find_by_kind(bootmodule_kind kind)
>       for ( i = 0 ; i < cmds->nr_mods ; i++ )
>       {
>           cmd = &cmds->cmdline[i];
> -        if ( cmd->kind == kind )
> +        if ( cmd->kind == kind && !cmd->domU )
>               return cmd;
>       }
>       return NULL;
> @@ -761,7 +781,7 @@ void __init start_xen(unsigned long boot_phys_offset,
>       /* Register Xen's load address as a boot module. */
>       xen_bootmodule = add_boot_module(BOOTMOD_XEN,
>                                (paddr_t)(uintptr_t)(_start + boot_phys_offset),
> -                             (paddr_t)(uintptr_t)(_end - _start + 1));
> +                             (paddr_t)(uintptr_t)(_end - _start + 1), false);
>       BUG_ON(!xen_bootmodule);
>   
>       xen_paddr = get_xen_paddr();
> diff --git a/xen/include/asm-arm/setup.h b/xen/include/asm-arm/setup.h
> index 7580007..3a30329 100644
> --- a/xen/include/asm-arm/setup.h
> +++ b/xen/include/asm-arm/setup.h
> @@ -30,9 +30,16 @@ struct meminfo {
>       struct membank bank[NR_MEM_BANKS];
>   };
>   
> +/*
> + * The domU flag is set for kernels and ramdisks of "xen,domain" nodes.
> + * The purpose of the domU flag is to avoid getting confused in
> + * kernel_probe, where we try to guess which is the dom0 kernel and
> + * initrd to be compatible with all versions of the multiboot spec.
> + */
>   #define BOOTMOD_MAX_CMDLINE 1024
>   struct bootmodule {
>       bootmodule_kind kind;
> +    bool domU;
>       paddr_t start;
>       paddr_t size;
>   };
> @@ -41,6 +48,7 @@ struct bootmodule {
>   #define DT_MAX_NAME 41
>   struct bootcmdline {
>       bootmodule_kind kind;
> +    bool domU;
>       char dt_name[DT_MAX_NAME];
>       char cmdline[BOOTMOD_MAX_CMDLINE];
>   };
> @@ -91,10 +99,10 @@ size_t __init boot_fdt_info(const void *fdt, paddr_t paddr);
>   const char __init *boot_fdt_cmdline(const void *fdt);
>   
>   struct bootmodule *add_boot_module(bootmodule_kind kind,
> -                                   paddr_t start, paddr_t size);
> +                                   paddr_t start, paddr_t size, bool domU);
>   struct bootmodule *boot_module_find_by_kind(bootmodule_kind kind);
>   void add_boot_cmdline(const char *name, const char *cmdline,
> -                      bootmodule_kind kind);
> +                      bootmodule_kind kind, bool domU);
>   struct bootcmdline *boot_cmdline_find_by_kind(bootmodule_kind kind);
>   const char * __init boot_module_kind_as_string(bootmodule_kind kind);
>   
> 

Cheers,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-10-30 11:50 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23  2:02 [PATCH v5 00/25] dom0less step1: boot multiple domains from device tree Stefano Stabellini
2018-10-23  2:02 ` [PATCH v5 01/25] xen: allow console_io hypercalls from certain DomUs Stefano Stabellini
2018-10-23  2:02 ` [PATCH v5 02/25] xen/arm: extend device tree based multiboot protocol Stefano Stabellini
2018-10-23  2:02 ` [PATCH v5 03/25] xen/arm: document dom0less Stefano Stabellini
2018-10-23  2:02 ` [PATCH v5 04/25] xen/arm: increase MAX_MODULES Stefano Stabellini
2018-10-23  2:02 ` [PATCH v5 05/25] xen/arm: check for multiboot nodes only under /chosen Stefano Stabellini
2018-10-26 19:25   ` Julien Grall
2018-10-26 21:12     ` Stefano Stabellini
2018-10-26 21:27       ` Julien Grall
2018-10-26 21:32         ` Julien Grall
2018-10-27  0:42           ` Stefano Stabellini
2018-10-28 17:28             ` Julien Grall
2018-10-23  2:02 ` [PATCH v5 06/25] xen/arm: introduce bootcmdlines Stefano Stabellini
2018-10-26 19:44   ` Julien Grall
2018-10-27  0:34     ` Stefano Stabellini
2018-10-23  2:02 ` [PATCH v5 07/25] xen/arm: don't add duplicate boot modules, introduce domU flag Stefano Stabellini
2018-10-30 11:50   ` Julien Grall [this message]
2018-11-02 20:15     ` Stefano Stabellini
2018-10-23  2:02 ` [PATCH v5 08/25] xen/arm: probe domU kernels and initrds Stefano Stabellini
2018-10-30 12:03   ` Julien Grall
2018-11-02 20:41     ` Stefano Stabellini
2018-10-23  2:02 ` [PATCH v5 09/25] xen/arm: rename get_11_allocation_size to get_allocation_size Stefano Stabellini
2018-10-23  2:02 ` [PATCH v5 10/25] xen/arm: rename allocate_memory to allocate_memory_11 Stefano Stabellini
2018-10-23  2:02 ` [PATCH v5 11/25] xen/arm: introduce allocate_memory Stefano Stabellini
2018-10-30 12:24   ` Julien Grall
2018-11-02 22:20     ` Stefano Stabellini
2018-10-30 20:56   ` Julien Grall
2018-11-02 21:15     ` Stefano Stabellini
2018-10-23  2:02 ` [PATCH v5 12/25] xen/arm: refactor construct_dom0 Stefano Stabellini
2018-10-30 16:32   ` Julien Grall
2018-10-23  2:02 ` [PATCH v5 13/25] xen/arm: move unregister_init_virtual_region to init_done Stefano Stabellini
2018-10-30 16:33   ` Julien Grall
2018-10-23  2:02 ` [PATCH v5 14/25] xen/arm: introduce create_domUs Stefano Stabellini
2018-10-30 16:38   ` Julien Grall
2018-10-23  2:02 ` [PATCH v5 15/25] xen/arm: implement construct_domU Stefano Stabellini
2018-10-30 20:56   ` Julien Grall
2018-10-23  2:02 ` [PATCH v5 16/25] xen/arm: generate a simple device tree for domUs Stefano Stabellini
2018-10-23  2:02 ` [PATCH v5 17/25] xen/arm: make set_interrupt_ppi able to handle non-PPI Stefano Stabellini
2018-10-23  2:02 ` [PATCH v5 18/25] xen/arm: generate vpl011 node on device tree for domU Stefano Stabellini
2018-10-30 20:58   ` Julien Grall
2018-10-23  2:02 ` [PATCH v5 19/25] xen/arm: introduce a union in vpl011 Stefano Stabellini
2018-10-23  2:02 ` [PATCH v5 20/25] xen/arm: refactor vpl011_data_avail Stefano Stabellini
2018-10-23  2:03 ` [PATCH v5 21/25] xen: support console_switching between Dom0 and DomUs on ARM Stefano Stabellini
2018-10-24 14:55   ` Oleksandr Andrushchenko
2018-10-29 20:00     ` Stefano Stabellini
2018-10-29 20:01       ` Julien Grall
2018-10-26 14:29   ` Jan Beulich
2018-10-29 19:56     ` Stefano Stabellini
2018-10-23  2:03 ` [PATCH v5 22/25] xen/arm: Allow vpl011 to be used by DomU Stefano Stabellini
2018-10-24 17:14   ` Oleksandr Tyshchenko
2018-10-29 20:03     ` Stefano Stabellini
2018-10-30 11:04       ` Oleksandr Tyshchenko
2018-10-23  2:03 ` [PATCH v5 23/25] xen/vpl011: buffer out chars when the backend is xen Stefano Stabellini
2018-10-24 14:46   ` Oleksandr Andrushchenko
2018-10-29 20:09     ` Stefano Stabellini
2018-10-31 13:27   ` Julien Grall
2018-10-23  2:03 ` [PATCH v5 24/25] xen/arm: move kernel.h to asm-arm/ Stefano Stabellini
2018-10-31 13:28   ` Julien Grall
2018-10-23  2:03 ` [PATCH v5 25/25] xen/arm: split domain_build.c Stefano Stabellini
2018-10-31 13:44   ` Julien Grall
2018-11-01 20:37     ` Stefano Stabellini

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=866f291e-ceff-3f43-e101-a146d87f993c@arm.com \
    --to=julien.grall@arm.com \
    --cc=Achin.Gupta@arm.com \
    --cc=andrii_anisov@epam.com \
    --cc=sstabellini@kernel.org \
    --cc=stefanos@xilinx.com \
    --cc=xen-devel@lists.xen.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.