All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dennis Luehring <dl.soluz@gmx.net>
To: Richard Henderson <rth@twiddle.net>,
	Artyom Tarasenko <atar4qemu@gmail.com>,
	Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Debian 7.8.0 SPARC64 on qemu - anything i can do to speedup the emulation?
Date: Fri, 21 Aug 2015 06:32:31 +0200	[thread overview]
Message-ID: <55D6A9DF.5070506@gmx.net> (raw)
In-Reply-To: <55D60C1B.9010502@twiddle.net>

Am 20.08.2015 um 19:19 schrieb Richard Henderson:
> This isn't surprising, because at the moment tcg optimizations are almost
> completely ineffective for sparc.  The way the register windows are implemented
> means that there are very few proper tcg temporaries to optimize.
>
> I've just updated an old branch that attempts to cure this.  It creates proper
> tcg temporaries for the windowed registers, and uses a bit of recursion to find
> the place at which they should be stored.
>
>     git://github.com/rth7680/qemu.git  tcg-indirect
>
> With a few quick unscientific tests, it appears to help.  It would be nice to
> put that branch side-by-side with your tests above.

tcg-indirect seems not to improve (stream test degrades even more)

without-optimization means qemu.org-git + undefine USE_TCG_OPTIMIZATIONS

git clone git://github.com/rth7680/qemu.git
cd qemu
git checkout tcg-indirect

g++ src/pugixml.cpp -g -Wall -Wextra -Werror -pedantic -std=c++0x -c 
-MMD -MP

tcg-indirect: ~2:46.5
qemu.org-git: ~2:51.2 (worst result)
without-optimization: ~2:14.1 (best result)

gcc prime.c -o prime.out -lm

prime.out runtime

tcg-indirect: ~9.3 sec (best result)
qemu.org-git: ~11 sec
without-optimization: ~9.9 sec (worst result)

stream results (STREAM version $Revision: 5.10 $)

tcg-indirect: (worst result)

Your clock granularity/precision appears to be 41 microseconds.
Each test below will take on the order of 632527 microseconds.
    (= 15427 clock ticks)
Function    Best Rate MB/s  Avg time     Min time     Max time
Copy:             320.8     0.511297     0.498785     0.590214
Scale:            187.0     0.858693     0.855465     0.863527
Add:              218.2     1.104654     1.099698     1.110341
Triad:            169.5     1.433273     1.416321     1.502248

qemu.org-git: (best result)

Your clock granularity/precision appears to be 42 microseconds.
Each test below will take on the order of 330428 microseconds.
     (= 7867 clock ticks)
Function    Best Rate MB/s  Avg time     Min time     Max time
Copy:             771.5     0.214717     0.207377     0.244214
Scale:            288.1     0.573320     0.555401     0.660161
Add:              423.5     0.633523     0.566661     1.092067
Triad:            242.9     1.053032     0.987970     1.499563

without-optimization:

Your clock granularity/precision appears to be 41 microseconds.
Each test below will take on the order of 745254 microseconds.
    (= 18176 clock ticks)
