From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: multipart/mixed; boundary="===============6728966925201597215=="
MIME-Version: 1.0
From: Xi Wang <xi.wang@gmail.com>
To: kbuild-all@lists.01.org
Subject: Re: [linux-next:master 5640/13335] arch/riscv/net/bpf_jit_comp64.c:1094:47: error: 'BPF_JIT_REGION_START' undeclared
Date: Tue, 31 Mar 2020 08:49:31 -0700
Message-ID: <CAKU6vyax7EQk6Ham4B0POcRGgEnOdvnPSURcqHejV34AnxbH3w@mail.gmail.com>
In-Reply-To: <CAJ+HfNiBbQmgTtc03yJDt3mCwOJmhvhasTNhX_TKktY+dHjYRA@mail.gmail.com>
List-Id: <oe-kbuild-all.lists.linux.dev>

--===============6728966925201597215==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

On Tue, Mar 31, 2020 at 2:49 AM Bj=C3=B6rn T=C3=B6pel <bjorn.topel@gmail.=
com> wrote:
> I'm taking a look right now! Thanks for the ping!

It's likely caused by commit 2191b4f298fa36 ("RISC-V: Move all address
space definition macros to one place").  BPF_JIT_REGION_START etc. are
moved under CONFIG_MMU, which is not set in the attached .config.

Maybe avoid using bpf_jit_alloc_exec and bpf_jit_free_exec in nommu mode?
--===============6728966925201597215==--