[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdW1iqNkmCztAv93W4eLR5ooxh5m+vRLJHJmCfrjsOmc5g@mail.gmail.com>
Date: Mon, 2 Dec 2019 14:32:28 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Kars de Jong <karsdejong@...e.nl>
Cc: Randy Dunlap <rdunlap@...radead.org>,
Mike Rapoport <rppt@...ux.ibm.com>,
linux-m68k <linux-m68k@...ts.linux-m68k.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: m68k Kconfig warning
Hi Kars,.
On Mon, Dec 2, 2019 at 12:42 PM Kars de Jong <karsdejong@...e.nl> wrote:
> Op wo 27 nov. 2019 om 08:12 schreef Geert Uytterhoeven <geert@...ux-m68k.org>:
> > On Wed, Nov 27, 2019 at 2:27 AM Randy Dunlap <rdunlap@...radead.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@...ux-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
Powered by blists - more mailing lists