From: Peter Crosthwaite <crosthwaitepeter@gmail.com>
To: qemu-devel@nongnu.org
Cc: armbru@redhat.com,
Peter Crosthwaite <crosthwaite.peter@gmail.com>,
lcapitulino@redhat.com, afaerber@suse.de, rth@twiddle.net
Subject: [Qemu-devel] [PATCH v2 0/2] monitor+disas: Remove uses of ENV_GET_CPU
Date: Sun, 24 May 2015 14:20:39 -0700 [thread overview]
Message-ID: <cover.1432501932.git.crosthwaite.peter@gmail.com> (raw)
Neither the monitor or disassembly core has a good reason to navigate from an
env pointer to a cpu pointer. Disas should not need env awarness at all, that
is removed in P2.
The monitor is trickier, the env is still needed by some #ifdef switched target
specific code but all common code only needs to trade in CPU pointers. As the
monitor always has access to a CPU pointer naturally, remove ENV_GET_CPU usages
(P1).
This is related to my multi-arch work, where the goal is to minimise use of
architecture defined global definitions, ENV_GET_CPU being a major headache in
that whole effort. The longer term goal is to limit ENV_GET_CPU use to genuinely
architecture specific code.
But I think these two patches stand in their own right, so sending ahead of the
motherload series. This brings both modules closer to common-oby-y'ification.
First RFC for multi arch is avaiable here:
https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg01771.html
The two patches are done together to avoid a conflict with monitor_disas which
is touched by both patches. If one patch gets acked, the other nacked then
either can be merged independently with trivial edits.
Changed since v1:
Addressed RH and Andreas comments on P1.
Peter Crosthwaite (2):
monitor: Split mon_get_cpu fn to remove ENV_GET_CPU
disas: Remove uses of CPU env
disas.c | 14 +++++-----
include/disas/disas.h | 4 +--
include/qemu/log.h | 4 +--
monitor.c | 65 +++++++++++++++++++------------------------
target-alpha/translate.c | 2 +-
target-arm/translate-a64.c | 2 +-
target-arm/translate.c | 2 +-
target-cris/translate.c | 2 +-
target-i386/translate.c | 2 +-
target-lm32/translate.c | 2 +-
target-m68k/translate.c | 2 +-
target-microblaze/translate.c | 2 +-
target-mips/translate.c | 2 +-
target-openrisc/translate.c | 2 +-
target-ppc/translate.c | 2 +-
target-s390x/translate.c | 2 +-
target-sh4/translate.c | 2 +-
target-sparc/translate.c | 2 +-
target-tricore/translate.c | 2 +-
target-unicore32/translate.c | 2 +-
target-xtensa/translate.c | 2 +-
21 files changed, 57 insertions(+), 64 deletions(-)
--
1.9.1
next reply other threads:[~2015-05-24 21:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 21:20 Peter Crosthwaite [this message]
2015-05-24 21:20 ` [Qemu-devel] [PATCH v2 1/2] monitor: Split mon_get_cpu fn to remove ENV_GET_CPU Peter Crosthwaite
2015-06-12 6:07 ` Markus Armbruster
2015-06-12 6:14 ` Markus Armbruster
2015-06-16 15:09 ` Markus Armbruster
2015-06-17 5:39 ` Peter Crosthwaite
2015-06-17 6:42 ` Markus Armbruster
2015-06-17 7:19 ` Peter Crosthwaite
2015-05-24 21:20 ` [Qemu-devel] [PATCH v2 2/2] disas: Remove uses of CPU env Peter Crosthwaite
2015-06-02 8:06 ` [Qemu-devel] [PATCH v2 0/2] monitor+disas: Remove uses of ENV_GET_CPU Peter Crosthwaite
2015-06-02 15:55 ` Luiz Capitulino
2015-06-11 17:54 ` Luiz Capitulino
2015-06-17 6:32 ` Markus Armbruster
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.1432501932.git.crosthwaite.peter@gmail.com \
--to=crosthwaitepeter@gmail.com \
--cc=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=crosthwaite.peter@gmail.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).