From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] arm:extend the reserved mrmory for initrd to be page aligned
Date: Mon, 15 Sep 2014 11:16:32 +0100 [thread overview]
Message-ID: <20140915101632.GA12361@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <35FD53F367049845BC99AC72306C23D103D6DB491605@CNBJMBX05.corpusers.net>
On Mon, Sep 15, 2014 at 05:59:27PM +0800, Wang, Yalin wrote:
> Hi
>
> Add more log:
> <4>[ 0.000000] INITRD unalign phys address:0x02000000+0x0022fb0e
> <4>[ 0.000000] INITRD aligned phys address:0x02000000+0x00230000
> <4>[ 0.574868] free_initrd: free initrd 0xc2000000+0xc222fb0e
> <4>[ 0.579398] free_initrd_mem: free pfn:8192---8752
>
> The inird used memory is still the same as the one passed by bootloads,
> I don't change it. It should be safe.
This tells me nothing about whether the initrd is actually /used/. What
it tells me is that it's being freed. The function of an initrd is not
to be a chunk of memory which gets freed later on in the boot process.
It is there to provide an "initial ramdisk" (whether it be a filesystem
image, or a CPIO compressed archive) for userspace to run.
So, have you checked that initrd is still functional after this patch?
--
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2014-09-15 10:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 5:11 [RFC] arm:extend the reserved mrmory for initrd to be page aligned Wang, Yalin
2014-09-15 8:46 ` Russell King - ARM Linux
2014-09-15 9:07 ` Wang, Yalin
2014-09-15 9:30 ` Russell King - ARM Linux
2014-09-15 9:59 ` Wang, Yalin
2014-09-15 10:16 ` Russell King - ARM Linux [this message]
2014-09-15 10:22 ` Wang, Yalin
2014-09-15 10:30 ` Russell King - ARM Linux
2014-09-15 10:58 ` Wang, Yalin
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=20140915101632.GA12361@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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