From: Menglong Dong <menglong.dong@linux.dev>
To: Hengqi Chen <hengqi.chen@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, chenhuacai@kernel.org,
yangtiezhu@loongson.cn, vincent.mc.li@gmail.com,
menglong8.dong@gmail.com, loongarch@lists.linux.dev,
bpf@vger.kernel.org, Hengqi Chen <hengqi.chen@gmail.com>
Subject: Re: [PATCH 0/3] bpf: fsession support for LoongArch
Date: Wed, 04 Mar 2026 10:51:22 +0800 [thread overview]
Message-ID: <3398058.aeNJFYEL58@7940hx> (raw)
In-Reply-To: <20260226065952.4082859-1-hengqi.chen@gmail.com>
On 2026/2/26 14:59 Hengqi Chen <hengqi.chen@gmail.com> write:
> This small set implements fsession support for LoongArch.
>
> Patch 1 introduces a helper named emit_store_stack_imm64().
> Patch 2 implements fsession support.
> Patch 3 enable fsession selftests on LoongArch.
I think this series belongs to the bpf-next tree, right? So pls add the
"bpf-next" tag in the next version.
>
> Hengqi Chen (3):
> LoongArch: BPF: Introduce emit_store_stack_imm64() helper
> LoongArch: BPF: Add fsession support for trampolines
> bpf/selftests: Enable fsession tests for LoongArch
>
> arch/loongarch/net/bpf_jit.c | 100 ++++++++++++++----
> .../selftests/bpf/progs/get_func_args_test.c | 3 +-
> .../selftests/bpf/progs/get_func_ip_test.c | 3 +-
> 3 files changed, 83 insertions(+), 23 deletions(-)
>
> --
> 2.43.5
>
>
prev parent reply other threads:[~2026-03-04 2:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 6:59 [PATCH 0/3] bpf: fsession support for LoongArch Hengqi Chen
2026-02-26 6:59 ` [PATCH 1/3] LoongArch: BPF: Introduce emit_store_stack_imm64() helper Hengqi Chen
2026-03-04 2:04 ` Menglong Dong
2026-02-26 6:59 ` [PATCH 2/3] LoongArch: BPF: Add fsession support for trampolines Hengqi Chen
2026-03-04 2:11 ` Menglong Dong
2026-02-26 6:59 ` [PATCH bpf-next 3/3] bpf/selftests: Enable fsession tests for LoongArch Hengqi Chen
2026-02-27 1:59 ` Vincent Li
2026-03-04 1:43 ` Menglong Dong
2026-03-04 2:51 ` Menglong Dong [this message]
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=3398058.aeNJFYEL58@7940hx \
--to=menglong.dong@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chenhuacai@kernel.org \
--cc=daniel@iogearbox.net \
--cc=hengqi.chen@gmail.com \
--cc=loongarch@lists.linux.dev \
--cc=martin.lau@linux.dev \
--cc=menglong8.dong@gmail.com \
--cc=vincent.mc.li@gmail.com \
--cc=yangtiezhu@loongson.cn \
/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