qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Julian Ganz <neither@nut.email>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: Julian Ganz <neither@nut.email>,
	Stafford Horne <shorne@gmail.com>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH v5 14/25] target/openrisc: call plugin trap callbacks
Date: Sun, 25 May 2025 22:56:43 +0200	[thread overview]
Message-ID: <20250525205645.4366-3-neither@nut.email> (raw)
In-Reply-To: <083923f4-26d2-4132-8ab0-80c3b465c036@linaro.org>

Hi Richard,

> On 5/19/25 16:19, Julian Ganz wrote:
> > diff --git a/target/openrisc/interrupt.c b/target/openrisc/interrupt.c
> > index 486823094c..08f0ed9b89 100644
> > --- a/target/openrisc/interrupt.c
> > +++ b/target/openrisc/interrupt.c
> > @@ -25,11 +25,13 @@
> >   #ifndef CONFIG_USER_ONLY
> >   #include "hw/loader.h"
> >   #endif
> > +#include "qemu/plugin.h"
> >   
> >   void openrisc_cpu_do_interrupt(CPUState *cs)
> >   {
> >       CPUOpenRISCState *env = cpu_env(cs);
> >       int exception = cs->exception_index;
> > +    uint64_t last_pc = env->pc;
> >   
> >       env->epcr = env->pc;
> >   
> > @@ -98,6 +100,17 @@ void openrisc_cpu_do_interrupt(CPUState *cs)
> >           cpu_abort(cs, "Unhandled exception 0x%x\n", exception);
> >       }
> >   
> > +    switch (exception) {
> > +    case EXCP_RESET:
> 
> There are plenty of other EXCP_RESET uses that aren't marked as interrupt.
> Bug?

Mh... I might not have been perfectly consistent with resets. We do expect
plugins to be notified of resets already, so we probably don't want to trigger
exception or interrupt callbacks.

I'll check and adjust for the next series.

Regards,
Julian


  reply	other threads:[~2025-05-25 20:58 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-19 15:19 [PATCH v5 00/25] tcg-plugins: add hooks for discontinuities Julian Ganz
2025-05-19 15:19 ` [PATCH v5 01/25] plugins: add types for callbacks related to certain discontinuities Julian Ganz
2025-05-24 16:43   ` Richard Henderson
2025-05-19 15:19 ` [PATCH v5 02/25] plugins: add API for registering discontinuity callbacks Julian Ganz
2025-05-24 16:48   ` Richard Henderson
2025-05-19 15:19 ` [PATCH v5 03/25] plugins: add hooks for new discontinuity related callbacks Julian Ganz
2025-05-24 16:55   ` Richard Henderson
2025-05-25 20:56     ` Julian Ganz
2025-05-26  8:08       ` Julian Ganz
2025-05-26  9:02         ` Richard Henderson
2025-05-24 17:27   ` Richard Henderson
2025-05-25 20:56     ` Julian Ganz
2025-05-19 15:19 ` [PATCH v5 04/25] contrib/plugins: add plugin showcasing new dicontinuity related API Julian Ganz
2025-05-19 15:19 ` [PATCH v5 05/25] target/alpha: call plugin trap callbacks Julian Ganz
2025-05-24 16:56   ` Richard Henderson
2025-05-25 12:14   ` Richard Henderson
2025-05-25 20:16     ` Julian Ganz
2025-05-26  9:01       ` Richard Henderson
2025-05-26  9:54         ` Julian Ganz
2025-05-26 16:22           ` Richard Henderson
2025-05-19 15:19 ` [PATCH v5 06/25] target/arm: " Julian Ganz
2025-05-24 17:05   ` Richard Henderson
2025-05-19 15:19 ` [PATCH v5 07/25] target/avr: " Julian Ganz
2025-05-24 17:06   ` Richard Henderson
2025-05-19 15:19 ` [PATCH v5 08/25] target/hppa: " Julian Ganz
2025-05-24 17:07   ` Richard Henderson
2025-05-24 23:19     ` Julian Ganz
2025-05-19 15:19 ` [PATCH v5 09/25] target/i386: " Julian Ganz
2025-05-19 15:19 ` [PATCH v5 10/25] target/loongarch: " Julian Ganz
2025-05-24 17:10   ` Richard Henderson
2025-05-19 15:19 ` [PATCH v5 11/25] target/m68k: " Julian Ganz
2025-05-24 17:19   ` Richard Henderson
2025-05-19 15:19 ` [PATCH v5 12/25] target/microblaze: " Julian Ganz
2025-05-24 17:21   ` Richard Henderson
2025-05-19 15:19 ` [PATCH v5 13/25] target/mips: " Julian Ganz
2025-05-24 17:23   ` Richard Henderson
2025-05-19 15:19 ` [PATCH v5 14/25] target/openrisc: " Julian Ganz
2025-05-24 17:25   ` Richard Henderson
2025-05-25 20:56     ` Julian Ganz [this message]
2025-05-19 15:19 ` [PATCH v5 15/25] target/ppc: " Julian Ganz
2025-05-24 17:30   ` Richard Henderson
2025-05-26 10:04     ` Julian Ganz
2025-05-19 15:19 ` [PATCH v5 16/25] target/riscv: " Julian Ganz
2025-05-19 15:19 ` [PATCH v5 17/25] target/rx: " Julian Ganz
2025-05-24 17:34   ` Richard Henderson
2025-05-19 15:19 ` [PATCH v5 18/25] target/s390x: " Julian Ganz
2025-05-24 17:36   ` Richard Henderson
2025-05-19 15:19 ` [PATCH v5 19/25] target/sh4: " Julian Ganz
2025-05-24 17:38   ` Richard Henderson
2025-05-19 15:20 ` [PATCH v5 20/25] target/sparc: " Julian Ganz
2025-05-24 17:41   ` Richard Henderson
2025-05-19 15:20 ` [PATCH v5 21/25] target/tricore: " Julian Ganz
2025-05-20 14:25   ` Bastian Koppelmann
2025-05-24 17:44   ` Richard Henderson
2025-05-19 15:20 ` [PATCH v5 22/25] target/xtensa: " Julian Ganz
2025-05-19 15:24 ` [PATCH v5 23/25] tests: add plugin asserting correctness of discon event's to_pc Julian Ganz
2025-05-20 20:01   ` Pierrick Bouvier
2025-05-20 20:44     ` Julian Ganz
2025-05-20 21:09       ` Pierrick Bouvier
2025-05-21 19:03         ` Pierrick Bouvier
2025-05-19 15:24 ` [PATCH v5 24/25] tests: add test for double-traps on rv64 Julian Ganz
2025-05-19 15:24 ` [PATCH v5 25/25] tests: add test with interrupted memory accesses " Julian Ganz
2025-09-02 10:20 ` [PATCH v5 00/25] tcg-plugins: add hooks for discontinuities Alex Bennée
2025-09-02 11:49   ` Julian Ganz

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=20250525205645.4366-3-neither@nut.email \
    --to=neither@nut.email \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=shorne@gmail.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).