From: Laurent Vivier <laurent@vivier.eu>
To: qemu-devel@nongnu.org
Cc: Thomas Huth <huth@tuxfamily.org>, Laurent Vivier <laurent@vivier.eu>
Subject: [Qemu-devel] [PATCH v5 00/17] target/m68k: supervisor mode (part 1)
Date: Tue, 2 Jan 2018 02:10:15 +0100 [thread overview]
Message-ID: <20180102011032.30056-1-laurent@vivier.eu> (raw)
This series is the first series that will allow
to introduce supervisor mode and execute
privileged instructions.
Some of these patches are only cleanup:
sync CC_OP before gen_jmp_tb()
fix gen_get_ccr()
softmmu cleanup
add CPU_LOG_INT trace
use insn_pc to generate instruction fault address
move CCR/SR functions
fix m68k_cpu_dump_state()
We also fix a problem with linux-user mode,
where the State Register is not updated with
the CCR value (found while testing "chk/chk2"
using signal()):
correctly manage SR in context
We introduce some new non privileged instructions:
add chk and chk2
add move16
move16 is used by the kernel when it is compiled only for
68040 (it's a 68040 only instruction).
We add some trivial privileged instructions (most are empty):
add cpush/cinv
add reset
implement fsave/frestore
And finally, we add the privileged instructions to
modify the state register, the Interrupt Stack
Pointer and the 680x0 stack frame formats:
add 680x0 "move to SR" instruction
add andi/ori/eori to SR/CCR
add the Interrupt Stack Pointer
manage 680x0 stack frames
The next series will introduce the MC68040 MMU.
Laurent Vivier (17):
target-m68k: sync CC_OP before gen_jmp_tb()
target/m68k: fix gen_get_ccr()
linux-user,m68k: correctly manage SR in context
target-m68k: use insn_pc to generate instruction fault address
target/m68k: add CPU_LOG_INT trace
target/m68k: manage 680x0 stack frames
target/m68k: add chk and chk2
target/m68k: add move16
target/m68k: softmmu cleanup
target/m68k: add cpush/cinv
target/m68k: add reset
target/m68k: implement fsave/frestore
target/m68k: move CCR/SR functions
target/m68k: add 680x0 "move to SR" instruction
target/m68k: add andi/ori/eori to SR/CCR
target/m68k: add the Interrupt Stack Pointer
target/m68k: fix m68k_cpu_dump_state()
linux-user/main.c | 7 +
linux-user/signal.c | 7 +-
target/m68k/cpu.c | 15 +-
target/m68k/cpu.h | 83 ++++++-
target/m68k/gdbstub.c | 1 +
target/m68k/helper.c | 89 +++++++-
target/m68k/helper.h | 8 +-
target/m68k/monitor.c | 1 +
target/m68k/op_helper.c | 270 ++++++++++++++++++++++-
target/m68k/translate.c | 558 +++++++++++++++++++++++++++++++++++++++---------
10 files changed, 921 insertions(+), 118 deletions(-)
--
2.14.3
next reply other threads:[~2018-01-02 1:10 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 1:10 Laurent Vivier [this message]
2018-01-02 1:10 ` [Qemu-devel] [PATCH v5 01/17] target-m68k: sync CC_OP before gen_jmp_tb() Laurent Vivier
2018-01-02 16:01 ` Richard Henderson
2018-01-02 1:10 ` [Qemu-devel] [PATCH v5 02/17] target/m68k: fix gen_get_ccr() Laurent Vivier
2018-01-02 16:04 ` Richard Henderson
2018-01-02 1:10 ` [Qemu-devel] [PATCH v5 03/17] linux-user, m68k: correctly manage SR in context Laurent Vivier
2018-01-02 16:06 ` Richard Henderson
2018-01-02 1:10 ` [Qemu-devel] [PATCH v5 04/17] target-m68k: use insn_pc to generate instruction fault address Laurent Vivier
2018-01-02 16:08 ` Richard Henderson
2018-01-02 1:10 ` [Qemu-devel] [PATCH v5 05/17] target/m68k: add CPU_LOG_INT trace Laurent Vivier
2018-01-02 16:10 ` Richard Henderson
2018-01-02 18:37 ` Laurent Vivier
2018-01-02 1:10 ` [Qemu-devel] [PATCH v5 06/17] target/m68k: manage 680x0 stack frames Laurent Vivier
2018-01-02 16:16 ` Richard Henderson
2018-01-02 1:10 ` [Qemu-devel] [PATCH v5 07/17] target/m68k: add chk and chk2 Laurent Vivier
2018-01-02 16:41 ` Richard Henderson
2018-01-02 23:33 ` Laurent Vivier
2018-01-02 1:10 ` [Qemu-devel] [PATCH v5 08/17] target/m68k: add move16 Laurent Vivier
2018-01-02 16:50 ` Richard Henderson
2018-01-02 18:42 ` Laurent Vivier
2018-01-02 23:49 ` Richard Henderson
2018-01-02 23:53 ` Laurent Vivier
2018-01-02 1:10 ` [Qemu-devel] [PATCH v5 09/17] target/m68k: softmmu cleanup Laurent Vivier
2018-01-02 16:52 ` Richard Henderson
2018-01-02 1:10 ` [Qemu-devel] [PATCH v5 10/17] target/m68k: add cpush/cinv Laurent Vivier
2018-01-02 16:53 ` Richard Henderson
2018-01-02 1:10 ` [Qemu-devel] [PATCH v5 11/17] target/m68k: add reset Laurent Vivier
2018-01-02 16:54 ` Richard Henderson
2018-01-02 1:10 ` [Qemu-devel] [PATCH v5 12/17] target/m68k: implement fsave/frestore Laurent Vivier
2018-01-02 16:58 ` Richard Henderson
2018-01-02 1:10 ` [Qemu-devel] [PATCH v5 13/17] target/m68k: move CCR/SR functions Laurent Vivier
2018-01-02 17:00 ` Richard Henderson
2018-01-02 1:10 ` [Qemu-devel] [PATCH v5 14/17] target/m68k: add 680x0 "move to SR" instruction Laurent Vivier
2018-01-02 17:02 ` Richard Henderson
2018-01-02 1:10 ` [Qemu-devel] [PATCH v5 15/17] target/m68k: add andi/ori/eori to SR/CCR Laurent Vivier
2018-01-02 17:06 ` Richard Henderson
2018-01-02 1:10 ` [Qemu-devel] [PATCH v5 16/17] target/m68k: add the Interrupt Stack Pointer Laurent Vivier
2018-01-02 17:13 ` Richard Henderson
2018-01-02 18:50 ` Laurent Vivier
2018-01-02 1:10 ` [Qemu-devel] [PATCH v5 17/17] target/m68k: fix m68k_cpu_dump_state() Laurent Vivier
2018-01-02 17:14 ` Richard Henderson
2018-01-02 1:31 ` [Qemu-devel] [PATCH v5 00/17] target/m68k: supervisor mode (part 1) no-reply
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=20180102011032.30056-1-laurent@vivier.eu \
--to=laurent@vivier.eu \
--cc=huth@tuxfamily.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).