From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 05/10] qemu-tech: document lazy condition code evaluation in cpu.h
Date: Fri, 7 Oct 2016 10:02:28 +0200 [thread overview]
Message-ID: <5b6d2360-d3a3-38fc-98f7-b13bc9bcd44b@redhat.com> (raw)
In-Reply-To: <CAFEAcA9P2uTERzN0sHqG9Mn=0_vNURZ6_PgsqXk1UzGRG2g+Pg@mail.gmail.com>
On 06/10/2016 20:45, Peter Maydell wrote:
> On 6 October 2016 at 16:24, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> Unlike the other sections, they are pretty specific to a particular CPU.
>>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> ---
>> qemu-tech.texi | 25 -------------------------
>> target-cris/cpu.h | 7 +++++++
>> target-i386/cpu.h | 7 +++++++
>> target-m68k/cpu.h | 8 ++++++++
>> target-sparc/cpu.h | 5 +++++
>> 5 files changed, 27 insertions(+), 25 deletions(-)
>
> target-s390x/ also seems to have the CC optimization...
Indeed:
diff --git a/target-s390x/cpu.h b/target-s390x/cpu.h
index 4fb34b5..4e58cde 100644
--- a/target-s390x/cpu.h
+++ b/target-s390x/cpu.h
@@ -671,6 +671,13 @@ ObjectClass *s390_cpu_class_by_name(const char *name);
/* CC optimization */
+/* Instead of computing the condition codes after each x86 instruction,
+ * QEMU just stores the result (called CC_DST), the type of operation
+ * (called CC_OP) and whatever operands are needed (CC_SRC and possibly
+ * CC_VR). When the condition codes are needed, the condition codes can
+ * be calculated using this information. Condition codes are not generated
+ * if they are only needed for conditional branches.
+ */
enum cc_op {
CC_OP_CONST0 = 0, /* CC is 0 */
CC_OP_CONST1, /* CC is 1 */
Paolo
next prev parent reply other threads:[~2016-10-07 8:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 15:24 [Qemu-devel] [PATCH 00/10] qemu-tech cleanup Paolo Bonzini
2016-10-06 15:24 ` [Qemu-devel] [PATCH 01/10] qemu-tech: drop index Paolo Bonzini
2016-10-06 15:24 ` [Qemu-devel] [PATCH 02/10] qemu-doc: replace introduction with the one from the internals manual Paolo Bonzini
2016-10-06 15:24 ` [Qemu-devel] [PATCH 03/10] qemu-doc: drop installation and compilation notes Paolo Bonzini
2016-10-06 15:24 ` [Qemu-devel] [PATCH 04/10] qemu-tech: move text from qemu-tech to tcg/README Paolo Bonzini
2016-10-06 15:24 ` [Qemu-devel] [PATCH 05/10] qemu-tech: document lazy condition code evaluation in cpu.h Paolo Bonzini
2016-10-06 16:18 ` Emilio G. Cota
2016-10-06 16:21 ` Paolo Bonzini
2016-10-06 18:45 ` Peter Maydell
2016-10-07 8:02 ` Paolo Bonzini [this message]
2016-10-06 15:24 ` [Qemu-devel] [PATCH 06/10] qemu-tech: move user mode emulation features from qemu-tech Paolo Bonzini
2016-10-06 18:32 ` Jonathan Neuschäfer
2016-10-07 7:55 ` Paolo Bonzini
2016-10-06 15:24 ` [Qemu-devel] [PATCH 07/10] qemu-tech: move TCG test documentation to tests/tcg/README Paolo Bonzini
2016-10-06 15:24 ` [Qemu-devel] [PATCH 08/10] qemu-tech: reorganize content Paolo Bonzini
2016-10-06 15:24 ` [Qemu-devel] [PATCH 09/10] qemu-tech: rewrite some parts Paolo Bonzini
2016-10-06 16:31 ` Emilio G. Cota
2016-10-07 7:55 ` Paolo Bonzini
2016-10-06 15:24 ` [Qemu-devel] [PATCH 10/10] qemu-doc: merge qemu-tech and qemu-doc Paolo Bonzini
2016-10-06 16:36 ` [Qemu-devel] [PATCH 00/10] qemu-tech cleanup Emilio G. Cota
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=5b6d2360-d3a3-38fc-98f7-b13bc9bcd44b@redhat.com \
--to=pbonzini@redhat.com \
--cc=peter.maydell@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 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.