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 <ian.jackson@eu.citrix.com>,
	tim@xen.org, stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH v5 19/19] libxl: build a device tree for ARM guests
Date: Thu, 14 Nov 2013 01:04:29 +0000	[thread overview]
Message-ID: <5284219D.3060503@linaro.org> (raw)
In-Reply-To: <1384366285-29277-19-git-send-email-ian.campbell@citrix.com>



On 11/13/2013 06:11 PM, Ian Campbell wrote:
> Uses xc_dom_devicetree_mem which was just added. The call to this needs to be
> carefully sequenced to be after xc_dom_parse_image (so we can tell which kind
> of guest we are building, although we don't use this yet) and before
> xc_dom_mem_init which tries to decide where to place the FDT in guest RAM.
>
> Removes libxl_noarch which would only have been used by IA64 after this
> change. Remove IA64 as part of this patch.
>
> There is no attempt to expose this as a configuration setting for the user.
>
> Includes a debug hook to dump the dtb to a file for inspection.
>
> TODO:
> - v7 CPU compat is hardcoded to cortex-a15 -- may need to define something more
>    generic via mach-virt dt bindngs?
>
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> Cc: Ian Jackson <ian.jackson@eu.citrix.com>
> ---
> v5: Correct error handling in debug_dump_fdt
> v4: Drop spurious comment in header
>      s/__be32/be32/ and s/gic_interrupt_t/gic_interrupt/ to avoid reserved names
>      Coding style fixes
>      Use GCSPRINTF
>      use for(;;) around FDT creation loop, undef FDT when done
>      use libxl__realloc for fdt size increase
>      Refactor debug dump into its own function, remove NDEBUG ifdef
> v2: base addresses, irq, evtchn etc stuff is now from public API headers,
>      avoiding the need to introduce domctls etc until we want to make them
>      dynamic.
>      fix memory node
>      Improve libfdt error handling, especially for FDT_ERR_NOSPACE.
>      Derive guest CPU and timer compatiblity nodes from the guest type.
>
> wip
> ---
>   tools/libxl/Makefile       |    6 +-
>   tools/libxl/libxl_arch.h   |    3 +
>   tools/libxl/libxl_arm.c    |  512 ++++++++++++++++++++++++++++++++++++++++++++
>   tools/libxl/libxl_dom.c    |    4 +
>   tools/libxl/libxl_noarch.c |    8 -
>   tools/libxl/libxl_x86.c    |    7 +
>   6 files changed, 530 insertions(+), 10 deletions(-)
>   create mode 100644 tools/libxl/libxl_arm.c
>   delete mode 100644 tools/libxl/libxl_noarch.c
>

[..]

> +    for (;;) {
> +next_resize:
> +        if (fdt_size) {
> +            fdt_size <<= 1;
> +            LOG(DEBUG, "Increasing FDT size to %zd and retrying", fdt_size);
> +        } else {
> +            fdt_size = 4096;
> +        }
> +
> +        fdt = libxl__realloc(gc, fdt, fdt_size);
> +
> +        FDT( fdt_create(fdt, fdt_size) );
> +
> +        FDT( fdt_finish_reservemap(fdt) );
> +
> +        FDT( fdt_begin_node(fdt, "") );
> +
> +        FDT( make_root_properties(gc, vers, fdt) );
> +        FDT( make_chosen_node(gc, fdt, info) );
> +        FDT( make_cpus_node(gc, fdt, info->max_vcpus, ainfo) );
> +        FDT( make_psci_node(gc, fdt) );
> +
> +        FDT( make_memory_node(gc, fdt,
> +                              dom->rambase_pfn << XC_PAGE_SHIFT,
> +                              info->target_memkb * 1024) );
> +        FDT( make_intc_node(gc, fdt,
> +                            GUEST_GICD_BASE, GUEST_GICD_SIZE,
> +                            GUEST_GICC_BASE, GUEST_GICD_SIZE) );
> +
> +        FDT( make_timer_node(gc, fdt, ainfo) );
> +        FDT( make_hypervisor_node(gc, fdt, vers) );
> +
> +        FDT( fdt_end_node(fdt) );
> +
> +        FDT( fdt_finish(fdt) );
> +        break;
> +    }
> +#undef FDT

Why didn't you try to use fdt_open_into? It should fit our usage: ie, 
grow up the size of the device tree. Actually, DTC uses this solution 
when the fdt needs to be resized.

-- 
Julien Grall

  parent reply	other threads:[~2013-11-14  1:04 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13 18:10 [PATCH v5 00/17] xen: arm: 64-bit guest support and domU FDT autogeneration Ian Campbell
2013-11-13 18:11 ` [PATCH v5 01/19] HACK Ian Campbell
2013-11-13 18:15   ` Julien Grall
2013-11-13 20:15     ` Ian Campbell
2013-11-13 18:11 ` [PATCH v5 02/19] xen: arm: drop LDFLAGS_DIRECT emulation specification Ian Campbell
2013-11-13 21:26   ` Julien Grall
2013-11-14  8:16     ` Ian Campbell
2013-11-13 18:11 ` [PATCH v5 03/19] xen: update config.{sub, guess} for arm64 Ian Campbell
2013-11-13 18:11 ` [PATCH v5 04/19] xen: arm: Report aarch64 capability Ian Campbell
2013-11-13 18:11 ` [PATCH v5 05/19] xen: arm: Add comment regard arm64 zImage v0 vs v1 Ian Campbell
2013-11-13 18:11 ` [PATCH v5 06/19] xen: arm: move dom0 gic and timer device tree nodes under /xen/ Ian Campbell
2013-11-13 18:28   ` Stefano Stabellini
2013-11-13 20:18     ` Ian Campbell
2013-11-14 12:22       ` Stefano Stabellini
2013-11-19  9:52         ` Ian Campbell
2013-11-13 21:31   ` Julien Grall
2013-11-14  8:18     ` Ian Campbell
2013-11-13 18:11 ` [PATCH v5 07/19] xen: arm: allocate dom0 memory separately from preparing the dtb Ian Campbell
2013-11-13 19:21   ` Stefano Stabellini
2013-11-13 20:18     ` Ian Campbell
2013-11-14 12:22       ` Stefano Stabellini
2013-11-13 21:34   ` Julien Grall
2013-11-14  8:23     ` Ian Campbell
2013-11-14  0:52   ` Julien Grall
2013-11-14  8:25     ` Ian Campbell
2013-11-13 18:11 ` [PATCH v5 08/19] xen: arm: add enable-method to cpu nodes for arm64 guests Ian Campbell
2013-11-13 18:11 ` [PATCH v5 09/19] xen: arm: include header for for arch_do_{sys, dom}ctl prototype Ian Campbell
2013-11-13 18:11 ` [PATCH v5 10/19] xen: arm: implement XEN_DOMCTL_set_address_size Ian Campbell
2013-11-13 18:11 ` [PATCH v5 11/19] xen: arm: implement arch_set_info_guest for 64-bit vcpus Ian Campbell
2013-11-13 18:11 ` [PATCH v5 12/19] tools: check for libfdt when building for ARM Ian Campbell
2013-11-13 18:11 ` [PATCH v5 13/19] xen: arm: define guest virtual platform in API headers Ian Campbell
2013-11-13 18:11 ` [PATCH v5 14/19] libxc: arm: rename various bits of zimage load with 32 suffix Ian Campbell
2013-11-13 18:11 ` [PATCH v5 15/19] libxc: allow caller to specify guest rambase rather than hardcoding Ian Campbell
2013-11-13 18:11 ` [PATCH v5 16/19] libxc: arm: allow passing a device tree blob to the guest Ian Campbell
2013-11-14  0:47   ` Julien Grall
2013-11-19 12:36     ` Ian Campbell
2013-11-13 18:11 ` [PATCH v5 17/19] libxc: support for arm64 Image format Ian Campbell
2013-11-14  1:17   ` Julien Grall
2013-11-19 12:39     ` Ian Campbell
2013-11-13 18:11 ` [PATCH v5 18/19] libxc: arm64 vcpu initialisation Ian Campbell
2013-11-13 18:11 ` [PATCH v5 19/19] libxl: build a device tree for ARM guests Ian Campbell
2013-11-13 18:19   ` Stefano Stabellini
2013-11-14  1:04   ` Julien Grall [this message]
2013-11-14  8:28     ` Ian Campbell
2013-11-14 12:17       ` Julien Grall
2013-11-14 11:50   ` Ian Jackson
2013-11-14 12:17     ` Stefano Stabellini
2013-11-14 12:24       ` Julien Grall
2013-11-14 12:45       ` Ian Campbell
2013-11-14 14:01         ` Stefano Stabellini
2013-11-19 10:30           ` 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=5284219D.3060503@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.