From: Emil Medve <Emilian.Medve@Freescale•com>
To: Aneesh Kumar K.V <aneesh.kumar@linux•vnet.ibm.com>,
<benh@kernel•crashing.org>, <linuxppc-dev@lists•ozlabs.org>
Subject: Re: [PATCH 2/2 v2] powerpc: Enable NO_BOOTMEM
Date: Wed, 7 May 2014 13:37:50 -0500 [thread overview]
Message-ID: <536A7D7E.8070509@Freescale.com> (raw)
In-Reply-To: <87lhueumdp.fsf@linux.vnet.ibm.com>
Hello Aneesh,
On 05/07/2014 01:35 AM, Aneesh Kumar K.V wrote:
> Emil Medve <Emilian.Medve@Freescale•com> writes:
>
>> Currently bootmem is just a wrapper around memblock. This gets rid of
>> the wrapper code just as other ARHC(es) did: x86, arm, etc.
>>
>> For now only cover !NUMA systems/builds
>>
>> Signed-off-by: Emil Medve <Emilian.Medve@Freescale•com>
>> ---
>>
>> v2: Acknowledge that NUMA systems/builds are not covered by this patch
>>
>> arch/powerpc/Kconfig | 3 +++
>> arch/powerpc/mm/mem.c | 8 ++++++++
>> 2 files changed, 11 insertions(+)
>>
>> diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
>> index e099899..07b164b 100644
>> --- a/arch/powerpc/Kconfig
>> +++ b/arch/powerpc/Kconfig
>> @@ -475,6 +475,9 @@ config SYS_SUPPORTS_HUGETLBFS
>>
>> source "mm/Kconfig"
>>
>> +config NO_BOOTMEM
>> + def_bool !NUMA
>
>
> There is actually one in mm/Kconfig
>
> So I guess you should make the platform that you are interested
> /tested just do select No_BOOTMEM like we do in arch/arm/Kconfig etc ?
I had a look at what was done for x86 and I missed why the mm/Kconfig
symbol was added. Will include your suggestion in the next version
Cheers,
prev parent reply other threads:[~2014-05-07 19:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 18:48 [PATCH 1/2 v2] bootmem/powerpc: Unify bootmem initialization Emil Medve
2014-05-06 18:48 ` [PATCH 2/2 v2] powerpc: Enable NO_BOOTMEM Emil Medve
2014-05-06 21:49 ` Scott Wood
2014-05-06 22:02 ` Scott Wood
2014-05-07 0:16 ` Emil Medve
2014-05-07 2:44 ` Scott Wood
2014-05-07 21:26 ` Emil Medve
2014-05-07 6:35 ` Aneesh Kumar K.V
2014-05-07 18:37 ` Emil Medve [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=536A7D7E.8070509@Freescale.com \
--to=emilian.medve@freescale$(echo .)com \
--cc=aneesh.kumar@linux$(echo .)vnet.ibm.com \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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