Hi, all, On Tue, Aug 23, 2022 at 8:46 AM Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx> wrote: > > On Sun, Aug 21, 2022 at 6:36 PM Tiezhu Yang <yangtiezhu@xxxxxxxxxxx> wrote: > > > > > > > > On 08/20/2022 07:50 PM, Tiezhu Yang wrote: > > > The basic support for LoongArch has been merged into the upstream Linux > > > kernel since 5.19-rc1 on June 5, 2022, this patch series adds BPF JIT > > > support for LoongArch. > > > > > > Here is the LoongArch documention: > > > https://www.kernel.org/doc/html/latest/loongarch/index.html > > > > > > With this patch series, the test cases in lib/test_bpf.ko have passed > > > on LoongArch. > > > > > > # echo 1 > /proc/sys/net/core/bpf_jit_enable > > > # modprobe test_bpf > > > # dmesg | grep Summary > > > test_bpf: Summary: 1026 PASSED, 0 FAILED, [1014/1014 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 > > > > > > It seems that this patch series can not be applied cleanly to bpf-next > > > which is not synced to v6.0-rc1. > > > > > > Hi Alexei, Daniel, Andrii, > > > > Do you know which tree this patch series will go through? > > bpf-next or loongarch-next? > > Whichever way is easier. > Looks like all changes are contained within arch/loongarch, > so there should be no conflicts with generic JIT infra. > In that sense it's fine to carry it in loongarch-next. > We can take it through bpf-next too with arch maintainers acks. OK, both ways look good to me. Huacai
