All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Oleksandr Dmytryshyn <oleksandr.dmytryshyn@globallogic.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@citrix.com>,
	Tim Deegan <tim@xen.org>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH] xen: arm: introduce uImage probe function for Dom0
Date: Tue, 19 Aug 2014 12:06:31 -0500	[thread overview]
Message-ID: <53F38417.6080400@linaro.org> (raw)
In-Reply-To: <1408444630-16995-1-git-send-email-oleksandr.dmytryshyn@globallogic.com>

Hi Oleksandr,

Thanks you for your patch,

On 19/08/14 05:37, Oleksandr Dmytryshyn wrote:
> Patch adds a possibility to boot dom0 kernel from uImage.
> This is needed to improve bootime. Comparing to zImage,

boot-time

> uImage is not packed, therefore we can save time needed
> to unpack.
>
> Change-Id: If92bc895721f0b2fa0a844bb92eddc8f1fdc5498
> Signed-off-by: Oleksandr Dmytryshyn <oleksandr.dmytryshyn@globallogic.com>
> ---
>   xen/arch/arm/kernel.c | 67 +++++++++++++++++++++++++++++++++++++++++++++++++++
>   1 file changed, 67 insertions(+)
>
> diff --git a/xen/arch/arm/kernel.c b/xen/arch/arm/kernel.c
> index d635a7e..45d92c9 100644
> --- a/xen/arch/arm/kernel.c
> +++ b/xen/arch/arm/kernel.c
> @@ -16,6 +16,12 @@
>
>   #include "kernel.h"
>
> +#define UIMAGE32_MAGIC_OFFSET 0x8
> +#define UIMAGE32_START_OFFSET 0x4
> +#define UIMAGE32_END_OFFSET   0x3

Can you define a structure as it's done for zImage64. It's easier to 
understand. Also, do you have any link to the uImage protocol?

A quick search doesn't allow me to find anything that match your format 
here.

[..]

> +    /*
> +     * Check for an appended DTB.
> +     */
> +    if ( addr + len + sizeof(dtb_hdr) <= size )
> +    {
> +        copy_from_paddr(&dtb_hdr, addr + len, sizeof(dtb_hdr));
> +
> +        if ( be32_to_cpu(dtb_hdr.magic) == DTB_MAGIC )
> +            len += be32_to_cpu(dtb_hdr.total_size);
> +
> +            if ( len - start > addr + size )
> +                return -EINVAL;
> +    }

This is a legacy on zImage, I don't really want to see it on 
implementation of a new format. Xen is creating the device tree for 
DOM0, the developer should not append a device tree.

-- 
Julien Grall

  reply	other threads:[~2014-08-19 17:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19 10:37 [PATCH] xen: arm: introduce uImage probe function for Dom0 Oleksandr Dmytryshyn
2014-08-19 17:06 ` Julien Grall [this message]
2014-08-20  5:17   ` Andrii Tseglytskyi
2014-08-20 15:24     ` Julien Grall
2014-08-20 10:01   ` Oleksandr Dmytryshyn

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=53F38417.6080400@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=ian.campbell@citrix.com \
    --cc=oleksandr.dmytryshyn@globallogic.com \
    --cc=stefano.stabellini@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.