From: "Julian Ganz" <neither@nut.email>
To: "Richard Henderson" <richard.henderson@linaro.org>,
qemu-devel@nongnu.org
Cc: "Helge Deller" <deller@gmx.de>
Subject: Re: [PATCH v7 08/25] target/hppa: call plugin trap callbacks
Date: Tue, 07 Oct 2025 13:29:34 +0000 [thread overview]
Message-ID: <ceaeff0c68fadcc2069c359aee72dc6c6fd52f90@nut.email> (raw)
In-Reply-To: <411110f3-dcc6-457e-a64b-c038e616d8ae@linaro.org>
Hello Richard,
October 7, 2025 at 12:38 AM, "Richard Henderson" wrote:
> On 10/6/25 02:57, Julian Ganz wrote:
> > @@ -212,6 +214,48 @@ void hppa_cpu_do_interrupt(CPUState *cs)
> > env->iasq_f = 0;
> > env->iasq_b = 0;
> > > + switch (i) {
> > + case EXCP_HPMC:
> > + case EXCP_POWER_FAIL:
> > + case EXCP_RC:
> > + case EXCP_EXT_INTERRUPT:
> > + case EXCP_LPMC:
> > + case EXCP_PER_INTERRUPT:
> > + case EXCP_TOC:
> > + qemu_plugin_vcpu_interrupt_cb(cs, last_pc);
> > + break;
> > + case EXCP_ITLB_MISS:
> > + case EXCP_IMP:
> > + case EXCP_ILL:
> > + case EXCP_BREAK:
> > + case EXCP_PRIV_OPR:
> > + case EXCP_PRIV_REG:
> > + case EXCP_OVERFLOW:
> > + case EXCP_COND:
> > + case EXCP_ASSIST:
> > + case EXCP_DTLB_MISS:
> > + case EXCP_NA_ITLB_MISS:
> > + case EXCP_NA_DTLB_MISS:
> > + case EXCP_DMP:
> > + case EXCP_DMB:
> > + case EXCP_TLB_DIRTY:
> > + case EXCP_PAGE_REF:
> > + case EXCP_ASSIST_EMU:
> > + case EXCP_HPT:
> > + case EXCP_LPT:
> > + case EXCP_TB:
> > + case EXCP_DMAR:
> > + case EXCP_DMPI:
> > + case EXCP_UNALIGN:
> > + case EXCP_SYSCALL:
> > + case EXCP_SYSCALL_LWS:
> >
> These last two are linux-user syscalls. Don't you want hostcall?
Hostcalls only really exist in system emulation mode. For regular
syscalls, we do want to observe the exception in that mode since the
kernel code we switch to is also emulated. For consistency's sake, we
handle it the same for user mode. And there's already a syscall API for
user mode emulation, so it doesn't make much sense to handle them as
host calls.
>
> >
> > + qemu_plugin_vcpu_exception_cb(cs, last_pc);
> > + break;
> > + default:
> > + qemu_plugin_vcpu_interrupt_cb(cs, last_pc);
> >
> g_assert_not_reached().
So that implies that there are no exceptions or interrupts that are not
represented by a EXCP_* constant/definition? In that case I'll rewrite
this with just the interrupts and a default case for all "proper"
syncroneous exceptions.
Regards,
Julian
next prev parent reply other threads:[~2025-10-07 13:31 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 9:56 [PATCH v7 00/25] tcg-plugins: add hooks for discontinuities Julian Ganz
2025-10-06 9:56 ` [PATCH v7 01/25] plugins: add types for callbacks related to certain discontinuities Julian Ganz
2025-10-14 11:06 ` Alex Bennée
2025-10-06 9:56 ` [PATCH v7 02/25] plugins: add API for registering discontinuity callbacks Julian Ganz
2025-10-14 11:06 ` Alex Bennée
2025-10-06 9:56 ` [PATCH v7 03/25] plugins: add hooks for new discontinuity related callbacks Julian Ganz
2025-10-06 9:56 ` [PATCH v7 04/25] contrib/plugins: add plugin showcasing new dicontinuity related API Julian Ganz
2025-10-14 11:08 ` Alex Bennée
2025-10-06 9:57 ` [PATCH v7 05/25] target/alpha: call plugin trap callbacks Julian Ganz
2025-10-06 9:57 ` [PATCH v7 06/25] target/arm: " Julian Ganz
2025-10-06 22:32 ` Richard Henderson
2025-10-06 9:57 ` [PATCH v7 07/25] target/avr: " Julian Ganz
2025-10-06 9:57 ` [PATCH v7 08/25] target/hppa: " Julian Ganz
2025-10-06 22:38 ` Richard Henderson
2025-10-07 13:29 ` Julian Ganz [this message]
2025-10-07 14:56 ` Richard Henderson
2025-10-06 9:57 ` [PATCH v7 09/25] target/i386: " Julian Ganz
2025-10-06 9:57 ` [PATCH v7 10/25] target/loongarch: " Julian Ganz
2025-10-14 10:55 ` Alex Bennée
2025-10-14 14:02 ` Julian Ganz
2025-10-06 9:57 ` [PATCH v7 11/25] target/m68k: " Julian Ganz
2025-10-06 9:57 ` [PATCH v7 12/25] target/microblaze: " Julian Ganz
2025-10-06 9:57 ` [PATCH v7 13/25] target/mips: " Julian Ganz
2025-10-06 9:57 ` [PATCH v7 14/25] target/openrisc: " Julian Ganz
2025-10-06 9:57 ` [PATCH v7 15/25] target/ppc: " Julian Ganz
2025-10-06 9:57 ` [PATCH v7 16/25] target/riscv: " Julian Ganz
2025-10-06 9:57 ` [PATCH v7 17/25] target/rx: " Julian Ganz
2025-10-06 9:57 ` [PATCH v7 18/25] target/s390x: " Julian Ganz
2025-10-06 9:57 ` [PATCH v7 19/25] target/sh4: " Julian Ganz
2025-10-06 9:57 ` [PATCH v7 20/25] target/sparc: " Julian Ganz
2025-10-06 9:59 ` [PATCH v7 21/25] target/tricore: " Julian Ganz
2025-10-06 9:59 ` [PATCH v7 22/25] target/xtensa: " Julian Ganz
2025-10-07 11:59 ` Philippe Mathieu-Daudé
2025-10-06 9:59 ` [PATCH v7 23/25] tests: add plugin asserting correctness of discon event's to_pc Julian Ganz
2025-10-06 9:59 ` [PATCH v7 24/25] tests: add test for double-traps on rv64 Julian Ganz
2025-10-09 2:49 ` Alistair Francis
2025-10-06 9:59 ` [PATCH v7 25/25] tests: add test with interrupted memory accesses " Julian Ganz
2025-10-14 12:47 ` Alex Bennée
2025-10-14 14:17 ` Julian Ganz
2025-10-14 12:52 ` [PATCH v7 00/25] tcg-plugins: add hooks for discontinuities 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=ceaeff0c68fadcc2069c359aee72dc6c6fd52f90@nut.email \
--to=neither@nut.email \
--cc=deller@gmx.de \
--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).