[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240429115643.7df77e08@kernel.org>
Date: Mon, 29 Apr 2024 11:56:43 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Daniel Borkmann <daniel@...earbox.net>, Alexei Starovoitov
<ast@...nel.org>, Andrii Nakryiko <andrii@...nel.org>, David Miller
<davem@...emloft.net>, Paolo Abeni <pabeni@...hat.com>, bpf
<bpf@...r.kernel.org>, Networking <netdev@...r.kernel.org>, Linux Kernel
Mailing List <linux-kernel@...r.kernel.org>, Linux Next Mailing List
<linux-next@...r.kernel.org>, Martin KaFai Lau <martin.lau@...nel.org>,
Puranjay Mohan <puranjay12@...il.com>, Puranjay Mohan <puranjay@...nel.org>
Subject: Re: linux-next: manual merge of the bpf-next tree with the net tree
On Mon, 29 Apr 2024 11:49:39 +1000 Stephen Rothwell wrote:
> +u64 __weak bpf_arch_uaddress_limit(void)
> +{
> +#if defined(CONFIG_64BIT) && defined(CONFIG_ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE)
> + return TASK_SIZE;
> +#else
> + return 0;
> +#endif
> +}
> +
> + bool __weak bpf_jit_supports_insn(struct bpf_insn *insn, bool in_arena)
> + {
> + return false;
> + }
Thanks! FTR I plan to used the inverse order, if that matters..
Powered by blists - more mailing lists