From: Pu Lehui <pulehui@huawei.com>
To: Menglong Dong <menglong8.dong@gmail.com>, <ast@kernel.org>,
<bjorn@kernel.org>
Cc: <daniel@iogearbox.net>, <andrii@kernel.org>,
<martin.lau@linux.dev>, <eddyz87@gmail.com>, <song@kernel.org>,
<yonghong.song@linux.dev>, <john.fastabend@gmail.com>,
<kpsingh@kernel.org>, <sdf@fomichev.me>, <haoluo@google.com>,
<jolsa@kernel.org>, <puranjay@kernel.org>, <pjw@kernel.org>,
<palmer@dabbelt.com>, <aou@eecs.berkeley.edu>, <alex@ghiti.fr>,
<bpf@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <jiang.biao@linux.dev>
Subject: Re: [PATCH bpf-next v4 0/3] bpf: fsession support for riscv
Date: Mon, 9 Feb 2026 21:18:52 +0800 [thread overview]
Message-ID: <036eb7a9-1759-447b-ad94-2d66928f9d71@huawei.com> (raw)
In-Reply-To: <20260208053311.698352-1-dongml2@chinatelecom.cn>
On 2026/2/8 13:33, Menglong Dong wrote:
> Implement bpf fsession for the riscv architecture.
>
> Changes v4 -> v3:
> * fix the build error
> * v3: https://lore.kernel.org/bpf/20260206122002.1494125-1-dongml2@chinatelecom.cn/
>
> Changes v3 -> v2:
> * fix some comments.
> * v2: https://lore.kernel.org/bpf/20260206115823.1070354-1-dongml2@chinatelecom.cn/T/#t
>
> Changes v2 -> v1:
> * use bpf_prog_calls_session_cookie() in invoke_bpf() in the 2nd patch.
> * v1: https://lore.kernel.org/bpf/20260203055231.1088479-1-dongml2@chinatelecom.cn/
>
> Menglong Dong (3):
> bpf, riscv: introduce emit_store_stack_imm64() for trampoline
> bpf, riscv: add fsession support for trampolines
> selftests/bpf: enable fsession_test on riscv64
>
> arch/riscv/net/bpf_jit_comp64.c | 97 +++++++++++++++----
> .../selftests/bpf/progs/get_func_args_test.c | 2 +-
> .../selftests/bpf/progs/get_func_ip_test.c | 2 +-
> 3 files changed, 79 insertions(+), 22 deletions(-)
>
looks good to me, feel free to add
Reviewed-by: Pu Lehui <pulehui@huawei.com>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-02-09 13:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-08 5:33 [PATCH bpf-next v4 0/3] bpf: fsession support for riscv Menglong Dong
2026-02-08 5:33 ` [PATCH bpf-next v4 1/3] bpf, riscv: introduce emit_store_stack_imm64() for trampoline Menglong Dong
2026-02-08 5:33 ` [PATCH bpf-next v4 2/3] bpf, riscv: add fsession support for trampolines Menglong Dong
2026-02-08 5:33 ` [PATCH bpf-next v4 3/3] selftests/bpf: enable fsession_test on riscv64 Menglong Dong
2026-02-09 13:18 ` Pu Lehui [this message]
2026-02-11 21:30 ` [PATCH bpf-next v4 0/3] bpf: fsession support for riscv patchwork-bot+netdevbpf
2026-03-24 6:07 ` patchwork-bot+linux-riscv
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=036eb7a9-1759-447b-ad94-2d66928f9d71@huawei.com \
--to=pulehui@huawei.com \
--cc=alex@ghiti.fr \
--cc=andrii@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=jiang.biao@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=martin.lau@linux.dev \
--cc=menglong8.dong@gmail.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=puranjay@kernel.org \
--cc=sdf@fomichev.me \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox