From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Cc: patches@linaro.org
Subject: [Qemu-devel] [PATCH v2 0/2] clean up cpu_dump_state flags
Date: Thu, 6 Sep 2012 11:41:39 +0100 [thread overview]
Message-ID: <1346928101-12958-1-git-send-email-peter.maydell@linaro.org> (raw)
This is a small cleanup patchset which moves some cpu_dump_state
flags from being x86 only to being generic, since the extra info
they ask for is not particularly x86 specific (many of our
target architectures have an fpu, and similarly several implement
the TCG condition-code optimisation). This allows us to remove
some ugly TARGET_I386 ifdefs from target-independent code.
I've also implemented the DUMP_FPU flag for ARM, by reinstating
(somewhat modified) some code which had been #if'd out for years.
There should be no behaviour change for other architectures.
Changes v1->v2: none, just rebased on master
(since the v1 patch only applied with fuzzing)
Peter Maydell (2):
cpu_dump_state: move DUMP_FPU and DUMP_CCOP flags from x86-only to
generic
target-arm: Reinstate display of VFP registers in cpu_dump_state
cpu-all.h | 3 +++
cpu-exec.c | 2 +-
cpus.c | 6 +-----
exec.c | 12 ++----------
monitor.c | 8 +-------
target-arm/translate.c | 42 ++++++++++++++++--------------------------
target-i386/cpu.c | 2 +-
target-i386/cpu.h | 4 ----
target-i386/helper.c | 4 ++--
target-i386/seg_helper.c | 4 ++--
target-i386/smm_helper.c | 4 ++--
11 files changed, 31 insertions(+), 60 deletions(-)
--
1.7.9.5
next reply other threads:[~2012-09-06 11:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 10:41 Peter Maydell [this message]
2012-09-06 10:41 ` [Qemu-devel] [PATCH v2 1/2] cpu_dump_state: move DUMP_FPU and DUMP_CCOP flags from x86-only to generic Peter Maydell
2012-09-06 10:41 ` [Qemu-devel] [PATCH v2 2/2] target-arm: Reinstate display of VFP registers in cpu_dump_state Peter Maydell
2012-09-25 13:08 ` [Qemu-devel] [PATCH v2 0/2] clean up cpu_dump_state flags 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=1346928101-12958-1-git-send-email-peter.maydell@linaro.org \
--to=peter.maydell@linaro.org \
--cc=patches@linaro.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).