From: Tejun Heo <tj@kernel.org>
To: Cyril Chemparathy <cyril@ti.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, davem@davemloft.net,
eric.dumazet@gmail.com, hannes@cmpxchg.org,
shangw@linux.vnet.ibm.com, vitalya@ti.com
Subject: Re: [PATCH] mm: bootmem: use phys_addr_t for physical addresses
Date: Thu, 13 Sep 2012 12:32:09 -0700 [thread overview]
Message-ID: <20120913193209.GL7677@google.com> (raw)
In-Reply-To: <50512B9A.9060905@ti.com>
Hello, Cyril.
On Wed, Sep 12, 2012 at 08:40:58PM -0400, Cyril Chemparathy wrote:
> You probably missed the lowmem bit from my response?
>
> This system has all of its memory outside the 4GB physical address
> space. This includes lowmem, which is permanently mapped into the
> kernel virtual address space as usual.
Yeah, I understand that and as a short-term solution we maybe can add
a check to verify that the goal and limits are under lowmem and fail
with NULL if not, but it still is a broken interface and I'd rather
not mess with it when memblock is already there. Converting to
memblock usually isn't too much work although it expectedly involves
some subtleties and fallouts for a while.
Do you recall what the problem was with sparsemem and memblock? I
don't think I'll directly work on arm but I'll be happy to help on
memblock issues.
Thanks.
--
tejun
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2012-09-13 19:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 16:06 [PATCH] mm: bootmem: use phys_addr_t for physical addresses Cyril Chemparathy
2012-09-12 20:39 ` Tejun Heo
2012-09-13 0:08 ` Cyril Chemparathy
2012-09-13 0:34 ` Tejun Heo
2012-09-13 0:40 ` Cyril Chemparathy
2012-09-13 19:32 ` Tejun Heo [this message]
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=20120913193209.GL7677@google.com \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cyril@ti.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shangw@linux.vnet.ibm.com \
--cc=vitalya@ti.com \
/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).