From: cov@codeaurora.org (Christopher Covington)
To: linux-arm-kernel@lists.infradead.org
Subject: [Qemu-devel] [PATCH] QEMU: ARM: boot: Load kernel at an Image friendly address
Date: Tue, 25 Mar 2014 08:29:37 -0400 [thread overview]
Message-ID: <533176B1.9060103@codeaurora.org> (raw)
In-Reply-To: <1395718484-20424-1-git-send-email-joelf@ti.com>
Hi Joel,
On 03/24/2014 11:34 PM, Joel Fernandes wrote:
> Loading kernel at offset 0x10000 works only for zImage, but not for Image,
> because the kernel expect the start of decompressed kernel (.head.text) to be
Nit: expects
> at an address that's a distance that's 16MB aligned from PAGE_OFFSET +
> TEXT_OFFSET (see vmlinux.lds.S). This check is enfornced in __fixup_pv_table in
Nit: enforced
> arch/arm/kernel/head.S TEXT_OFFSET is 0x00008000, so a 16MB alignment needs to
> have a "0x8000" in the lower 16 bits so that they cancel out. Currently the
> offset Qemu loads it at is 0x10000.
>
> With zImage, this need is met because zImage loads the uncompressed Image
> correctly, however when loading an Image and executing directly Qemu is
> required it to load it at the correct location. Doing so, doesn't break Qemu's
> zImage loading. With this patch, both zImage and Image work correctly.
I had just been playing with my own version of this change. Glad to see it
going upstream.
Tested-by: Christopher Covington <cov@codeaurora.org>
Thanks,
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
WARNING: multiple messages have this Message-ID (diff)
From: Christopher Covington <cov@codeaurora.org>
To: Joel Fernandes <joelf@ti.com>
Cc: qemu-devel@nongnu.org,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [Qemu-devel] [PATCH] QEMU: ARM: boot: Load kernel at an Image friendly address
Date: Tue, 25 Mar 2014 08:29:37 -0400 [thread overview]
Message-ID: <533176B1.9060103@codeaurora.org> (raw)
In-Reply-To: <1395718484-20424-1-git-send-email-joelf@ti.com>
Hi Joel,
On 03/24/2014 11:34 PM, Joel Fernandes wrote:
> Loading kernel at offset 0x10000 works only for zImage, but not for Image,
> because the kernel expect the start of decompressed kernel (.head.text) to be
Nit: expects
> at an address that's a distance that's 16MB aligned from PAGE_OFFSET +
> TEXT_OFFSET (see vmlinux.lds.S). This check is enfornced in __fixup_pv_table in
Nit: enforced
> arch/arm/kernel/head.S TEXT_OFFSET is 0x00008000, so a 16MB alignment needs to
> have a "0x8000" in the lower 16 bits so that they cancel out. Currently the
> offset Qemu loads it at is 0x10000.
>
> With zImage, this need is met because zImage loads the uncompressed Image
> correctly, however when loading an Image and executing directly Qemu is
> required it to load it at the correct location. Doing so, doesn't break Qemu's
> zImage loading. With this patch, both zImage and Image work correctly.
I had just been playing with my own version of this change. Glad to see it
going upstream.
Tested-by: Christopher Covington <cov@codeaurora.org>
Thanks,
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
next prev parent reply other threads:[~2014-03-25 12:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 3:34 [PATCH] QEMU: ARM: boot: Load kernel at an Image friendly address Joel Fernandes
2014-03-25 3:34 ` [Qemu-devel] " Joel Fernandes
2014-03-25 12:29 ` Christopher Covington [this message]
2014-03-25 12:29 ` Christopher Covington
2014-03-25 13:43 ` Joel Fernandes
2014-03-25 13:43 ` Joel Fernandes
2014-03-25 13:13 ` Peter Maydell
2014-03-25 13:13 ` [Qemu-devel] " Peter Maydell
2014-03-25 13:46 ` Joel Fernandes
2014-03-25 13:46 ` [Qemu-devel] " Joel Fernandes
2014-04-01 17:10 ` Peter Maydell
2014-04-01 17:10 ` [Qemu-devel] " Peter Maydell
2014-04-02 12:11 ` Peter Crosthwaite
2014-04-02 12:11 ` Peter Crosthwaite
2014-04-02 12:47 ` Peter Maydell
2014-04-02 12:47 ` Peter Maydell
2014-04-02 12:58 ` Peter Crosthwaite
2014-04-02 12:58 ` Peter Crosthwaite
2014-04-02 15:04 ` Christopher Covington
2014-04-02 15:04 ` Christopher Covington
2014-04-02 16:06 ` Joel Fernandes
2014-04-02 16:06 ` Joel Fernandes
2014-04-17 10:02 ` Peter Maydell
2014-04-17 13:34 ` Christopher Covington
2014-04-17 16:53 ` Joel Fernandes
2014-04-23 2:20 ` Peter Crosthwaite
2014-04-23 2:47 ` 答复: " lig.fnst at cn.fujitsu.com
2014-04-17 16:58 ` Rob Herring
2014-04-17 19:26 ` Peter Maydell
2014-04-23 2:07 ` Peter Crosthwaite
2014-04-28 16:19 ` Uwe Kleine-König
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=533176B1.9060103@codeaurora.org \
--to=cov@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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.