qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: Richard Henderson <rth@twiddle.net>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target-sparc register window handling
Date: Sat, 6 Oct 2012 12:15:16 +0200	[thread overview]
Message-ID: <20121006101516.GK4623@ohm.aurel32.net> (raw)
In-Reply-To: <1349481605-9561-1-git-send-email-rth@twiddle.net>

On Fri, Oct 05, 2012 at 05:00:04PM -0700, Richard Henderson wrote:
> This applies with or without the sparc-compare patch set I
> recently sent, and it works with the same set of tests.
> 
> I've not had time to do true benchmarking on this, but it
> does reduce the size of the generated code:

Experience proves that there is not a direct relation between size of
the generated code and the resulting emulation speed, sometimes smaller
code means slower emulation (when the code generation/optimization takes
too much time), and sometimes bigger code might means faster emulation
(think about replacing some helpers by TCG code).

As from the user point of view what is important is the emulation speed,
I think benchmarks (even simple ones like measuring the boot time of a
guest) are essential for this kind of patch.

> BEFORE
> Translation buffer state:
> gen code size       509344/33431552
> TB count            2196/262144
> TB avg target size  22 max=252 bytes
> TB avg host size    231 bytes (expansion ratio: 10.3)
> cross page TB count 0 (0%)
> direct jump count   1153 (52%) (2 jumps=628 28%)
> 
> AFTER
> Translation buffer state:
> gen code size       418064/33431552
> TB count            2196/262144
> TB avg target size  22 max=252 bytes
> TB avg host size    190 bytes (expansion ratio: 8.4)
> cross page TB count 0 (0%)
> direct jump count   1153 (52%) (2 jumps=628 28%)
> 
> 
> r~
> 
> 
> Richard Henderson (1):
>   target-sparc: Use TCG registers for windowed registers
> 
>  gdbstub.c                          |   4 +-
>  linux-user/main.c                  |  17 ++--
>  linux-user/signal.c                |  78 +++++++--------
>  linux-user/sparc/target_signal.h   |   2 +-
>  linux-user/sparc64/target_signal.h |   2 +-
>  monitor.c                          |   2 +-
>  target-sparc/cpu.c                 |   3 +-
>  target-sparc/cpu.h                 |  20 ++--
>  target-sparc/int32_helper.c        |   4 +-
>  target-sparc/ldst_helper.c         |  12 +--
>  target-sparc/translate.c           | 188 +++++++++++++++++--------------------
>  target-sparc/win_helper.c          |  56 ++++++-----
>  12 files changed, 190 insertions(+), 198 deletions(-)
> 
> -- 
> 1.7.11.4
> 
> 
> 

-- 
Aurelien Jarno                          GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net

  parent reply	other threads:[~2012-10-06 10:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-06  0:00 [Qemu-devel] [PATCH] target-sparc register window handling Richard Henderson
2012-10-06  0:00 ` [Qemu-devel] [PATCH] target-sparc: Use TCG registers for windowed registers Richard Henderson
2012-10-06 10:15 ` Aurelien Jarno [this message]
2012-10-08  6:17   ` [Qemu-devel] [PATCH] target-sparc register window handling Aurelien Jarno
2012-10-09 16:53     ` Richard Henderson
2012-10-09 17:06       ` Aurelien Jarno

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=20121006101516.GK4623@ohm.aurel32.net \
    --to=aurelien@aurel32.net \
    --cc=blauwirbel@gmail.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).