All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Chen Pei <cp0613@linux.alibaba.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	memxor@gmail.com, bjorn@kernel.org, puranjay@kernel.org,
	ihor.solodrai@linux.dev, eddyz87@gmail.com, martin.lau@linux.dev,
	song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
	emil@etsalapatis.com, pulehui@huawei.com, pjw@kernel.org,
	palmer@dabbelt.com, shuah@kernel.org, guoren@kernel.org,
	bpf@vger.kernel.org, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v3 0/4] bpf, riscv: Add support for indirect jumps
Date: Sun, 11 Oct 2026 13:40:11 +0000	[thread overview]
Message-ID: <179172601151.2055679.7493510397466756418.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260928071845.2432-1-cp0613@linux.alibaba.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Mon, 28 Sep 2026 15:18:41 +0800 you wrote:
> The indirect jump instruction (BPF_JMP | BPF_JA | BPF_X, "gotox") and the
> BPF_MAP_TYPE_INSN_ARRAY jump tables it consumes are core features: the
> verifier accepts them on every architecture, and the x86-64, arm64 and
> powerpc JITs implement them. On riscv64 a program using gotox passes
> verification and then fails to load, because the JIT does not know the
> opcode and CONFIG_BPF_JIT_ALWAYS_ON leaves no interpreter to fall back
> onto.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/4] bpf, riscv: Add support for indirect jumps
    https://git.kernel.org/bpf/bpf-next/c/c0316386fecd
  - [bpf-next,v3,2/4] selftests/bpf: Enable gotox tests for riscv64
    https://git.kernel.org/bpf/bpf-next/c/5f750ad6d675
  - [bpf-next,v3,3/4] selftests/bpf: Enable gotox liveness test for riscv64
    https://git.kernel.org/bpf/bpf-next/c/6ce75af4f59e
  - [bpf-next,v3,4/4] selftests/bpf: Enable instruction array test for riscv64
    https://git.kernel.org/bpf/bpf-next/c/eec2444d9b9d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Chen Pei <cp0613@linux.alibaba.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	memxor@gmail.com, bjorn@kernel.org, puranjay@kernel.org,
	ihor.solodrai@linux.dev, eddyz87@gmail.com, martin.lau@linux.dev,
	song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
	emil@etsalapatis.com, pulehui@huawei.com, pjw@kernel.org,
	palmer@dabbelt.com, shuah@kernel.org, guoren@kernel.org,
	bpf@vger.kernel.org, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v3 0/4] bpf, riscv: Add support for indirect jumps
Date: Sun, 11 Oct 2026 13:40:11 +0000	[thread overview]
Message-ID: <179172601151.2055679.7493510397466756418.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260928071845.2432-1-cp0613@linux.alibaba.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Mon, 28 Sep 2026 15:18:41 +0800 you wrote:
> The indirect jump instruction (BPF_JMP | BPF_JA | BPF_X, "gotox") and the
> BPF_MAP_TYPE_INSN_ARRAY jump tables it consumes are core features: the
> verifier accepts them on every architecture, and the x86-64, arm64 and
> powerpc JITs implement them. On riscv64 a program using gotox passes
> verification and then fails to load, because the JIT does not know the
> opcode and CONFIG_BPF_JIT_ALWAYS_ON leaves no interpreter to fall back
> onto.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/4] bpf, riscv: Add support for indirect jumps
    https://git.kernel.org/bpf/bpf-next/c/c0316386fecd
  - [bpf-next,v3,2/4] selftests/bpf: Enable gotox tests for riscv64
    https://git.kernel.org/bpf/bpf-next/c/5f750ad6d675
  - [bpf-next,v3,3/4] selftests/bpf: Enable gotox liveness test for riscv64
    https://git.kernel.org/bpf/bpf-next/c/6ce75af4f59e
  - [bpf-next,v3,4/4] selftests/bpf: Enable instruction array test for riscv64
    https://git.kernel.org/bpf/bpf-next/c/eec2444d9b9d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  parent reply	other threads:[~2026-10-11 13:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28  7:18 [PATCH bpf-next v3 0/4] bpf, riscv: Add support for indirect jumps Chen Pei
2026-09-28  7:18 ` Chen Pei
2026-09-28  7:18 ` [PATCH bpf-next v3 1/4] " Chen Pei
2026-09-28  7:18   ` Chen Pei
2026-09-28  7:18 ` [PATCH bpf-next v3 2/4] selftests/bpf: Enable gotox tests for riscv64 Chen Pei
2026-09-28  7:18   ` Chen Pei
2026-09-28  7:18 ` [PATCH bpf-next v3 3/4] selftests/bpf: Enable gotox liveness test " Chen Pei
2026-09-28  7:18   ` Chen Pei
2026-09-28  7:18 ` [PATCH bpf-next v3 4/4] selftests/bpf: Enable instruction array " Chen Pei
2026-09-28  7:18   ` Chen Pei
2026-09-28  9:10 ` [PATCH bpf-next v3 0/4] bpf, riscv: Add support for indirect jumps Pu Lehui
2026-09-28  9:10   ` Pu Lehui
2026-10-11 13:40 ` patchwork-bot+netdevbpf [this message]
2026-10-11 13:40   ` patchwork-bot+netdevbpf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=179172601151.2055679.7493510397466756418.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bjorn@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=cp0613@linux.alibaba.com \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=emil@etsalapatis.com \
    --cc=guoren@kernel.org \
    --cc=ihor.solodrai@linux.dev \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=pulehui@huawei.com \
    --cc=puranjay@kernel.org \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=yonghong.song@linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.