All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <ian.campbell@citrix.com>, xen-devel@lists.xen.org
Cc: ian.jackson@eu.citrix.com, tim@xen.org, stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH v4 7/9] tools: arm: prepare guest FDT building for multiple RAM banks
Date: Tue, 13 May 2014 13:35:09 +0100	[thread overview]
Message-ID: <5372117D.2060903@linaro.org> (raw)
In-Reply-To: <1399980574-12515-7-git-send-email-ian.campbell@citrix.com>

Hi Ian,

On 05/13/2014 12:29 PM, Ian Campbell wrote:
> This required exposing the sizes of the banks determined by the domain builder
> up to libxl via xc_dom_image.
> 
> Since the domain build needs to know the size of the DTB we create placeholder
> nodes for each possible bank and when we finialise the DTB we fill in the ones

finalise

> which are actually populated and NOP out the rest.

It's annoying that we can't dissociate bank setup (i.e defining the size
of each banks) and placing modules (kernel, DTB,...).

It would avoid to have 2 step to create memory node.

Anyway, I'm fine with this solution for now.

[..]

>  int libxl__arch_domain_finalise_hw_description(libxl__gc *gc,
>                                                 libxl_domain_build_info *info,
>                                                 struct xc_dom_image *dom)
>  {
>      void *fdt = dom->devicetree_blob;
> +    int i;
> +    const uint64_t bankbase[GUEST_RAM_BANKS] = {
> +        GUEST_RAM0_BASE
> +    };

You've duplicate this variable in multiple place (twice in libxl and
once in libxc).

I think it's better if we can avoid duplicating this variable, maybe by
storing in xc_dom_image?

>  
>      const struct xc_dom_seg *ramdisk = dom->ramdisk_blob ?
>          &dom->ramdisk_seg : NULL;
> @@ -552,9 +588,16 @@ int libxl__arch_domain_finalise_hw_description(libxl__gc *gc,
>          assert(!res);
>  
>          val = cpu_to_fdt64(ramdisk->vend);
> -        res = fdt_setprop_inplace(fdt, chosen,PROP_INITRD_END,
> +        res = fdt_setprop_inplace(fdt, chosen, PROP_INITRD_END,
>                                    &val, sizeof(val));

Spurious change?

Regards,

-- 
Julien Grall

  reply	other threads:[~2014-05-13 12:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 11:28 [PATCH v4 0/9] xen: arm: support up to (almost) 1TB of guest RAM Ian Campbell
2014-05-13 11:29 ` [PATCH v4 1/9] tools: libxl: use uint64_t not unsigned long long for addresses Ian Campbell
2014-05-13 11:29 ` [PATCH v4 2/9] tools: arm: report an error if the guest RAM is too large Ian Campbell
2014-05-13 11:29 ` [PATCH v4 3/9] tools: arm: move magic pfns out of guest RAM region Ian Campbell
2014-05-13 11:29 ` [PATCH v4 4/9] tools: arm: rearrange guest physical address space to increase max RAM Ian Campbell
2014-05-13 11:29 ` [PATCH v4 5/9] tools: arm: refactor code to setup guest p2m and fill it with RAM Ian Campbell
2014-05-13 11:29 ` [PATCH v4 6/9] tools: arm: prepare domain builder for multiple banks of guest RAM Ian Campbell
2014-05-13 12:21   ` Julien Grall
2014-05-13 11:29 ` [PATCH v4 7/9] tools: arm: prepare guest FDT building for multiple RAM banks Ian Campbell
2014-05-13 12:35   ` Julien Grall [this message]
2014-05-15 11:27     ` Ian Campbell
2014-05-13 11:29 ` [PATCH v4 8/9] tools: arm: support up to (almost) 1TB of guest RAM Ian Campbell
2014-05-13 11:29 ` [PATCH v4 9/9] tools: arm: increase size of region set aside for guest grant table Ian Campbell

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=5372117D.2060903@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --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.