qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Julian Ganz <neither@nut.email>
To: qemu-devel@nongnu.org
Cc: Julian Ganz <neither@nut.email>,
	Yoshinori Sato <ysato@users.sourceforge.jp>
Subject: [PATCH v4 17/23] target/rx: call plugin trap callbacks
Date: Sun, 11 May 2025 15:14:09 +0200	[thread overview]
Message-ID: <012fb70e3b3ae27c79eb99da91a38d8430121c28.1746968215.git.neither@nut.email> (raw)
In-Reply-To: <cover.1746968215.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 Renesas Xtreme targets.

Signed-off-by: Julian Ganz <neither@nut.email>
---
 target/rx/helper.c | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/target/rx/helper.c b/target/rx/helper.c
index 0640ab322b..09f1c25be2 100644
--- a/target/rx/helper.c
+++ b/target/rx/helper.c
@@ -22,6 +22,7 @@
 #include "exec/log.h"
 #include "accel/tcg/cpu-ldst.h"
 #include "hw/irq.h"
+#include "qemu/plugin.h"
 
 void rx_cpu_unpack_psw(CPURXState *env, uint32_t psw, int rte)
 {
@@ -46,6 +47,7 @@ void rx_cpu_do_interrupt(CPUState *cs)
     CPURXState *env = cpu_env(cs);
     int do_irq = cs->interrupt_request & INT_FLAGS;
     uint32_t save_psw;
+    uint64_t last_pc = env->pc;
 
     env->in_sleep = 0;
 
@@ -65,6 +67,7 @@ void rx_cpu_do_interrupt(CPUState *cs)
             env->psw_ipl = 15;
             cs->interrupt_request &= ~CPU_INTERRUPT_FIR;
             qemu_set_irq(env->ack, env->ack_irq);
+            qemu_plugin_vcpu_interrupt_cb(cs, last_pc);
             qemu_log_mask(CPU_LOG_INT, "fast interrupt raised\n");
         } else if (do_irq & CPU_INTERRUPT_HARD) {
             env->isp -= 4;
@@ -75,6 +78,7 @@ void rx_cpu_do_interrupt(CPUState *cs)
             env->psw_ipl = env->ack_ipl;
             cs->interrupt_request &= ~CPU_INTERRUPT_HARD;
             qemu_set_irq(env->ack, env->ack_irq);
+            qemu_plugin_vcpu_interrupt_cb(cs, last_pc);
             qemu_log_mask(CPU_LOG_INT,
                           "interrupt 0x%02x raised\n", env->ack_irq);
         }
@@ -92,6 +96,14 @@ void rx_cpu_do_interrupt(CPUState *cs)
         } else {
             env->pc = cpu_ldl_data(env, env->intb + (vec & 0xff) * 4);
         }
+
+        if (vec == 30) {
+            /* Non-maskable interrupt */
+            qemu_plugin_vcpu_interrupt_cb(cs, last_pc);
+        } else {
+            qemu_plugin_vcpu_exception_cb(cs, last_pc);
+        }
+
         switch (vec) {
         case 20:
             expname = "privilege violation";
-- 
2.49.0



  parent reply	other threads:[~2025-05-11 13:17 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-11 13:13 [PATCH v4 00/23] tcg-plugins: add hooks for discontinuities Julian Ganz
2025-05-11 13:13 ` [PATCH v4 01/23] plugins: add types for callbacks related to certain discontinuities Julian Ganz
2025-05-12 22:35   ` Pierrick Bouvier
2025-05-11 13:13 ` [PATCH v4 02/23] plugins: add API for registering discontinuity callbacks Julian Ganz
2025-05-12 22:36   ` Pierrick Bouvier
2025-05-11 13:13 ` [PATCH v4 03/23] plugins: add hooks for new discontinuity related callbacks Julian Ganz
2025-05-12 22:37   ` Pierrick Bouvier
2025-05-11 13:13 ` [PATCH v4 04/23] contrib/plugins: add plugin showcasing new dicontinuity related API Julian Ganz
2025-05-12 22:45   ` Pierrick Bouvier
2025-05-13  7:22     ` Julian Ganz
2025-05-11 13:13 ` [PATCH v4 05/23] target/alpha: call plugin trap callbacks Julian Ganz
2025-05-11 13:13 ` [PATCH v4 06/23] target/arm: " Julian Ganz
2025-05-11 13:13 ` [PATCH v4 07/23] target/avr: " Julian Ganz
2025-05-11 13:14 ` [PATCH v4 08/23] target/hppa: " Julian Ganz
2025-05-11 13:14 ` [PATCH v4 09/23] target/i386: " Julian Ganz
2025-05-11 13:14 ` [PATCH v4 10/23] target/loongarch: " Julian Ganz
2025-05-11 13:14 ` [PATCH v4 11/23] target/m68k: " Julian Ganz
2025-05-11 13:14 ` [PATCH v4 12/23] target/microblaze: " Julian Ganz
2025-05-11 13:14 ` [PATCH v4 13/23] target/mips: " Julian Ganz
2025-05-11 13:14 ` [PATCH v4 14/23] target/openrisc: " Julian Ganz
2025-05-11 13:14 ` [PATCH v4 15/23] target/ppc: " Julian Ganz
2025-05-11 13:14 ` [PATCH v4 16/23] target/riscv: " Julian Ganz
2025-05-12 12:49   ` Daniel Henrique Barboza
2025-05-12 22:50   ` Alistair Francis
2025-05-11 13:14 ` Julian Ganz [this message]
2025-05-11 13:14 ` [PATCH v4 18/23] target/s390x: " Julian Ganz
2025-05-12  7:47   ` David Hildenbrand
     [not found]     ` <20250512084352.2424-1-ganz@fzi.de>
2025-05-12  8:55       ` Julian Ganz
2025-05-12  9:09       ` David Hildenbrand
2025-05-11 13:14 ` [PATCH v4 19/23] target/sparc: " Julian Ganz
2025-05-11 13:14 ` [PATCH v4 20/23] target/xtensa: " Julian Ganz
2025-05-11 20:40   ` Max Filippov
2025-05-11 13:14 ` [PATCH v4 21/23] tests: add plugin asserting correctness of discon event's to_pc Julian Ganz
2025-05-13  0:25   ` Pierrick Bouvier
2025-05-13  7:45     ` Julian Ganz
2025-05-13 19:15       ` Julian Ganz
2025-05-11 13:22 ` [PATCH v4 22/23] tests: add test for double-traps on rv64 Julian Ganz
2025-05-12 12:50   ` Daniel Henrique Barboza
2025-05-11 13:22 ` [PATCH v4 23/23] tests: add test with interrupted memory accesses " Julian Ganz
2025-05-12 12:51   ` Daniel Henrique Barboza

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=012fb70e3b3ae27c79eb99da91a38d8430121c28.1746968215.git.neither@nut.email \
    --to=neither@nut.email \
    --cc=qemu-devel@nongnu.org \
    --cc=ysato@users.sourceforge.jp \
    /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).