From: Alexandre Ghiti <alexghiti@rivosinc.com>
To: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Anup Patel <anup@brainfault.org>,
Atish Patra <atish.patra@linux.dev>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
"Alexandre Ghiti" <alexghiti@rivosinc.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Andrew Jones" <ajones@ventanamicro.com>
Subject: [PATCH v5 0/3] Move duplicated instructions macros into asm/insn.h
Date: Fri, 20 Jun 2025 20:21:56 +0000 [thread overview]
Message-ID: <20250620-dev-alex-insn_duplicate_v5_manual-v5-0-d865dc9ad180@rivosinc.com> (raw)
The instructions parsing macros were duplicated and one of them had different
implementations, which is error prone.
So let's consolidate those macros in asm/insn.h.
v1: https://lore.kernel.org/linux-riscv/20250422082545.450453-1-alexghiti@rivosinc.com/
v2: https://lore.kernel.org/linux-riscv/20250508082215.88658-1-alexghiti@rivosinc.com/
v3: https://lore.kernel.org/linux-riscv/20250508125202.108613-1-alexghiti@rivosinc.com/
v4: https://lore.kernel.org/linux-riscv/20250516140805.282770-1-alexghiti@rivosinc.com/
Changes in v5:
- Rebase on top of 6.16-rc1
Changes in v4:
- Rebase on top of for-next (on top of 6.15-rc6)
Changes in v3:
- Fix patch 2 which caused build failures (linux riscv bot), but the
patchset is exactly the same as v2
Changes in v2:
- Rebase on top of 6.15-rc5
- Add RB tags
- Define RV_X() using RV_X_mask() (Clément)
- Remove unused defines (Clément)
- Fix tabulations (Drew)
Signed-off-by: Alexandre Ghiti <alexghiti@rivosinc.com>
---
Alexandre Ghiti (3):
riscv: Fix typo EXRACT -> EXTRACT
riscv: Strengthen duplicate and inconsistent definition of RV_X()
riscv: Move all duplicate insn parsing macros into asm/insn.h
arch/riscv/include/asm/insn.h | 206 +++++++++++++++++++++++++++++----
arch/riscv/kernel/machine_kexec_file.c | 2 +-
arch/riscv/kernel/traps_misaligned.c | 144 +----------------------
arch/riscv/kernel/vector.c | 2 +-
arch/riscv/kvm/vcpu_insn.c | 128 +-------------------
5 files changed, 188 insertions(+), 294 deletions(-)
---
base-commit: 731e998c429974cb141a049c1347a9cab444e44c
change-id: 20250620-dev-alex-insn_duplicate_v5_manual-2c23191c30fb
Best regards,
--
Alexandre Ghiti <alexghiti@rivosinc.com>
next reply other threads:[~2025-06-20 20:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 20:21 Alexandre Ghiti [this message]
2025-06-20 20:21 ` [PATCH v5 1/3] riscv: Fix typo EXRACT -> EXTRACT Alexandre Ghiti
2025-06-20 20:21 ` [PATCH v5 2/3] riscv: Strengthen duplicate and inconsistent definition of RV_X() Alexandre Ghiti
2025-06-20 20:21 ` [PATCH v5 3/3] riscv: Move all duplicate insn parsing macros into asm/insn.h Alexandre Ghiti
2025-06-23 8:07 ` [PATCH v5 0/3] Move duplicated instructions " Clément Léger
2025-06-23 8:48 ` Alexandre Ghiti
2025-06-25 14:20 ` 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=20250620-dev-alex-insn_duplicate_v5_manual-v5-0-d865dc9ad180@rivosinc.com \
--to=alexghiti@rivosinc.com \
--cc=ajones@ventanamicro.com \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@linux.dev \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=philmd@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).