From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <ian.campbell@citrix.com>, xen-devel@lists.xen.org
Cc: tim@xen.org, stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH v5 16/19] libxc: arm: allow passing a device tree blob to the guest
Date: Thu, 14 Nov 2013 00:47:27 +0000 [thread overview]
Message-ID: <52841D9F.10007@linaro.org> (raw)
In-Reply-To: <1384366285-29277-16-git-send-email-ian.campbell@citrix.com>
On 11/13/2013 06:11 PM, Ian Campbell wrote:
> Placement of the blob in guest RAM is simplistic but will do for now.
>
> This operation is only supported on ARM.
>
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
> ---
> v4: Return EINVAL on non-ARM platforms (which do not support device-tree)
> Slightly less rubbish DTB placement which isn't perfect but at least now
> doesn't fail with <128MB of RAM.
> ---
> tools/libxc/xc_dom.h | 8 +++++++
> tools/libxc/xc_dom_arm.c | 22 ++++++++++++++++++-
> tools/libxc/xc_dom_core.c | 53 +++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 82 insertions(+), 1 deletion(-)
>
[..]
> diff --git a/tools/libxc/xc_dom_arm.c b/tools/libxc/xc_dom_arm.c
> index 9f3fdd3..4c59177 100644
> --- a/tools/libxc/xc_dom_arm.c
> +++ b/tools/libxc/xc_dom_arm.c
> @@ -124,7 +124,8 @@ static int vcpu_arm(struct xc_dom_image *dom, void *ptr)
> * using CONFIG_ARM_APPENDED_DTB. Ensure that r2 does not look
> * like a valid pointer to a set of ATAGS or a DTB.
> */
> - ctxt->user_regs.r2_usr = 0xffffffff;
> + ctxt->user_regs.r2_usr = dom->devicetree_blob ?
> + dom->devicetree_seg.vstart : 0xffffffff;
>
> ctxt->sctlr = SCTLR_GUEST_INIT;
>
> @@ -191,6 +192,25 @@ int arch_setup_meminit(struct xc_dom_image *dom)
> 0, 0, &dom->p2m_host[i]);
> }
>
> + if ( dom->devicetree_blob )
> + {
> + const uint64_t rambase = dom->rambase_pfn << XC_PAGE_SHIFT;
> + const uint64_t ramend = rambase + ( dom->total_pages << XC_PAGE_SHIFT );
> + const uint64_t dtbsize = ( dom->devicetree_size + 3 ) & ~0x3;
> +
> + /* Place at 128MB if there is sufficient RAM */
> + if (ramend >= rambase + 128*1024*1024 + dtbsize )
Minor coding style error : if ( ... )
Also, I'm wondering if (128 << 20) will be more clear?
[..]
--
Julien Grall
next prev parent reply other threads:[~2013-11-14 0:47 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 [this message]
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
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=52841D9F.10007@linaro.org \
--to=julien.grall@linaro.org \
--cc=ian.campbell@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).