[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ+HfNgOrx1D-tSxXsoZsMxZtHX-Ksdeg8bZFFPRPGChup4oFg@mail.gmail.com>
Date: Mon, 3 Feb 2020 13:28:35 +0100
From: Björn Töpel <bjorn.topel@...il.com>
To: Alex Ghiti <alex@...ti.fr>
Cc: Daniel Borkmann <daniel@...earbox.net>,
Alexei Starovoitov <ast@...nel.org>,
Netdev <netdev@...r.kernel.org>, linux-riscv@...ts.infradead.org,
bpf <bpf@...r.kernel.org>, Anup Patel <anup@...infault.org>,
vincent.chen@...ive.com
Subject: Re: [PATCH bpf-next v2 6/9] riscv, bpf: provide RISC-V specific JIT
image alloc/free
On Sun, 2 Feb 2020 at 14:37, Alex Ghiti <alex@...ti.fr> wrote:
>
[...]
>
> I think it would be better to completely avoid this patch and the
> definition of this
> new zone by using the generic implementation if we had the patch
> discussed here
> regarding modules memory allocation (that in any case we need to fix
> modules loading):
>
> https://lore.kernel.org/linux-riscv/d868acf5-7242-93dc-0051-f97e64dc4387@ghiti.fr/T/#m2be30cb71dc9aa834a50d346961acee26158a238
>
This patch is already upstream. I agree that when the module
allocation fix is upstream, the BPF image allocation can be folded
into the module allocation. IOW, I wont send any page table dumper
patch for BPF memory.
But keep in mind that the RV BPF JIT relies on having the kernel text
within the 32b range (as does modules)
Cheers,
Björn
Powered by blists - more mailing lists