From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] ARM: xip: Use correct symbol for end of ROM marker
Date: Fri, 13 Nov 2015 07:46:24 +0000 [thread overview]
Message-ID: <CAMuHMdXsw8BBCY5-fxWLvF1vxh83DhhKGD113LTBu-8ZFV68gw@mail.gmail.com> (raw)
In-Reply-To: <1447362108-4333-1-git-send-email-chris.brandt@renesas.com>
Hi Chris,
On Thu, Nov 12, 2015 at 10:01 PM, Chris Brandt <chris.brandt@renesas.com> wrote:
> For an XIP build, _edata_loc, not _etext, represents the end of the
> binary image that will be programmed into ROM and mapped into the
> MODULES_VADDR area.
> With an XIP kernel, nothing is loaded into RAM before boot, meaning
> you have to take into account the size of the entire binary image
> that was programmed, including the init data values that will be copied
> to RAM during kernel boot.
>
> This fixes the bug where you might lose the end of your kernel area
> after page table setup is complete.
Thanks for your patch!
> Signed-off-by: Chris Brandt <chris.brandt@renesas.com>
> ---
> v2
> * Added change for MODULES_VADDR
> * Moved extern to new file asm/sections.h
> ---
> arch/arm/include/asm/sections.h | 8 ++++++++
> arch/arm/kernel/module.c | 2 +-
> arch/arm/mm/mmu.c | 4 ++--
> 3 files changed, 11 insertions(+), 3 deletions(-)
> create mode 100644 arch/arm/include/asm/sections.h
If you create an arm-specific <asm/sections.h>, you also have to remove the
line
generic-y += sections.h
from arch/arm/include/asm/Kbuild.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2015-11-13 7:46 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 14:17 [PATCH] ARM: xip: Use correct symbol for end of ROM marker Chris Brandt
2015-11-12 12:17 ` Peter Hurley
2015-11-12 13:15 ` Chris Brandt
2015-11-12 16:32 ` Russell King - ARM Linux
2015-11-12 21:01 ` [PATCH v2] " Chris Brandt
2015-11-13 7:46 ` Geert Uytterhoeven [this message]
2015-11-13 20:03 ` Chris Brandt
2015-11-16 18:05 ` [PATCH v3] " Chris Brandt
2015-11-16 18:17 ` Russell King - ARM Linux
2015-11-16 19:46 ` Chris Brandt
2015-11-16 19:53 ` Russell King - ARM Linux
2015-11-16 20:18 ` Chris Brandt
2015-11-16 20:30 ` Russell King - ARM Linux
2015-11-16 20:57 ` Nicolas Pitre
2015-11-16 21:09 ` Chris Brandt
2015-11-16 20:27 ` Nicolas Pitre
2015-11-16 21:02 ` Chris Brandt
2015-11-16 21:47 ` Nicolas Pitre
2015-11-16 22:19 ` Chris Brandt
2015-11-17 0:48 ` Nicolas Pitre
2015-11-17 2:11 ` Chris Brandt
2015-11-17 2:37 ` Nicolas Pitre
2015-11-17 16:56 ` Chris Brandt
2015-11-17 17:24 ` Nicolas Pitre
2015-11-18 3:58 ` Nicolas Pitre
2015-11-18 5:12 ` Magnus Damm
2015-11-18 13:45 ` Nicolas Pitre
2015-11-18 17:01 ` Nicolas Pitre
2015-11-18 19:12 ` Chris Brandt
2015-11-18 20:23 ` Nicolas Pitre
2015-11-18 20:51 ` Chris Brandt
2015-11-18 21:36 ` Nicolas Pitre
2016-01-29 21:12 ` Chris Brandt
2016-01-29 21:17 ` Nicolas Pitre
2015-11-17 16:45 ` Chris Brandt
2015-11-17 16:57 ` Nicolas Pitre
2015-11-18 2:09 ` Chris Brandt
2015-11-18 3:17 ` Nicolas Pitre
2015-11-18 8:30 ` Arnd Bergmann
2015-11-18 15:28 ` Chris Brandt
2015-11-18 15:16 ` Chris Brandt
2015-11-18 17:07 ` Nicolas Pitre
2015-11-18 19:36 ` Chris Brandt
2015-11-18 19:44 ` Nicolas Pitre
2015-11-18 20:00 ` Chris Brandt
2015-11-17 17:33 ` Russell King - ARM Linux
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=CAMuHMdXsw8BBCY5-fxWLvF1vxh83DhhKGD113LTBu-8ZFV68gw@mail.gmail.com \
--to=geert@linux-m68k.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 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).