From: Scott Wood <scottwood@freescale.com>
To: Emil Medve <Emilian.Medve@Freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/2 v2] powerpc: Enable NO_BOOTMEM
Date: Tue, 6 May 2014 17:02:54 -0500 [thread overview]
Message-ID: <1399413774.15726.204.camel@snotra.buserror.net> (raw)
In-Reply-To: <1399412988.15726.202.camel@snotra.buserror.net>
On Tue, 2014-05-06 at 16:49 -0500, Scott Wood wrote:
> On Tue, 2014-05-06 at 13:48 -0500, Emil Medve wrote:
> > 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
>
> This will allow a user to manually turn on CONFIG_NO_BOOTMEM in the
> presence of NUMA. From the changelog it sounds like this is not what
> you intended.
Ignore this part -- I see it doesn't have an option string for it to
show up to the user.
-Scott
next prev parent reply other threads:[~2014-05-06 22:03 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 [this message]
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
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=1399413774.15726.204.camel@snotra.buserror.net \
--to=scottwood@freescale.com \
--cc=Emilian.Medve@Freescale.com \
--cc=linuxppc-dev@lists.ozlabs.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).