From: Laurent Vivier <laurent@vivier.eu>
To: BALATON Zoltan <balaton@eik.bme.hu>,
qemu-devel@nongnu.org,
Lucien Murray-Pitts <lucienmp.qemu@gmail.com>
Subject: Re: [PATCH] target/m68k: Allow movec only on 68010+
Date: Tue, 14 Jan 2020 21:50:19 +0100 [thread overview]
Message-ID: <202ca4b5-cb25-a654-fbfd-a958feebcf66@vivier.eu> (raw)
In-Reply-To: <20200114202226.E859E745702@zero.eik.bme.hu>
Le 14/01/2020 à 21:13, BALATON Zoltan a écrit :
> The movec opcode does not exist on 68000 and should raise an
> exception. Fix the feature mask to only allow movec on newer 68k CPUs.
>
> Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
> ---
> target/m68k/translate.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/target/m68k/translate.c b/target/m68k/translate.c
> index fcdb7bc8e4..f19da064c8 100644
> --- a/target/m68k/translate.c
> +++ b/target/m68k/translate.c
> @@ -5988,7 +5988,7 @@ void register_m68k_insns (CPUM68KState *env)
> BASE(stop, 4e72, ffff);
> BASE(rte, 4e73, ffff);
> INSN(cf_movec, 4e7b, ffff, CF_ISA_A);
> - INSN(m68k_movec, 4e7a, fffe, M68000);
> + INSN(m68k_movec, 4e7a, fffe, FPU);
> #endif
> BASE(nop, 4e71, ffff);
> INSN(rtd, 4e74, ffff, RTD);
>
Good point. But as movec is not related to FPU I don't think this is the
good flag to use.
Lucien has sent a patch to fix this issue last year:
[5/6] MOVEC insn. doesnt generate exception if wrong CR is accessed
https://patchwork.kernel.org/patch/10997467/
it needs a rework (M680x0 feature flags are now specific to each CPU, so
the table cannot be set to the older one, 68010, and 68060 is missing)
but I think it's a better approach.
Thanks,
Laurent
next prev parent reply other threads:[~2020-01-14 20:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 20:13 [PATCH] target/m68k: Allow movec only on 68010+ BALATON Zoltan
2020-01-14 20:50 ` Laurent Vivier [this message]
2020-05-01 13:11 ` BALATON Zoltan
2020-05-01 14:02 ` Laurent Vivier
2020-05-02 1:38 ` BALATON Zoltan
2020-05-02 14:55 ` Laurent Vivier
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=202ca4b5-cb25-a654-fbfd-a958feebcf66@vivier.eu \
--to=laurent@vivier.eu \
--cc=balaton@eik.bme.hu \
--cc=lucienmp.qemu@gmail.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).