From: Huacai Chen <chenhuacai@loongson.cn>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Huacai Chen <chenhuacai@kernel.org>
Cc: loongarch@lists.linux.dev, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org, Guo Ren <guoren@kernel.org>,
Xuerui Wang <kernel@xen0n.name>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Huacai Chen <chenhuacai@loongson.cn>
Subject: [GIT PULL] LoongArch changes for v6.7
Date: Sun, 12 Nov 2023 13:12:48 +0800 [thread overview]
Message-ID: <20231112051248.272444-1-chenhuacai@loongson.cn> (raw)
The following changes since commit ffc253263a1375a65fa6c9f62a893e9767fbebfa:
Linux 6.6 (2023-10-29 16:31:08 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/chenhuacai/linux-loongson.git tags/loongarch-6.7
for you to fetch changes up to 1d375d65466e5c8d7a9406826d80d475a22e8c6d:
selftests/bpf: Enable cpu v4 tests for LoongArch (2023-11-08 14:12:21 +0800)
----------------------------------------------------------------
LoongArch changes for v6.7
1, Support PREEMPT_DYNAMIC with static keys;
2, Relax memory ordering for atomic operations;
3, Support BPF CPU v4 instructions for LoongArch;
4, Some build and runtime warning fixes.
Note: There is a conflicts in arch/loongarch/include/asm/inst.h but can
be simply fixed by adjusting context.
----------------------------------------------------------------
Hengqi Chen (8):
LoongArch: Add more instruction opcodes and emit_* helpers
LoongArch: BPF: Support sign-extension load instructions
LoongArch: BPF: Support sign-extension mov instructions
LoongArch: BPF: Support unconditional bswap instructions
LoongArch: BPF: Support 32-bit offset jmp instructions
LoongArch: BPF: Support signed div instructions
LoongArch: BPF: Support signed mod instructions
selftests/bpf: Enable cpu v4 tests for LoongArch
Huacai Chen (3):
Merge 'bpf-next 2023-10-16' into loongarch-next
LoongArch: Support PREEMPT_DYNAMIC with static keys
LoongArch/smp: Call rcutree_report_cpu_starting() earlier
Nathan Chancellor (1):
LoongArch: Mark __percpu functions as always inline
WANG Rui (2):
LoongArch: Disable module from accessing external data directly
LoongArch: Relax memory ordering for atomic operations
arch/loongarch/Kconfig | 1 +
arch/loongarch/Makefile | 2 +
arch/loongarch/include/asm/atomic.h | 88 ++++++++++---
arch/loongarch/include/asm/inst.h | 13 ++
arch/loongarch/include/asm/percpu.h | 10 +-
arch/loongarch/kernel/smp.c | 3 +-
arch/loongarch/net/bpf_jit.c | 143 ++++++++++++++++-----
tools/testing/selftests/bpf/progs/test_ldsx_insn.c | 3 +-
tools/testing/selftests/bpf/progs/verifier_bswap.c | 3 +-
tools/testing/selftests/bpf/progs/verifier_gotol.c | 3 +-
tools/testing/selftests/bpf/progs/verifier_ldsx.c | 3 +-
tools/testing/selftests/bpf/progs/verifier_movsx.c | 3 +-
tools/testing/selftests/bpf/progs/verifier_sdiv.c | 3 +-
13 files changed, 215 insertions(+), 63 deletions(-)
next reply other threads:[~2023-11-12 5:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 5:12 Huacai Chen [this message]
2023-11-12 19:18 ` [GIT PULL] LoongArch changes for v6.7 pr-tracker-bot
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=20231112051248.272444-1-chenhuacai@loongson.cn \
--to=chenhuacai@loongson.cn \
--cc=arnd@arndb.de \
--cc=chenhuacai@kernel.org \
--cc=guoren@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel@xen0n.name \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=torvalds@linux-foundation.org \
/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.