From: guoren@kernel.org
To: guoren@kernel.org, palmer@dabbelt.com, paul.walmsley@sifive.com,
mhiramat@kernel.org, conor.dooley@microchip.com,
penberg@kernel.org, mark.rutland@arm.com, jrtc27@jrtc27.com,
andy.chiu@sifive.com, zong.li@sifive.com
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Guo Ren <guoren@linux.alibaba.com>
Subject: [PATCH -next V3 0/2] riscv: jump_label: Fixup & Optimization
Date: Thu, 26 Jan 2023 12:06:05 -0500 [thread overview]
Message-ID: <20230126170607.1489141-1-guoren@kernel.org> (raw)
From: Guo Ren <guoren@linux.alibaba.com>
Patch 1 is the fixup patch should be merged into stable-tree.
Patch 2 is a continuous optimization for jump_label patch_text
atomicity.
Changes in V3:
- Correct the typo C.JAL -> C.J (Thx Jessica)
- Fixup compile error when CONFIG_RISCV_ISA_C=n
- Rebase on riscv for-next (20230127)
Changes in V2:
https://lore.kernel.org/linux-riscv/20221210100927.835145-3-guoren@kernel.org/
Changes in V1:
https://lore.kernel.org/linux-riscv/20220913094252.3555240-6-andy.chiu@sifive.com/
Andy Chiu (1):
riscv: jump_label: Fixup unaligned arch_static_branch function
Guo Ren (1):
riscv: jump_label: Optimize the code size with compressed instruction
arch/riscv/include/asm/jump_label.h | 14 ++++++++++++--
arch/riscv/kernel/jump_label.c | 30 +++++++++++++++++++++++++++--
2 files changed, 40 insertions(+), 4 deletions(-)
--
2.36.1
next reply other threads:[~2023-01-26 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 17:06 guoren [this message]
2023-01-26 17:06 ` [PATCH -next V3 1/2] riscv: jump_label: Fixup unaligned arch_static_branch function guoren
2023-01-30 11:57 ` Björn Töpel
2023-01-31 13:35 ` Guo Ren
2023-01-26 17:06 ` [PATCH -next V3 2/2] riscv: jump_label: Optimize the code size with compressed instruction guoren
2023-02-22 15:00 ` [PATCH -next V3 0/2] riscv: jump_label: Fixup & Optimization 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=20230126170607.1489141-1-guoren@kernel.org \
--to=guoren@kernel.org \
--cc=andy.chiu@sifive.com \
--cc=conor.dooley@microchip.com \
--cc=guoren@linux.alibaba.com \
--cc=jrtc27@jrtc27.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=penberg@kernel.org \
--cc=zong.li@sifive.com \
/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