From: tj@kernel.org (Tejun Heo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] WIP: HACK: LPAE, BOOTMEM and NO_BOOTMEM
Date: Mon, 5 Aug 2013 11:01:27 -0400 [thread overview]
Message-ID: <20130805150127.GC19631@mtj.dyndns.org> (raw)
In-Reply-To: <51FC1F3A.8090201@ti.com>
Hello,
On Fri, Aug 02, 2013 at 05:06:02PM -0400, Santosh Shilimkar wrote:
> Looking at the situation, how about proceeding with patch updating
> the bootmem API signatures to use phys_addr_t which can unblock me
> to get my machine working.
I'm not sure about that. No matter how you play it, it'll end up
duplicating memblock interface.
> Introduction of new API, conversions of core kernel code and then
What new API are we talking about? Wasn't the plan to convert core
kernel code to use memblock and let bootmem emulate bootmem API?
There's no new API.
> arches moving away from bootmem is going to take significant time
And arches moving away from bootmem doesn't have to happen now.
> anyways. I will continue my effort to get ARM port moved to no-bootmem
> and get that merged.
Thanks.
--
tejun
next prev parent reply other threads:[~2013-08-05 15:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 1:01 [PATCH] WIP: HACK: LPAE, BOOTMEM and NO_BOOTMEM Santosh Shilimkar
2013-06-29 15:29 ` Tejun Heo
2013-06-29 17:21 ` Russell King - ARM Linux
2013-06-29 17:57 ` Tejun Heo
2013-06-29 18:23 ` H. Peter Anvin
2013-06-29 19:29 ` Yinghai Lu
2013-06-29 19:55 ` Russell King - ARM Linux
2013-06-29 20:08 ` Yinghai Lu
2013-07-01 14:10 ` Santosh Shilimkar
2013-07-25 22:33 ` Santosh Shilimkar
2013-07-25 22:36 ` Tejun Heo
2013-07-25 23:15 ` Santosh Shilimkar
2013-07-26 3:08 ` Tejun Heo
2013-08-02 21:06 ` Santosh Shilimkar
2013-08-05 15:01 ` Tejun Heo [this message]
2013-08-05 15:29 ` Santosh Shilimkar
2013-08-05 15:38 ` Tejun Heo
2013-08-05 15:47 ` Santosh Shilimkar
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=20130805150127.GC19631@mtj.dyndns.org \
--to=tj@kernel.org \
--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).