[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAGM2reb=KeLH7KKUP+7-u27nJxvTcBskhtS2cDH8SwiiEZ1jNQ@mail.gmail.com>
Date: Thu, 12 Jul 2018 11:09:20 -0400
From: Pavel Tatashin <pasha.tatashin@...cle.com>
To: osalvador@...hadventures.net
Cc: mpe@...erman.id.au, osalvador.vilardaga@...il.com,
Andrew Morton <akpm@...ux-foundation.org>, broonie@...nel.org,
mhocko@...e.cz, Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, linux-fsdevel@...r.kernel.org,
Linux Memory Management List <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>, mm-commits@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, bhe@...hat.com,
aneesh.kumar@...ux.ibm.com, khandual@...ux.vnet.ibm.com
Subject: Re: Boot failures with "mm/sparse: Remove CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER"
on powerpc (was Re: mmotm 2018-07-10-16-50 uploaded)
On Thu, Jul 12, 2018 at 5:50 AM Oscar Salvador
<osalvador@...hadventures.net> wrote:
>
> > > I just roughly check, but if I checked the right place,
> > > vmemmap_populated() checks for the section to contain the flags we are
> > > setting in sparse_init_one_section().
> >
> > Yes.
> >
> > > But with this patch, we populate first everything, and then we call
> > > sparse_init_one_section() in sparse_init().
> > > As I said I could be mistaken because I just checked the surface.
Yes, this is right, sparse_init_one_section() is needed after every
populate call on ppc64. I am adding this to my sparse_init re-write,
and it actually simplifies code, as it avoids one extra loop, and
makes ppc64 to work.
Pavel
Powered by blists - more mailing lists