From: Nam Cao <namcaov@gmail.com>
To: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Nam Cao <namcaov@gmail.com>
Subject: [PATCH 0/3] riscv: kprobes: simulate some instructions
Date: Sun, 30 Jul 2023 10:27:06 +0200 [thread overview]
Message-ID: <cover.1690704360.git.namcaov@gmail.com> (raw)
Simulate some currently rejected instructions. Still to be simulated are:
- c.jal
- c.ebreak
Nam Cao (3):
riscv: kprobes: simulate c.j instruction
riscv: kprobes: simulate c.jr and c.jalr instructions
riscv: kprobes: simulate c.beqz and c.bnez
arch/riscv/kernel/probes/decode-insn.c | 11 +-
arch/riscv/kernel/probes/simulate-insn.c | 105 +++++++++
arch/riscv/kernel/probes/simulate-insn.h | 5 +
drivers/test_kprobe/Makefile | 3 +
drivers/test_kprobe/test_kprobe.c | 265 +++++++++++++++++++++++
5 files changed, 384 insertions(+), 5 deletions(-)
create mode 100644 drivers/test_kprobe/Makefile
create mode 100644 drivers/test_kprobe/test_kprobe.c
--
2.34.1
next reply other threads:[~2023-07-30 8:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 8:27 Nam Cao [this message]
2023-07-30 8:27 ` [PATCH 1/3] riscv: kprobes: simulate c.j instruction Nam Cao
2023-08-09 0:11 ` Charlie Jenkins
2023-08-09 1:05 ` Charlie Jenkins
2023-07-30 8:27 ` [PATCH 2/3] riscv: kprobes: simulate c.jr and c.jalr instructions Nam Cao
2023-08-09 1:06 ` Charlie Jenkins
2023-07-30 8:27 ` [PATCH 3/3] riscv: kprobes: simulate c.beqz and c.bnez Nam Cao
2023-08-09 1:14 ` Charlie Jenkins
2023-07-30 8:27 ` test code for kprobe Nam Cao
2023-08-14 12:28 ` Björn Töpel
2023-08-14 13:50 ` Nam Cao
2023-08-14 14:10 ` Björn Töpel
2023-08-30 13:20 ` [PATCH 0/3] riscv: kprobes: simulate some instructions 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=cover.1690704360.git.namcaov@gmail.com \
--to=namcaov@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--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