From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm: fix kernel image size
Date: Tue, 21 Jun 2016 00:43:21 -0700 [thread overview]
Message-ID: <20160621074319.GH22406@atomide.com> (raw)
In-Reply-To: <E1bDzh4-0006a4-7p@e0050434b2927.dyn.armlinux.org.uk>
Hi,
* Russell King <rmk@armlinux.org.uk> [160617 12:52]:
> If we want to assume that the compressed image will expand by a maximum
> of 4x, we actually need to reserve 5x the space, since we need to keep
> a copy of the compessed image around while decompressing.
Looks like 5x is not enough with omap2plus_defconfig at least..
This one needs to be set to 6x for that. Maybe we should just make
it go all the way to 11 :)
Otherwise we get this without initrd:
kernel: 0xb6c2d008 kernel_size: 0x3a4418
MEMORY RANGES
0000000080000000-00000000bfdfffff (0)
kexec_load: entry = 0x80008000 flags = 0x280000
nr_segments = 2
segment[0].buf = 0xb6c2d008
segment[0].bufsz = 0x3a4418
segment[0].mem = 0x80008000
segment[0].memsz = 0x3a5000
segment[1].buf = 0xadf80
segment[1].bufsz = 0xe000
segment[1].mem = 0x8123f000
segment[1].memsz = 0xe000
[ 32.886077] kexec_core: Starting new kernel
[ 32.890502] Disabling non-boot CPUs ...
[ 32.926696] CPU1: shutdown
[ 32.991882] Bye!
Warning: Neither atags nor dtb found
And we get this with initrd:
kernel: 0xb6bf4008 kernel_size: 0x3a4418
MEMORY RANGES
0000000080000000-00000000fedfffff (0)
kexec_load: entry = 0x80008000 flags = 0x280000
nr_segments = 3
segment[0].buf = 0xb6bf4008
segment[0].bufsz = 0x3a4418
segment[0].mem = 0x80008000
segment[0].memsz = 0x3a5000
segment[1].buf = 0xb6686008
segment[1].bufsz = 0x56dba2
segment[1].mem = 0x8123e000
segment[1].memsz = 0x56e000
segment[2].buf = 0xadf80
segment[2].bufsz = 0xd080
segment[2].mem = 0x817ac000
segment[2].memsz = 0xe000
...
INITRD: 0x8123e000+0x0056dba2 overlaps in-use memory region - disabling initrd
Regards,
Tony
next prev parent reply other threads:[~2016-06-21 7:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 19:44 [PATCH 0/2] Simple fix to the ARM kexec tools implementation Russell King - ARM Linux
2016-06-17 19:44 ` [PATCH 1/2] arm: take account of TEXT_OFFSET for subsequent images Russell King
2016-06-17 19:44 ` [PATCH 2/2] arm: fix kernel image size Russell King
2016-06-21 7:43 ` Tony Lindgren [this message]
2016-06-21 9:47 ` Russell King - ARM Linux
2016-06-21 10:38 ` Tony Lindgren
2016-06-21 10:57 ` Tony Lindgren
2016-06-21 15:44 ` Russell King - ARM Linux
2016-06-21 16:55 ` Tony Lindgren
2016-06-21 21:51 ` Russell King - ARM Linux
2016-06-22 7:36 ` Tony Lindgren
2016-06-22 8:29 ` Russell King - ARM Linux
2016-06-22 8:51 ` Tony Lindgren
2016-06-21 11:02 ` Mason
2016-06-21 6:11 ` [PATCH 0/2] Simple fix to the ARM kexec tools implementation Pratyush Anand
2016-06-21 8:20 ` Russell King - ARM Linux
2016-06-23 0:41 ` Simon Horman
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=20160621074319.GH22406@atomide.com \
--to=tony@atomide.com \
--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).