1. Patchew
  2. QEMU
  3. View series

[PATCH] target/m68k: Fix exception frame format for 68010

Daniel Palmer posted 1 patch 10 months, 2 weeks ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/qemu tags/patchew/20240115101643.2165387-1-daniel@0x0f.com
Maintainers: Laurent Vivier <laurent@vivier.eu>
target/m68k/cpu.c       | 4 +++-
target/m68k/cpu.h       | 2 ++
target/m68k/op_helper.c | 4 ++--
3 files changed, 7 insertions(+), 3 deletions(-)
[PATCH] target/m68k: Fix exception frame format for 68010
Posted by Daniel Palmer 10 months, 2 weeks ago 
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) {
-- 
2.43.0
Re: [PATCH] target/m68k: Fix exception frame format for 68010
Posted by Laurent Vivier 9 months, 1 week ago 
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>
Re: [PATCH] target/m68k: Fix exception frame format for 68010
Posted by Thomas Huth 9 months, 1 week ago 
On 15/01/2024 11.16, Daniel Palmer wrote:
>  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) {

LGTM,
Reviewed-by: Thomas Huth <thuth@redhat.com>

Laurent, if you're currently too busy with other stuff, I could also add 
this to my next pull request?

  Thomas
Re: [PATCH] target/m68k: Fix exception frame format for 68010
Posted by Mark Cave-Ayland 9 months, 1 week ago 
On 22/02/2024 09:57, Thomas Huth wrote:
> On 15/01/2024 11.16, Daniel Palmer wrote:
>>  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) {
> 
> LGTM,
> Reviewed-by: Thomas Huth <thuth@redhat.com>

This is also:
Fixes: https://gitlab.com/qemu-project/qemu/-/issues/2164

> Laurent, if you're currently too busy with other stuff, I could also add this to my 
> next pull request?
> 
>   Thomas


ATB,

Mark.
Re: [PATCH] target/m68k: Fix exception frame format for 68010
Posted by Peter Maydell 9 months, 1 week ago 
On Thu, 22 Feb 2024 at 13:34, Mark Cave-Ayland
<mark.cave-ayland@ilande.co.uk> wrote:

> This is also:
> Fixes: https://gitlab.com/qemu-project/qemu/-/issues/2164

"Resolves:" for gitlab bug URLs; "Fixes:" is for git commits.

-- PMM
Re: [PATCH] target/m68k: Fix exception frame format for 68010
Posted by Mark Cave-Ayland 9 months, 1 week ago 
On 22/02/2024 13:37, Peter Maydell wrote:

> On Thu, 22 Feb 2024 at 13:34, Mark Cave-Ayland
> <mark.cave-ayland@ilande.co.uk> wrote:
> 
>> This is also:
>> Fixes: https://gitlab.com/qemu-project/qemu/-/issues/2164
> 
> "Resolves:" for gitlab bug URLs; "Fixes:" is for git commits.

I think GitLab will happily accept either form (see 
https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) 
which appears to be supported by the git history? But I can certainly make a note of 
this convention for the future.


ATB,

Mark.
Re: [PATCH] target/m68k: Fix exception frame format for 68010
Posted by Peter Maydell 9 months, 1 week ago 
On Thu, 22 Feb 2024 at 13:50, Mark Cave-Ayland
<mark.cave-ayland@ilande.co.uk> wrote:
>
> On 22/02/2024 13:37, Peter Maydell wrote:
>
> > On Thu, 22 Feb 2024 at 13:34, Mark Cave-Ayland
> > <mark.cave-ayland@ilande.co.uk> wrote:
> >
> >> This is also:
> >> Fixes: https://gitlab.com/qemu-project/qemu/-/issues/2164
> >
> > "Resolves:" for gitlab bug URLs; "Fixes:" is for git commits.
>
> I think GitLab will happily accept either form (see
> https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
> which appears to be supported by the git history? But I can certainly make a note of
> this convention for the future.

Yes, gitlab's regex for detecting this is quite wide; the
intention is to try to keep the semantic uses "note which
git commit this change is correcting" and "note the bug
which this change is resolving" distinct.

-- PMM

Patchew 2.1-devel-b67e4c2

© 2016 - 2024 Red Hat, Inc.