From: Michael Ellerman <mpe@ellerman.id.au>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: Gavin Shan <gwshan@linux.vnet.ibm.com>, zhlcindy@linux.vnet.ibm.com
Subject: Re: [RFC] powerpc/mm: Support bootmem for PPC64 again
Date: Sat, 26 Mar 2016 20:23:54 +1100 (AEDT) [thread overview]
Message-ID: <3qXF961KWTz9s4x@ozlabs.org> (raw)
In-Reply-To: <1458921821-14960-1-git-send-email-gwshan@linux.vnet.ibm.com>
On Fri, 2016-25-03 at 16:03:41 UTC, Gavin Shan wrote:
> CONFIG_NO_BOOTMEM is enabled on PPC platforms by default. However,
> user might disable that to have bootmem for other purpose. So it's
> resonable to support it.
Hi Gavin,
Sorry but I don't understand. We deliberately removed bootmem support, and don't
want it back, it doesn't add anything other than complexity. See 10239733ee86
("powerpc: Remove bootmem allocator").
I wasn't aware there was any way to enable it? If there is we should fix that.
cheers
next prev parent reply other threads:[~2016-03-26 9:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 16:03 [PATCH RFC] powerpc/mm: Support bootmem for PPC64 again Gavin Shan
2016-03-26 7:15 ` Balbir Singh
2016-03-26 9:23 ` Michael Ellerman [this message]
2016-03-26 12:50 ` [RFC] " Gavin Shan
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=3qXF961KWTz9s4x@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=gwshan@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=zhlcindy@linux.vnet.ibm.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).