lkml.org 
[lkml]   [2019]   [Dec]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: m68k Kconfig warning
Hi Kars,.

On Mon, Dec 2, 2019 at 12:42 PM Kars de Jong <karsdejong@home.nl> wrote:
> Op wo 27 nov. 2019 om 08:12 schreef Geert Uytterhoeven <geert@linux-m68k.org>:
> > On Wed, Nov 27, 2019 at 2:27 AM Randy Dunlap <rdunlap@infradead.org> wrote:
> > > Just noticed this. I don't know what the right fix is.
> > > Would you take care of it, please?
> > >
> > > on Linux 5.4, m68k allmodconfig:
> > >
> > > WARNING: unmet direct dependencies detected for NEED_MULTIPLE_NODES
> > > Depends on [n]: DISCONTIGMEM [=n] || NUMA
> > > Selected by [y]:
> > > - SINGLE_MEMORY_CHUNK [=y] && MMU [=y]
> >
> > This has been basically there forever, but working.
>
> The reason for SINGLE_MEMORY_CHUNK depending on NEED_MULTIPLE_NODES is
> historic due to the way it is implemented.
> I played with it this weekend and I got a working version of FLATMEM,
> which can replace SINGLE_MEMORY_CHUNK.

Nice, thanks!

> step might be to replace DISCONTIGMEM with SPARSEMEM (since
> DISCONTIGMEM has been deprecated).

Mike Rapoport has patches for that:
"[PATCH v2 0/3] m68k/mm: switch from DISCONTIGMEM to SPARSEMEM"

Unfortunately they're not on lore, and there were some issues with them.

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds

\
 
 \ /
  Last update: 2019-12-02 14:32    [W:0.052 / U:9.424 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site