From: Peter Crosthwaite <crosthwaitepeter@gmail.com>
To: qemu-devel@nongnu.org
Cc: afaerber@suse.de, Peter Crosthwaite <crosthwaite.peter@gmail.com>
Subject: [Qemu-devel] [PATCH 0/8] Disas QOMification, round 2
Date: Sat, 11 Jul 2015 18:59:57 -0700 [thread overview]
Message-ID: <cover.1436665556.git.crosthwaite.peter@gmail.com> (raw)
Continue QOMifying target-specific disassembly. Convert all arches except for
X86 and PPC. They will be round 3 and are non-trivial.
This brings us close to no arch-specific code in disas.c allow conversion to
common-obj and preparing these arches for inclusion in multi-arch.
Tested to various degrees depending on image availability. Arches with bios's
are the easiest, others have sample test images available. Some that accept
binary blobs as code I half-tested with random data as code. Moxie has no
testing. Status:
s390: Tested with bios
moxie: No testing (requires an elf)
m68k: Tested with random code
sparc,sparc64: Tested with bios
lm32: Tested with random code
sh4: Tested with sample image
mips: Tested with sample image
alpha: Tested with bios
Peter Crosthwaite (8):
disas: s390x: QOMify target specific disas setup
disas: moxie: QOMify target specific disas setup
disas: m68k: QOMify target specific disas setup
disas: sparc: QOMify target specific disas setup
disas: lm32: QOMify target specific disas setup
disas: sh4: QOMify target specific disas setup
disas: mips: QOMify target specific disas setup
disas: alpha: QOMify target specific disas setup
disas.c | 55 ------------------------------------------------------
target-alpha/cpu.c | 8 ++++++++
target-lm32/cpu.c | 8 ++++++++
target-m68k/cpu.c | 7 +++++++
target-mips/cpu.c | 10 ++++++++++
target-moxie/cpu.c | 7 +++++++
target-s390x/cpu.c | 8 ++++++++
target-sh4/cpu.c | 8 ++++++++
target-sparc/cpu.c | 9 +++++++++
9 files changed, 65 insertions(+), 55 deletions(-)
--
1.9.1
next reply other threads:[~2015-07-12 2:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-12 1:59 Peter Crosthwaite [this message]
2015-07-12 1:59 ` [Qemu-devel] [PATCH 1/8] disas: s390x: QOMify target specific disas setup Peter Crosthwaite
2015-08-16 2:39 ` Peter Crosthwaite
2015-07-12 1:59 ` [Qemu-devel] [PATCH 2/8] disas: moxie: " Peter Crosthwaite
2015-07-12 2:00 ` [Qemu-devel] [PATCH 3/8] disas: m68k: " Peter Crosthwaite
2015-07-12 8:43 ` Laurent Vivier
2015-07-13 3:58 ` Greg Ungerer
2015-07-12 2:00 ` [Qemu-devel] [PATCH 4/8] disas: sparc: " Peter Crosthwaite
2015-07-12 2:00 ` [Qemu-devel] [PATCH 5/8] disas: lm32: " Peter Crosthwaite
2015-07-12 10:06 ` Michael Walle
2015-07-12 2:00 ` [Qemu-devel] [PATCH 6/8] disas: sh4: " Peter Crosthwaite
2015-07-14 15:47 ` Aurelien Jarno
2015-07-12 2:00 ` [Qemu-devel] [PATCH 7/8] disas: mips: " Peter Crosthwaite
2015-07-13 16:00 ` Leon Alrae
2015-07-12 2:00 ` [Qemu-devel] [PATCH 8/8] disas: alpha: " Peter Crosthwaite
2015-08-16 2:40 ` Peter Crosthwaite
2015-07-12 12:18 ` [Qemu-devel] [PATCH 0/8] Disas QOMification, round 2 Andreas Färber
2015-08-16 2:38 ` Peter Crosthwaite
2015-08-23 19:22 ` Peter Crosthwaite
2015-08-27 22:47 ` Andreas Färber
2015-08-28 4:20 ` Richard Henderson
2015-08-28 15:46 ` Andreas Färber
2015-08-28 16:02 ` Peter Maydell
2015-08-28 16:19 ` Peter Crosthwaite
2015-08-28 16:22 ` Peter Maydell
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.1436665556.git.crosthwaite.peter@gmail.com \
--to=crosthwaitepeter@gmail.com \
--cc=afaerber@suse.de \
--cc=crosthwaite.peter@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.