From: "Julian Ganz" <neither@nut.email>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: "Richard Henderson" <richard.henderson@linaro.org>
Subject: Re: [PATCH v8 05/25] target/alpha: call plugin trap callbacks
Date: Tue, 21 Oct 2025 20:38:23 +0000 [thread overview]
Message-ID: <20bf0927d2331f70d92048726362558d78caa4a8@nut.email> (raw)
In-Reply-To: <2a0a4cde-1427-4d87-a331-f4ed6fa64aa2@linaro.org>
Hi Philippe,
October 21, 2025 at 10:10 PM, "Philippe Mathieu-Daudé" wrote:
> On 19/10/25 17:14, Julian Ganz wrote:
> > 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 Alpha targets.
> > Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
> > Signed-off-by: Julian Ganz <neither@nut.email>
> > ---
> > target/alpha/helper.c | 13 +++++++++++++
> > 1 file changed, 13 insertions(+)
> > diff --git a/target/alpha/helper.c b/target/alpha/helper.c
> > index 096eac3445..a9af52a928 100644
> > --- a/target/alpha/helper.c
> > +++ b/target/alpha/helper.c
> > @@ -27,6 +27,7 @@
> > #include "exec/helper-proto.h"
> > #include "qemu/qemu-print.h"
> > #include "system/memory.h"
> > +#include "qemu/plugin.h"
> > > > #define CONVERT_BIT(X, SRC, DST) \
> > @@ -328,6 +329,7 @@ void alpha_cpu_do_interrupt(CPUState *cs)
> > {
> > CPUAlphaState *env = cpu_env(cs);
> > int i = cs->exception_index;
> > + uint64_t last_pc = env->pc;
> > > if (qemu_loglevel_mask(CPU_LOG_INT)) {
> > static int count;
> > @@ -431,6 +433,17 @@ void alpha_cpu_do_interrupt(CPUState *cs)
> > > /* Switch to PALmode. */
> > env->flags |= ENV_FLAG_PAL_MODE;
> > +
> > + switch (i) {
> > + case EXCP_SMP_INTERRUPT:
> > + case EXCP_CLK_INTERRUPT:
> > + case EXCP_DEV_INTERRUPT:
> > + qemu_plugin_vcpu_interrupt_cb(cs, last_pc);
> > + break;
> > + default:
> > + qemu_plugin_vcpu_exception_cb(cs, last_pc);
> > + break;
> >
> Shouldn't we handle EXCP_CALL_PAL with qemu_plugin_vcpu_hostcall_cb()?
Host calls are exclusively calls that are handled outside the emulation,
on the host, regardless of whether they are hypervisor calls or not. In
that respect EXCP_CALL_PAL looks to me like a regular exception that is
handled by translated code within the emulation.
Regards,
Julian
next prev parent reply other threads:[~2025-10-21 20:39 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 [this message]
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 ` [PATCH v8 16/25] target/riscv: " Julian Ganz
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=20bf0927d2331f70d92048726362558d78caa4a8@nut.email \
--to=neither@nut.email \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
/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).