From: Alexandre Ghiti <alex@ghiti.fr>
To: Nam Cao <namcao@linutronix.de>, patchwork-bot+linux-riscv@kernel.org
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 00/11] riscv: kprobes: Clean up instruction simulation
Date: Tue, 8 Jul 2025 15:27:23 +0200 [thread overview]
Message-ID: <9bf5fc76-4bb2-4baf-88fe-e593b451f0ff@ghiti.fr> (raw)
In-Reply-To: <20250708102537.VovauOQC@linutronix.de>
Hi Nam,
On 7/8/25 12:25, Nam Cao wrote:
> On Wed, Jun 04, 2025 at 02:33:06PM +0000, patchwork-bot+linux-riscv@kernel.org wrote:
>> Hello:
>>
>> This series was applied to riscv/linux.git (for-next)
>> by Alexandre Ghiti <alexghiti@rivosinc.com>:
>>
>> On Wed, 14 May 2025 11:38:39 +0200 you wrote:
>>> Hi,
>>>
>>> There is some instruction-processing code in kprobes simulate code. These
>>> code should be insn.h. In fact, most of them is duplicating insn.h.
>>>
>>> This series remove the duplicated bits and make use of macros already
>>> defined in insn.h. The non-duplicated bits are moved into insn.h.
>>>
>>> [...]
>> Here is the summary with links:
>> - [v2,01/11] riscv: kprobes: Move branch_rs2_idx to insn.h
>> https://git.kernel.org/riscv/c/d29656bab74c
>> - [v2,02/11] riscv: kprobes: Move branch_funct3 to insn.h
>> https://git.kernel.org/riscv/c/da6de46c2eed
>> - [v2,03/11] riscv: kprobes: Remove duplication of RV_EXTRACT_JTYPE_IMM
>> https://git.kernel.org/riscv/c/6d47d903b18f
>> - [v2,04/11] riscv: kprobes: Remove duplication of RV_EXTRACT_RS1_REG
>> https://git.kernel.org/riscv/c/5cefc323f32a
>> - [v2,05/11] riscv: kprobes: Remove duplication of RV_EXTRACT_BTYPE_IMM
>> https://git.kernel.org/riscv/c/a285674909ae
>> - [v2,06/11] riscv: kproves: Remove duplication of RVC_EXTRACT_JTYPE_IMM
>> https://git.kernel.org/riscv/c/c7196c136e29
>> - [v2,07/11] riscv: kprobes: Remove duplication of RVC_EXTRACT_C2_RS1_REG
>> https://git.kernel.org/riscv/c/768007ca3fe8
>> - [v2,08/11] riscv: kprobes: Remove duplication of RVC_EXTRACT_BTYPE_IMM
>> https://git.kernel.org/riscv/c/f2c715fff676
>> - [v2,09/11] riscv: kprobes: Remove duplication of RV_EXTRACT_RD_REG
>> https://git.kernel.org/riscv/c/284ca2a100de
>> - [v2,10/11] riscv: kprobes: Remove duplication of RV_EXTRACT_UTYPE_IMM
>> https://git.kernel.org/riscv/c/a60c2933ec74
>> - [v2,11/11] riscv: kprobes: Remove duplication of RV_EXTRACT_ITYPE_IMM
>> https://git.kernel.org/riscv/c/ee4c45f5cbeb
> This series was dropped from 6.16 due to conflict. Can it be re-applied? It
> applies cleanly to riscv/for-next.
>
> The same story for:
> https://lore.kernel.org/linux-riscv/174904758974.2309006.8809303189389627595.git-patchwork-notify@kernel.org/
Yes, I have both in my for-next branch, sorry I did not advertise that
(I'm working on it).
FYI, I have enabled kunit tests in the upstream kernel CI:
https://github.com/linux-riscv/linux/actions/runs/15967114709/job/45030410210?pr=571#step:5:625
Thanks,
Alex
>
> Best regards,
> Nam
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2025-07-08 13:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 9:38 Nam Cao
2025-05-14 9:38 ` [PATCH v2 01/11] riscv: kprobes: Move branch_rs2_idx to insn.h Nam Cao
2025-05-14 9:38 ` [PATCH v2 02/11] riscv: kprobes: Move branch_funct3 " Nam Cao
2025-05-14 9:38 ` [PATCH v2 03/11] riscv: kprobes: Remove duplication of RV_EXTRACT_JTYPE_IMM Nam Cao
2025-05-14 9:38 ` [PATCH v2 04/11] riscv: kprobes: Remove duplication of RV_EXTRACT_RS1_REG Nam Cao
2025-05-14 9:38 ` [PATCH v2 05/11] riscv: kprobes: Remove duplication of RV_EXTRACT_BTYPE_IMM Nam Cao
2025-05-14 9:38 ` [PATCH v2 06/11] riscv: kproves: Remove duplication of RVC_EXTRACT_JTYPE_IMM Nam Cao
2025-05-14 9:38 ` [PATCH v2 07/11] riscv: kprobes: Remove duplication of RVC_EXTRACT_C2_RS1_REG Nam Cao
2025-05-14 9:38 ` [PATCH v2 08/11] riscv: kprobes: Remove duplication of RVC_EXTRACT_BTYPE_IMM Nam Cao
2025-05-14 9:38 ` [PATCH v2 09/11] riscv: kprobes: Remove duplication of RV_EXTRACT_RD_REG Nam Cao
2025-05-14 9:38 ` [PATCH v2 10/11] riscv: kprobes: Remove duplication of RV_EXTRACT_UTYPE_IMM Nam Cao
2025-05-14 9:38 ` [PATCH v2 11/11] riscv: kprobes: Remove duplication of RV_EXTRACT_ITYPE_IMM Nam Cao
2025-06-04 14:33 ` [PATCH v2 00/11] riscv: kprobes: Clean up instruction simulation patchwork-bot+linux-riscv
2025-07-08 10:25 ` Nam Cao
2025-07-08 13:27 ` Alexandre Ghiti [this message]
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=9bf5fc76-4bb2-4baf-88fe-e593b451f0ff@ghiti.fr \
--to=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=namcao@linutronix.de \
--cc=palmer@dabbelt.com \
--cc=patchwork-bot+linux-riscv@kernel.org \
--cc=paul.walmsley@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
all inboxes | Powered by JetHome®