[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wi5DYKbFE4j-jC2HGsKVuf1RpZbEiYt4tSXuxGKiN9oJg@mail.gmail.com>
Date: Mon, 25 Apr 2022 01:17:57 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: "song@...nel.org" <song@...nel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
Rik van Riel <riel@...com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"bpf@...r.kernel.org" <bpf@...r.kernel.org>,
"rick.p.edgecombe@...el.com" <rick.p.edgecombe@...el.com>,
"hch@....de" <hch@....de>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"daniel@...earbox.net" <daniel@...earbox.net>,
"hch@...radead.org" <hch@...radead.org>,
"mcgrof@...nel.org" <mcgrof@...nel.org>,
"ast@...nel.org" <ast@...nel.org>,
Kernel Team <Kernel-team@...com>,
"imbrenda@...ux.ibm.com" <imbrenda@...ux.ibm.com>
Subject: Re: [PATCH v4 bpf 2/4] page_alloc: use vmalloc_huge for large system hash
On Mon, Apr 25, 2022 at 12:07 AM Geert Uytterhoeven
<geert@...ux-m68k.org> wrote:
>
> vmalloc_huge() is provided by mm/vmalloc.c, which is not
> compiled if CONFIG_MMU=n.
Well, that's annoying.
Does this trivial patch fix it for you?
I get this feeling that this could be done better with a weak alias to
__vmalloc(), and that could take care of the "arch doesn't support
VMAP_HUGE" case too, but the attached is the stupid and
straightforward version.
Linus
View attachment "patch.diff" of type "text/x-patch" (426 bytes)
Powered by blists - more mailing lists