From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: Paul Burton <paul.burton@mips.com>
Cc: Serge Semin <fancer.lancer@gmail.com>,
Ralf Baechle <ralf@linux-mips.org>,
James Hogan <jhogan@kernel.org>, Huacai Chen <chenhc@lemote.com>,
Michal Hocko <mhocko@kernel.org>,
linux-mips@linux-mips.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mips: switch to NO_BOOTMEM
Date: Sat, 15 Sep 2018 15:58:07 +0300 [thread overview]
Message-ID: <20180915125806.GH15191@rapoport-lnx> (raw)
In-Reply-To: <20180914195300.7wnmsph2qhpixm7s@pburton-laptop>
On Fri, Sep 14, 2018 at 12:53:00PM -0700, Paul Burton wrote:
> Hi Mike,
>
> On Mon, Sep 10, 2018 at 12:23:18PM +0300, Mike Rapoport wrote:
> > MIPS already has memblock support and all the memory is already registered
> > with it.
> >
> > This patch replaces bootmem memory reservations with memblock ones and
> > removes the bootmem initialization.
> >
> > Since memblock allocates memory in top-down mode, we ensure that memblock
> > limit is max_low_pfn to prevent allocations from the high memory.
> >
> > To have the exceptions base in the lower 512M of the physical memory, its
> > allocation in arch/mips/kernel/traps.c::traps_init() is using bottom-up
> > mode.
> >
> > Signed-off-by: Mike Rapoport <rppt@linux.vnet.ibm.com>
> > ---
> > v2:
> > * set memblock limit to max_low_pfn to avoid allocation attempts from high
> > memory
> > * use boottom-up mode for allocation of the exceptions base
> >
> > Build tested with *_defconfig.
> > Boot tested with qemu-system-mips64el for 32r6el, 64r6el and fuloong2e
> > defconfigs.
> > Boot tested with qemu-system-mipsel for malta defconfig.
> >
> > arch/mips/Kconfig | 1 +
> > arch/mips/kernel/setup.c | 99 ++++++++--------------------------
> > arch/mips/kernel/traps.c | 3 ++
> > arch/mips/loongson64/loongson-3/numa.c | 34 ++++++------
> > arch/mips/sgi-ip27/ip27-memory.c | 11 ++--
> > 5 files changed, 46 insertions(+), 102 deletions(-)
>
> Thanks - applied to mips-next for 4.20.
>
> Apologies for the delay, my son decided to be born a few weeks early &
> scupper my plans :)
Congratulations! :)
> Paul
>
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2018-09-15 12:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 9:23 [PATCH v2] mips: switch to NO_BOOTMEM Mike Rapoport
2018-09-14 19:53 ` Paul Burton
2018-09-15 12:58 ` Mike Rapoport [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=20180915125806.GH15191@rapoport-lnx \
--to=rppt@linux.vnet.ibm.com \
--cc=chenhc@lemote.com \
--cc=fancer.lancer@gmail.com \
--cc=jhogan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=paul.burton@mips.com \
--cc=ralf@linux-mips.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).