From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: ian.jackson@eu.citrix.com, stefano.stabellini@eu.citrix.com,
tim@xen.org, xen-devel@lists.xen.org
Subject: Re: [PATCH v3 12/14] libxc: support for arm64 Image format
Date: Mon, 11 Nov 2013 14:28:57 +0000 [thread overview]
Message-ID: <5280E9A9.6070605@linaro.org> (raw)
In-Reply-To: <1383842696-8598-12-git-send-email-ian.campbell@citrix.com>
On 11/07/2013 04:44 PM, Ian Campbell wrote:
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> ---
> tools/libxc/xc_dom_armzimageloader.c | 88 ++++++++++++++++++++++++++++++++++
> 1 file changed, 88 insertions(+)
>
> diff --git a/tools/libxc/xc_dom_armzimageloader.c b/tools/libxc/xc_dom_armzimageloader.c
> index 4e3f7ae..609d3a0 100644
> --- a/tools/libxc/xc_dom_armzimageloader.c
> +++ b/tools/libxc/xc_dom_armzimageloader.c
> @@ -129,6 +129,86 @@ static int xc_dom_parse_zimage32_kernel(struct xc_dom_image *dom)
> }
>
> /* ------------------------------------------------------------ */
> +/* 64-bit zImage Support */
> +/* ------------------------------------------------------------ */
> +
> +#define ZIMAGE64_MAGIC_V0 0x14000008
> +#define ZIMAGE64_MAGIC_V1 0x644d5241 /* "ARM\x64" */
> +
> +/* linux/Documentation/arm64/booting.txt */
> +struct zimage64_hdr {
> + uint32_t magic0;
> + uint32_t res0;
> + uint64_t text_offset; /* Image load offset */
> + uint64_t res1;
> + uint64_t res2;
> + /* zImage V1 only from here */
> + uint64_t res3;
> + uint64_t res4;
> + uint64_t res5;
> + uint32_t magic1;
> + uint32_t res6;
> +};
> +static int xc_dom_probe_zimage64_kernel(struct xc_dom_image *dom)
> +{
> + struct zimage64_hdr *zimage;
> +
> + if ( dom->kernel_blob == NULL )
> + {
> + xc_dom_panic(dom->xch, XC_INTERNAL_ERROR,
> + "%s: no kernel image loaded", __FUNCTION__);
> + return -EINVAL;
> + }
> +
> + if ( dom->kernel_size < sizeof(*zimage) )
> + {
> + xc_dom_printf(dom->xch, "%s: kernel image too small", __FUNCTION__);
> + return -EINVAL;
> + }
> +
> + zimage = dom->kernel_blob;
> + if ( zimage->magic0 != ZIMAGE64_MAGIC_V0 &&
> + zimage->magic1 != ZIMAGE64_MAGIC_V1 )
> + {
> + xc_dom_printf(dom->xch, "%s: kernel is not an arm64 Image", __FUNCTION__);
> + return -EINVAL;
> + }
> +
> + return 0;
> +}
> +
> +static int xc_dom_parse_zimage64_kernel(struct xc_dom_image *dom)
> +{
> + struct zimage64_hdr *zimage;
> + uint32_t entry_addr;
> + uint64_t v_start, v_end;
> + uint64_t rambase = dom->rambase_pfn << XC_PAGE_SHIFT;
> +
> + DOMPRINTF_CALLED(dom->xch);
> +
> + zimage = dom->kernel_blob;
> +
> + v_start = rambase + zimage->text_offset;
> + v_end = v_start + dom->kernel_size;
You define v_end which is not use in the function.
--
Julien Grall
next prev parent reply other threads:[~2013-11-11 14:28 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 16:44 [PATCH v3 00/14] xen: arm: 64-bit guest support and domU FDT autogeneration Ian Campbell
2013-11-07 16:44 ` [PATCH v3 01/14] xen: arm: Report aarch64 capability Ian Campbell
2013-11-07 16:44 ` [PATCH v3 02/14] xen: arm: Add comment regard arm64 zImage v0 vs v1 Ian Campbell
2013-11-07 16:44 ` [PATCH v3 03/14] xen: arm: allocate dom0 memory separately from preparing the dtb Ian Campbell
2013-11-08 7:18 ` Julien Grall
2013-11-08 9:36 ` Ian Campbell
2013-11-11 12:08 ` Julien Grall
2013-11-11 12:12 ` Ian Campbell
2013-11-11 12:25 ` Julien Grall
2013-11-11 13:17 ` Stefano Stabellini
2013-11-07 16:44 ` [PATCH v3 04/14] xen: arm: add enable-method to cpu nodes for arm64 guests Ian Campbell
2013-11-07 16:44 ` [PATCH v3 05/14] xen: arm: implement XEN_DOMCTL_set_address_size Ian Campbell
2013-11-11 12:13 ` Julien Grall
2013-11-07 16:44 ` [PATCH v3 06/14] xen: arm: implement arch_set_info_guest for 64-bit vcpus Ian Campbell
2013-11-08 7:20 ` Julien Grall
2013-11-07 16:44 ` [PATCH v3 07/14] tools: check for libfdt when building for ARM Ian Campbell
2013-11-07 17:04 ` Ian Jackson
2013-11-07 16:44 ` [PATCH v3 08/14] xen: arm: define guest virtual platform in API headers Ian Campbell
2013-11-08 7:29 ` Julien Grall
2013-11-08 9:48 ` Ian Campbell
2013-11-11 14:25 ` Julien Grall
2013-11-11 15:12 ` Ian Campbell
2013-11-07 16:44 ` [PATCH v3 09/14] libxc: arm: rename various bits of zimage load with 32 suffix Ian Campbell
2013-11-07 16:44 ` [PATCH v3 10/14] libxc: allow caller to specify guest rambase rather than hardcoding Ian Campbell
2013-11-07 17:06 ` Ian Jackson
2013-11-07 17:09 ` Ian Campbell
2013-11-07 17:30 ` Ian Jackson
2013-11-07 16:44 ` [PATCH v3 11/14] libxc: allow passing a device tree blob to the guest Ian Campbell
2013-11-07 17:09 ` Ian Jackson
2013-11-07 17:10 ` Ian Campbell
2013-11-07 17:31 ` Ian Jackson
2013-11-07 17:42 ` Ian Campbell
2013-11-12 10:46 ` Ian Campbell
2013-11-07 16:44 ` [PATCH v3 12/14] libxc: support for arm64 Image format Ian Campbell
2013-11-11 14:28 ` Julien Grall [this message]
2013-11-07 16:44 ` [PATCH v3 13/14] libxc: arm64 vcpu initialisation Ian Campbell
2013-11-07 17:09 ` Ian Jackson
2013-11-11 15:03 ` Julien Grall
2013-11-07 16:44 ` [PATCH v3 14/14] libxl: build a device tree for ARM guests Ian Campbell
2013-11-07 17:30 ` Ian Jackson
2013-11-07 17:41 ` Ian Campbell
2013-11-07 17:47 ` Ian Jackson
2013-11-08 9:30 ` Ian Campbell
2013-11-08 15:14 ` Ian Jackson
2013-11-11 12:14 ` Ian Campbell
2013-11-12 10:51 ` 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=5280E9A9.6070605@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 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).