From: Julian Ganz <neither@nut.email>
To: qemu-devel@nongnu.org
Cc: Julian Ganz <neither@nut.email>,
Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
Alistair Francis <alistair.francis@wdc.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Weiwei Li <liwei1518@gmail.com>,
Liu Zhiwei <zhiwei_liu@linux.alibaba.com>,
qemu-riscv@nongnu.org (open list:RISC-V TCG CPUs)
Subject: [PATCH v8 16/25] target/riscv: call plugin trap callbacks
Date: Sun, 19 Oct 2025 17:15:05 +0200 [thread overview]
Message-ID: <f34d6b43caf46a8fbae929304becb328557259f6.1760884672.git.neither@nut.email> (raw)
In-Reply-To: <cover.1760884672.git.neither@nut.email>
We recently introduced API for registering callbacks for trap related
events as well as the corresponding hook functions. Due to differences
between architectures, the latter need to be called from target specific
code.
This change places hooks for RISC-V targets.
Reviewed-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
Signed-off-by: Julian Ganz <neither@nut.email>
---
target/riscv/cpu_helper.c | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/target/riscv/cpu_helper.c b/target/riscv/cpu_helper.c
index 3479a62cc7..10a10dcd90 100644
--- a/target/riscv/cpu_helper.c
+++ b/target/riscv/cpu_helper.c
@@ -36,6 +36,7 @@
#include "cpu_bits.h"
#include "debug.h"
#include "pmp.h"
+#include "qemu/plugin.h"
int riscv_env_mmu_index(CPURISCVState *env, bool ifetch)
{
@@ -2176,6 +2177,7 @@ void riscv_cpu_do_interrupt(CPUState *cs)
uint64_t hdeleg = async ? env->hideleg : env->hedeleg;
const bool prev_virt = env->virt_enabled;
const target_ulong prev_priv = env->priv;
+ uint64_t last_pc = env->pc;
target_ulong tval = 0;
target_ulong tinst = 0;
target_ulong htval = 0;
@@ -2198,6 +2200,7 @@ void riscv_cpu_do_interrupt(CPUState *cs)
case RISCV_EXCP_SEMIHOST:
do_common_semihosting(cs);
env->pc += 4;
+ qemu_plugin_vcpu_hostcall_cb(cs, last_pc);
return;
#endif
case RISCV_EXCP_LOAD_GUEST_ACCESS_FAULT:
@@ -2467,6 +2470,12 @@ void riscv_cpu_do_interrupt(CPUState *cs)
prev_priv, prev_virt);
}
+ if (async) {
+ qemu_plugin_vcpu_interrupt_cb(cs, last_pc);
+ } else {
+ qemu_plugin_vcpu_exception_cb(cs, last_pc);
+ }
+
/*
* Interrupt/exception/trap delivery is asynchronous event and as per
* zicfilp spec CPU should clear up the ELP state. No harm in clearing
--
2.49.1
next prev parent reply other threads:[~2025-10-19 15:17 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-19 15:14 [PATCH v8 00/25] tcg-plugins: add hooks for discontinuities Julian Ganz
2025-10-19 15:14 ` [PATCH v8 01/25] plugins: add types for callbacks related to certain discontinuities Julian Ganz
2025-10-19 15:14 ` [PATCH v8 02/25] plugins: add API for registering discontinuity callbacks Julian Ganz
2025-10-19 15:14 ` [PATCH v8 03/25] plugins: add hooks for new discontinuity related callbacks Julian Ganz
2025-10-19 15:14 ` [PATCH v8 04/25] contrib/plugins: add plugin showcasing new dicontinuity related API Julian Ganz
2025-10-19 15:14 ` [PATCH v8 05/25] target/alpha: call plugin trap callbacks Julian Ganz
2025-10-21 20:10 ` Philippe Mathieu-Daudé
2025-10-21 20:38 ` Julian Ganz
2025-10-21 20:47 ` Philippe Mathieu-Daudé
2025-10-19 15:14 ` [PATCH v8 06/25] target/arm: " Julian Ganz
2025-10-19 15:14 ` [PATCH v8 07/25] target/avr: " Julian Ganz
2025-10-21 20:10 ` Philippe Mathieu-Daudé
2025-10-19 15:14 ` [PATCH v8 08/25] target/hppa: " Julian Ganz
2025-10-21 19:56 ` Philippe Mathieu-Daudé
2025-10-19 15:14 ` [PATCH v8 09/25] target/i386: " Julian Ganz
2025-10-21 19:57 ` Philippe Mathieu-Daudé
2025-10-19 15:14 ` [PATCH v8 10/25] target/loongarch: " Julian Ganz
2025-10-20 1:36 ` gaosong
2025-10-19 15:15 ` [PATCH v8 11/25] target/m68k: " Julian Ganz
2025-10-21 19:58 ` Philippe Mathieu-Daudé
2025-10-19 15:15 ` [PATCH v8 12/25] target/microblaze: " Julian Ganz
2025-10-21 19:58 ` Philippe Mathieu-Daudé
2025-10-19 15:15 ` [PATCH v8 13/25] target/mips: " Julian Ganz
2025-10-21 19:59 ` Philippe Mathieu-Daudé
2025-10-19 15:15 ` [PATCH v8 14/25] target/openrisc: " Julian Ganz
2025-10-21 19:59 ` Philippe Mathieu-Daudé
2025-10-19 15:15 ` [PATCH v8 15/25] target/ppc: " Julian Ganz
2025-10-19 15:15 ` Julian Ganz [this message]
2025-10-19 15:15 ` [PATCH v8 17/25] target/rx: " Julian Ganz
2025-10-21 20:00 ` Philippe Mathieu-Daudé
2025-10-19 15:15 ` [PATCH v8 18/25] target/s390x: " Julian Ganz
2025-10-21 20:07 ` Philippe Mathieu-Daudé
2025-10-21 20:25 ` Julian Ganz
2025-10-19 15:15 ` [PATCH v8 19/25] target/sh4: " Julian Ganz
2025-10-19 15:15 ` [PATCH v8 20/25] target/sparc: " Julian Ganz
2025-10-21 20:01 ` Philippe Mathieu-Daudé
2025-10-19 15:18 ` [PATCH v8 21/25] target/tricore: " Julian Ganz
2025-10-19 15:18 ` [PATCH v8 22/25] target/xtensa: " Julian Ganz
2025-10-19 15:18 ` [PATCH v8 23/25] tests: add plugin asserting correctness of discon event's to_pc Julian Ganz
2025-10-19 15:18 ` [PATCH v8 24/25] tests: add test for double-traps on rv64 Julian Ganz
2025-10-19 15:18 ` [PATCH v8 25/25] tests: add test with interrupted memory accesses " Julian Ganz
2025-10-21 19:35 ` [PATCH v8 00/25] tcg-plugins: add hooks for discontinuities Alex Bennée
2025-10-23 12:16 ` Alex Bennée
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=f34d6b43caf46a8fbae929304becb328557259f6.1760884672.git.neither@nut.email \
--to=neither@nut.email \
--cc=alistair.francis@wdc.com \
--cc=dbarboza@ventanamicro.com \
--cc=liwei1518@gmail.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).