linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM initrd updates
Date: Wed, 8 Feb 2017 11:10:24 +0000	[thread overview]
Message-ID: <20170208111024.GV27312@n2100.armlinux.org.uk> (raw)

Three patches to cleanup and update the ARM initrd handling, after problems
identified by William Helsby.

The first patch merely moves the early initrd code into a separate
function, rather than being bundled up inside arm_memblock_init().

The second patch restructures the initrd code to be cleaner, but with
no functional changes.  We get rid of the repetitive phys_initrd_size
checks, as we can now just "return" from the function.

The third patch changes how we check for overlaps and the region that
we reserve.  Since the kernel deals with pages and not bytes for
allocation, the minimum granule for marking addresses reserved and
later freeing them is one page.  We already adjust the initrd addresses
in free_initrd_mem(), but we fail to mark the partially used pages
entirely reserved.  Add this.

 arch/arm/mm/init.c | 57 +++++++++++++++++++++++++++++++++++++-----------------
 1 file changed, 39 insertions(+), 18 deletions(-)

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

             reply	other threads:[~2017-02-08 11:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08 11:10 Russell King - ARM Linux [this message]
2017-02-08 11:10 ` [PATCH 1/3] ARM: mm: move initrd init code out of arm_memblock_init() Russell King
2017-02-08 11:11 ` [PATCH 2/3] ARM: mm: clean up initrd initialisation Russell King
2017-02-08 11:11 ` [PATCH 3/3] ARM: mm: round the initrd reservation to page boundaries Russell King

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=20170208111024.GV27312@n2100.armlinux.org.uk \
    --to=linux@armlinux.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;
as well as URLs for NNTP newsgroup(s).