From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: Huacai Chen <chenhuacai@kernel.org>, Hengqi Chen <hengqi.chen@gmail.com>
Cc: loongarch@lists.linux.dev, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] LoongArch: BPF: Refine move_imm() and optimize 32-bit operations
Date: Thu, 22 Oct 2026 15:43:58 +0800 [thread overview]
Message-ID: <0b06e77e-540d-19d4-4d9f-de3db1f2c317@loongson.cn> (raw)
In-Reply-To: <20261016081006.26069-1-yangtiezhu@loongson.cn>
On 2026/10/16 下午4:10, Tiezhu Yang wrote:
> v3:
> -- Add a prerequisite patch to detect CPUCFG2_DIV32 feature.
> -- Fix a hardware compatibility bug by checking cpu_has_div32
> before emitting native 32-bit div/mod instructions.
>
> This version is based on v7.3-rc7 and has been tested on Loongson-3A6000
> and Loongson-3A5000 physical machines.
>
> All of the testcases of test_bpf passed on Loongson-3A6000 (with DIV32)
> and Loongson-3A5000 (without DIV32), here are the test results:
>
> $ sudo modprobe test_bpf
> $ dmesg -t | grep Summary
> test_bpf: Summary: 1061 PASSED, 0 FAILED, [1049/1049 JIT'ed]
> test_bpf: test_tail_calls: Summary: 10 PASSED, 0 FAILED, [10/10 JIT'ed]
> test_bpf: test_skb_segment: Summary: 2 PASSED, 0 FAILED
>
> For the BPF selftests test_verifier and test_progs, there are no any
> regressions.
>
> Tiezhu Yang (3):
> LoongArch: Add CPUCFG2 DIV32 feature detection
> LoongArch: BPF: Clean up and decouple is32 parameter from move_imm()
> LoongArch: BPF: Optimize 32-bit operations using native instructions
Hi Huacai, Hengqi,
A gentle ping on the last 2 patches of this series since patch 1
has been applied.
There are no any reports from bot+bpf-ci and sashiko-bot,
and also "test_bpf" and "./test_progs -t jit_insns" tests passed.
Just to clarify the testing status: the 3 failures mentioned in
the previous test report are entirely pre-existing on the clean
bpf-next tree and completely unrelated to this 32-bit optimization
series.
The core ALU32/JMP32 paths introduced here have been fully verified
and passed without any regressions on both 3A6000 and 3A5000 physical
machines.
Do you have any further comments or objections to patches 2 and 3?
If these look good to you, it would be great to have them merged to
avoid rebasing and resending these patches after this merge window.
Thanks,
Tiezhu
next prev parent reply other threads:[~2026-10-22 7:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 8:10 Tiezhu Yang
2026-10-16 8:10 ` [PATCH v3 1/3] LoongArch: Add CPUCFG2 DIV32 feature detection Tiezhu Yang
2026-10-20 10:48 ` Huacai Chen
2026-10-16 8:10 ` [PATCH v3 2/3] LoongArch: BPF: Clean up and decouple is32 parameter from move_imm() Tiezhu Yang
2026-10-27 1:36 ` Hengqi Chen
2026-10-16 8:10 ` [PATCH v3 3/3] LoongArch: BPF: Optimize 32-bit operations using native instructions Tiezhu Yang
2026-10-16 15:18 ` Alexei Starovoitov
2026-10-17 10:58 ` Tiezhu Yang
2026-10-27 2:02 ` Hengqi Chen
2026-10-27 4:10 ` Tiezhu Yang
2026-10-27 8:13 ` Hengqi Chen
2026-10-28 4:19 ` Huacai Chen
2026-10-28 6:55 ` Hengqi Chen
2026-10-22 7:43 ` Tiezhu Yang [this message]
2026-10-23 8:42 ` [PATCH v3 0/3] LoongArch: BPF: Refine move_imm() and optimize 32-bit operations Huacai Chen
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=0b06e77e-540d-19d4-4d9f-de3db1f2c317@loongson.cn \
--to=yangtiezhu@loongson.cn \
--cc=bpf@vger.kernel.org \
--cc=chenhuacai@kernel.org \
--cc=hengqi.chen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.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
all inboxes | Powered by JetHome®