From: Laurent Vivier <laurent@vivier.eu>
To: Daniel Palmer <daniel@0x0f.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] target/m68k: Fix exception frame format for 68010
Date: Fri, 23 Feb 2024 13:03:43 +0100 [thread overview]
Message-ID: <6ee33d49-4add-4354-964e-788ba6c9a13d@vivier.eu> (raw)
In-Reply-To: <20240115101643.2165387-1-daniel@0x0f.com>
Le 15/01/2024 à 11:16, Daniel Palmer a écrit :
> From the 68010 a word with the frame format and exception vector
> are placed on the stack before the PC and SR.
>
> M68K_FEATURE_QUAD_MULDIV is currently checked to workout if to do
> this or not for the configured CPU but that flag isn't set for
> 68010 so currently the exception stack when 68010 is configured
> is incorrect.
>
> It seems like checking M68K_FEATURE_MOVEFROMSR_PRIV would do but
> adding a new flag that shows exactly what is going on here is
> maybe clearer.
>
> Add a new flag for the behaviour, M68K_FEATURE_EXCEPTION_FORMAT_VEC,
> and set it for 68010 and above, and then use it to control if the
> format and vector word are pushed/pop during exception entry/exit.
>
> Signed-off-by: Daniel Palmer <daniel@0x0f.com>
> ---
> target/m68k/cpu.c | 4 +++-
> target/m68k/cpu.h | 2 ++
> target/m68k/op_helper.c | 4 ++--
> 3 files changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/target/m68k/cpu.c b/target/m68k/cpu.c
> index 1421e77c2c07..20718944b4c8 100644
> --- a/target/m68k/cpu.c
> +++ b/target/m68k/cpu.c
> @@ -137,7 +137,8 @@ static void m68000_cpu_initfn(Object *obj)
> }
>
> /*
> - * Adds BKPT, MOVE-from-SR *now priv instr, and MOVEC, MOVES, RTD
> + * Adds BKPT, MOVE-from-SR *now priv instr, and MOVEC, MOVES, RTD,
> + * format+vector in exception frame.
> */
> static void m68010_cpu_initfn(Object *obj)
> {
> @@ -150,6 +151,7 @@ static void m68010_cpu_initfn(Object *obj)
> m68k_set_feature(env, M68K_FEATURE_BKPT);
> m68k_set_feature(env, M68K_FEATURE_MOVEC);
> m68k_set_feature(env, M68K_FEATURE_MOVEFROMSR_PRIV);
> + m68k_set_feature(env, M68K_FEATURE_EXCEPTION_FORMAT_VEC);
> }
>
> /*
> diff --git a/target/m68k/cpu.h b/target/m68k/cpu.h
> index d13427b0fe61..0fc591e618f6 100644
> --- a/target/m68k/cpu.h
> +++ b/target/m68k/cpu.h
> @@ -549,6 +549,8 @@ enum m68k_features {
> M68K_FEATURE_TRAPCC,
> /* MOVE from SR privileged (from 68010) */
> M68K_FEATURE_MOVEFROMSR_PRIV,
> + /* Exception frame with format+vector (from 68010) */
> + M68K_FEATURE_EXCEPTION_FORMAT_VEC,
> };
>
> static inline bool m68k_feature(CPUM68KState *env, int feature)
> diff --git a/target/m68k/op_helper.c b/target/m68k/op_helper.c
> index 1ce850bbc594..b09771672dec 100644
> --- a/target/m68k/op_helper.c
> +++ b/target/m68k/op_helper.c
> @@ -52,7 +52,7 @@ throwaway:
> sp += 2;
> env->pc = cpu_ldl_mmuidx_ra(env, sp, MMU_KERNEL_IDX, 0);
> sp += 4;
> - if (m68k_feature(env, M68K_FEATURE_QUAD_MULDIV)) {
> + if (m68k_feature(env, M68K_FEATURE_EXCEPTION_FORMAT_VEC)) {
> /* all except 68000 */
> fmt = cpu_lduw_mmuidx_ra(env, sp, MMU_KERNEL_IDX, 0);
> sp += 2;
> @@ -256,7 +256,7 @@ static inline void do_stack_frame(CPUM68KState *env, uint32_t *sp,
> uint16_t format, uint16_t sr,
> uint32_t addr, uint32_t retaddr)
> {
> - if (m68k_feature(env, M68K_FEATURE_QUAD_MULDIV)) {
> + if (m68k_feature(env, M68K_FEATURE_EXCEPTION_FORMAT_VEC)) {
> /* all except 68000 */
> CPUState *cs = env_cpu(env);
> switch (format) {
Reviewed-by: Laurent Vivier <laurent@vivier.eu>
prev parent reply other threads:[~2024-02-23 12:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 10:16 [PATCH] target/m68k: Fix exception frame format for 68010 Daniel Palmer
2024-02-22 9:57 ` Thomas Huth
2024-02-22 13:33 ` Mark Cave-Ayland
2024-02-22 13:37 ` Peter Maydell
2024-02-22 13:50 ` Mark Cave-Ayland
2024-02-22 14:48 ` Peter Maydell
2024-02-23 12:03 ` Laurent Vivier [this message]
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=6ee33d49-4add-4354-964e-788ba6c9a13d@vivier.eu \
--to=laurent@vivier.eu \
--cc=daniel@0x0f.com \
--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).