Function    Best Rate MB/s  Avg time     Min time     Max time
Copy:             316.6     0.524065     0.505313     0.580103
Scale:            200.5     0.813356     0.798024     0.840986
Add:              243.9     1.010247     0.984025     1.119149
Triad:            182.9     1.345601     1.312236     1.427459

  reply	other threads:[~2015-08-21  4:33 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28  7:52 [Qemu-devel] Debian 7.8.0 SPARC64 on qemu - anything i can do to speedup the emulation? Dennis Luehring
2015-07-28  9:54 ` Artyom Tarasenko
2015-07-29  6:20   ` Dennis Luehring
2015-07-29  8:23     ` Artyom Tarasenko
2015-07-29 15:01     ` Aurelien Jarno
2015-07-30  3:52       ` Dennis Luehring
2015-07-30  7:52         ` Aurelien Jarno
2015-07-30  8:16           ` Dennis Luehring
2015-07-30  8:42             ` Artyom Tarasenko
2015-07-30  8:55             ` Aurelien Jarno
2015-07-30  9:35               ` Artyom Tarasenko
2015-07-30 10:09                 ` Aurelien Jarno
2015-07-30 18:21                   ` Dennis Luehring
2015-07-30 15:50               ` Aurelien Jarno
2015-07-31 15:31                 ` Artyom Tarasenko
2015-07-31 15:43                   ` Aurelien Jarno
2015-08-02 13:11                     ` Mark Cave-Ayland
2015-08-03  8:31                     ` Artyom Tarasenko
2015-08-03  9:17                       ` Aurelien Jarno
2015-08-18  9:24                         ` Artyom Tarasenko
2015-08-18 17:55                           ` Richard Henderson
2015-08-19 10:41                             ` Artyom Tarasenko
2015-08-19 11:00                               ` Aurelien Jarno
2015-08-19 14:41                                 ` Artyom Tarasenko
2015-08-20  5:22                                   ` Dennis Luehring
2015-08-20 10:40                                     ` Artyom Tarasenko
2015-08-20 17:19                                   ` Richard Henderson
2015-08-21  4:32                                     ` Dennis Luehring [this message]
2015-08-21  5:49                                       ` Richard Henderson
2015-08-21  6:05                                         ` Dennis Luehring
2015-08-21 15:47                                           ` Richard Henderson
2015-08-21 16:13                                             ` Aurelien Jarno
2015-08-21 16:41                                             ` Dennis Luehring
2015-08-22 16:45                                     ` Artyom Tarasenko
2015-08-22 17:47                                       ` Dennis Luehring
2015-08-22 18:53                                         ` Artyom Tarasenko
2015-08-23 12:11                                           ` Dennis Luehring
2015-08-23  0:41                                       ` Richard Henderson
2015-08-26 16:17                                         ` Artyom Tarasenko
2015-08-26 19:47                                           ` Richard Henderson
2015-08-27  5:54                                             ` Dennis Luehring
2015-08-27 15:04                                               ` Richard Henderson
2015-08-27 15:58                                             ` Artyom Tarasenko
2015-08-17 11:32                     ` Dennis Luehring
2015-08-03  7:58               ` Dennis Luehring
2015-08-03 14:51               ` Dennis Luehring
2015-08-03 15:59                 ` Karel Gardas
2015-08-03 19:51                   ` Dennis Luehring
2015-08-06  9:00                     ` Karel Gardas
2015-08-06  9:21                       ` Dennis Luehring
2015-08-06  9:27                         ` Dennis Luehring
2015-08-06 12:50                           ` Karel Gardas
2015-08-06 16:35                             ` Dennis Luehring
2015-08-18  4:25                       ` Dennis Luehring
2015-08-18  8:19                         ` Aurelien Jarno
2015-08-18 10:39                           ` Dennis Luehring
2015-08-18 11:21                           ` Dennis Luehring
     [not found]                         ` <CAMO55fkcW1eOaZSz2MJgqZEP29pTuHvTLe0Kna5eHYfg7cFyPA@mail.gmail.com>
2015-08-19  4:28                           ` Dennis Luehring
2015-07-29  8:07   ` Dennis Luehring
2015-07-29 15:03     ` Aurelien Jarno
2015-07-29  9:17 ` Karel Gardas
2015-07-29 10:20   ` Dennis Luehring
2015-07-29 13:45     ` Karel Gardas
2015-07-29 15:13       ` Aurelien Jarno
2015-07-29 10:55   ` Dennis Luehring
2015-07-29 12:34     ` Karel Gardas
2015-07-29 12:38       ` Karel Gardas
2015-07-29 13:55       ` Dennis Luehring
2015-07-29 14:41         ` Karel Gardas
2015-07-30  3:47           ` Dennis Luehring
2015-07-30  7:12             ` Paolo Bonzini
2015-07-30  8:31               ` Artyom Tarasenko
2015-08-02 19:12                 ` Alex Bennée
2015-07-30  7:55             ` Aurelien Jarno
2015-08-17 14:19               ` Artyom Tarasenko
2015-08-17 15:40                 ` Richard Henderson
2015-08-17 16:25                   ` Artyom Tarasenko
2015-08-17 21:08                     ` Aurelien Jarno
2015-08-27 15:29 ` Artyom Tarasenko
2015-09-02  4:34   ` Dennis Luehring

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=55D6A9DF.5070506@gmx.net \
    --to=dl.soluz@gmx.net \
    --cc=atar4qemu@gmail.com \
    --cc=aurelien@aurel32.net \
    --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 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.