From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Subject: Re: [PATCH v5 11/25] target/m68k: call plugin trap callbacks
Date: Sat, 24 May 2025 18:19:50 +0100 [thread overview]
Message-ID: <be2f91dc-c156-4f1b-95b0-2e7be3a860d4@linaro.org> (raw)
In-Reply-To: <d559b98b46bf7c9a410a0ff4ff7ca4a5cc403281.1747666625.git.neither@nut.email>
On 5/19/25 16:19, 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 Motorola 68000 targets.
>
> Signed-off-by: Julian Ganz <neither@nut.email>
> ---
> target/m68k/op_helper.c | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/target/m68k/op_helper.c b/target/m68k/op_helper.c
> index f29ae12af8..ca15af5765 100644
> --- a/target/m68k/op_helper.c
> +++ b/target/m68k/op_helper.c
> @@ -22,6 +22,7 @@
> #include "exec/helper-proto.h"
> #include "accel/tcg/cpu-ldst.h"
> #include "semihosting/semihost.h"
> +#include "qemu/plugin.h"
>
> #if !defined(CONFIG_USER_ONLY)
>
> @@ -183,6 +184,21 @@ static const char *m68k_exception_name(int index)
> return "Unassigned";
> }
>
> +static void do_plugin_vcpu_interrupt_cb(CPUState *cs, uint64_t from)
> +{
> + switch (cs->exception_index) {
> + case EXCP_SPURIOUS ... EXCP_INT_LEVEL_7:
> + qemu_plugin_vcpu_interrupt_cb(cs, from);
> + break;
> + case EXCP_SEMIHOSTING:
> + qemu_plugin_vcpu_hostcall_cb(cs, from);
> + break;
> + default:
> + qemu_plugin_vcpu_exception_cb(cs, from);
> + break;
> + }
> +}
> +
> static void cf_interrupt_all(CPUM68KState *env, int is_hw)
> {
> CPUState *cs = env_cpu(env);
> @@ -200,9 +216,11 @@ static void cf_interrupt_all(CPUM68KState *env, int is_hw)
> case EXCP_RTE:
> /* Return from an exception. */
> cf_rte(env);
> + qemu_plugin_vcpu_exception_cb(cs, retaddr);
> return;
EXCP_RTE is not an architectural exception, it's qemu implementation detail. Think
"subroutine return, and also pop cpu state". I don't think you should expose this.
Certainly you're not instrumenting "return from exception" for other targets.
> @@ -277,12 +297,14 @@ static void m68k_interrupt_all(CPUM68KState *env, int is_hw)
> uint32_t sp;
> uint32_t vector;
> uint16_t sr, oldsr;
> + uint64_t last_pc = env->pc;
>
> if (!is_hw) {
> switch (cs->exception_index) {
> case EXCP_RTE:
> /* Return from an exception. */
> m68k_rte(env);
> + qemu_plugin_vcpu_exception_cb(cs, last_pc);
> return;
> }
> }
Likewise.
r~
next prev parent reply other threads:[~2025-05-24 17:21 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 [this message]
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
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=be2f91dc-c156-4f1b-95b0-2e7be3a860d4@linaro.org \
--to=richard.henderson@linaro.org \
--cc=qemu-devel@nongnu.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).