From: orca.chen@gmail.com (Min-Hua Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 0/2] creating non-section aligned lowmem mappings
Date: Thu, 11 Jun 2015 02:59:31 +0800 [thread overview]
Message-ID: <1433962773-8402-1-git-send-email-orca.chen@gmail.com> (raw)
Hi,
I found problems when I reserved non-section aligned memory blocks
by the device tree. The problem is that the memblock_set_current_limit()
point to the first section aligned memblock in the
first place (sanity_check_meminfo), but the memblock may be split
into non-section aligned memblocks because the memblock_reserve() calls
in arm_memblock_init().
*** BLURB HERE ***
Min-Hua Chen (2):
arm: fix non-section-aligned low memory mapping
arm: use max_lowmem_limit in find_limit()
arch/arm/mm/init.c | 2 +-
arch/arm/mm/mmu.c | 48 ++++++++++++++----------------------------------
2 files changed, 15 insertions(+), 35 deletions(-)
--
1.7.10.4
next reply other threads:[~2015-06-10 18:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 18:59 Min-Hua Chen [this message]
2015-06-10 18:59 ` [PATCHv3 1/2] arm: fix non-section-aligned low memory mapping Min-Hua Chen
2015-06-10 22:40 ` Russell King - ARM Linux
2015-06-11 0:02 ` Min-Hua Chen
2015-06-10 18:59 ` [PATCHv3 2/2] arm: use max_lowmem_limit in find_limit() Min-Hua Chen
2015-06-10 22:41 ` 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=1433962773-8402-1-git-send-email-orca.chen@gmail.com \
--to=orca.chen@gmail.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).