All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Rydberg <jrydberg@night.trouble.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] performance of qemu
Date: Tue, 3 Jun 2003 20:12:15 +0200	[thread overview]
Message-ID: <20030603201215.0ca4063b.jrydberg@night.trouble.net> (raw)


Hi,

has anyone of you guys (Fabrice et al) done any performance measurements of
QEMU?  I'm particular intrested in the performance of functions that
set the condition codes.  

If I'm not mistaken, the condition codes is simulated using two values and
an operator specifying what type of insn that generated the condition codes.

When is the full eflags register generated?  In the epilogue of a translated
block, or when ever an insn/callback reads the eflag register?

Is any optmization done in the case that two insns that kill the condition 
codes? (example: two insns that kills the condition codes, but no insn between 
them that uses it).

brgds,
Johan.

             reply	other threads:[~2003-06-03 18:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03 18:12 Johan Rydberg [this message]
2003-06-04  8:20 ` [Qemu-devel] performance of qemu Fabrice Bellard
2003-06-04 14:16   ` Johan Rydberg
2003-06-04 16:01     ` Fabrice Bellard
2003-06-04 16:08       ` Johan Rydberg

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=20030603201215.0ca4063b.jrydberg@night.trouble.net \
    --to=jrydberg@night.trouble.net \
    --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.