All of lore.kernel.org
 help / color / mirror / Atom feed
From: BALATON Zoltan <balaton@eik.bme.hu>
To: qemu-devel@nongnu.org
Cc: Laurent Vivier <laurent@vivier.eu>,
	Lucien Murray-Pitts <lucienmp.qemu@gmail.com>
Subject: [PATCH 0/6] m68k: Overhaul of MOVEC instruction to support exception/MSP
Date: Mon, 01 Feb 2021 01:01:52 +0100	[thread overview]
Message-ID: <cover.1612137712.git.balaton@eik.bme.hu> (raw)

Hello,

This is Lucien's m68k series rebased on and fixed up to work with
current master as per previous discussion:
https://lists.gnu.org/archive/html/qemu-devel/2020-01/msg02840.html

I've left previous Reviewed-by tags for reference but these should
probably be reviewed again. I've only lightly tested it so I don't
know if everything is correct but it does seem to fix the problem my
original patch tried to fix at least. More testing, review and help to
finish this so it can be merged at last is welcome.

Regards,
BALATON Zoltan

Lucien Murray-Pitts (6):
  m68k: improve cpu instantiation comments
  m68k: cascade m68k_features by m680xx_cpu_initfn() to improve
    readability
  m68k: improve comments on m68k_move_to/from helpers
  m68k: add missing BUSCR/PCR CR defines, and BUSCR/PCR/CAAR CR to
    m68k_move_to/from
  m68k: MOVEC insn. should generate exception if wrong CR is accessed
  m68k: add MSP detection support for stack pointer swap helpers

 target/m68k/cpu.c       | 116 ++++++++++++++------
 target/m68k/cpu.h       |  64 +++++++----
 target/m68k/helper.c    | 234 +++++++++++++++++++++++++++++++---------
 target/m68k/translate.c |   2 +-
 4 files changed, 309 insertions(+), 107 deletions(-)

-- 
2.21.3



             reply	other threads:[~2021-02-01  0:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01  0:01 BALATON Zoltan [this message]
2021-02-01  0:01 ` [PATCH 1/6] m68k: improve cpu instantiation comments BALATON Zoltan
2021-02-01  0:01 ` [PATCH 6/6] m68k: add MSP detection support for stack pointer swap helpers BALATON Zoltan
2021-02-01  0:01 ` [PATCH 4/6] m68k: add missing BUSCR/PCR CR defines, and BUSCR/PCR/CAAR CR to m68k_move_to/from BALATON Zoltan
2021-02-01  7:34   ` Philippe Mathieu-Daudé
2021-02-01  0:01 ` [PATCH 2/6] m68k: cascade m68k_features by m680xx_cpu_initfn() to improve readability BALATON Zoltan
2021-02-01  0:01 ` [PATCH 3/6] m68k: improve comments on m68k_move_to/from helpers BALATON Zoltan
2021-02-01  0:01 ` [PATCH 5/6] m68k: MOVEC insn. should generate exception if wrong CR is accessed BALATON Zoltan
2021-02-09 16:53 ` [PATCH 0/6] m68k: Overhaul of MOVEC instruction to support exception/MSP BALATON Zoltan
2021-02-11 20:16 ` 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=cover.1612137712.git.balaton@eik.bme.hu \
    --to=balaton@eik.bme.hu \
    --cc=laurent@vivier.eu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.