From: Dennis Luehring <dl.soluz@gmx.net>
To: Artyom Tarasenko <atar4qemu@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] Debian 7.8.0 SPARC64 on qemu - anything i can do to speedup the emulation?
Date: Wed, 29 Jul 2015 10:07:14 +0200 [thread overview]
Message-ID: <55B889B2.2040609@gmx.net> (raw)
In-Reply-To: <CACXAS8CYCyGW+4P0=DzJu8D+zsiAzMZhzBqWrZVuUBO-HEkiwQ@mail.gmail.com>
currently qemu emulates an TI UltraSparc IIi (Sabre)
does that mean that qemu emulates the sparc somwhere around 270-480Mhz
(i can't find the running mhz in qemu)
how can i get the Mhz the sparc is running?
(cpuinfo and lscpu missing Mhz, dmidecode is not available,
/sys/devices/system/cpu/cpu*/cpufreq/scaling_max_freq is empty, lshw
does not show anything)
is there a way to increase the clock speed of the cpu/fpu without
killing other timemings - or switch to a different cpu?
(because i do not need real speed behavior for my testing)
another benchmark
sysbench (0.4.12) --num-threads=1 --test=cpu --cpu-max-prime=2000 run
Host x64 : 1.3580s
Qemu SPARC64: 184.2532s
------------------------------
/proc/cpuinfo:
cpu : TI UltraSparc IIi (Sabre)
fpu : UltraSparc IIi integrated FPU
pmu : ultra12
prom : OBP 3.10.24 1999/01/01 01:01
type : sun4u
ncpus probed : 1
ncpus active : 1
D$ parity tl1 : 0
I$ parity tl1 : 0
Cpu0ClkTck : 0000000005f5e100
cpucaps : flush,stbar,swap,muldiv,v9,mul32,div32,v8plus,vis
MMU Type : Spitfire
lscpu:
Architecture: sparc64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Big Endian
CPU(s): 1
On-line CPU(s) list: 0
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 1
https://en.wikipedia.org/wiki/UltraSPARC_II
UltraSPARC IIi
The UltraSPARC IIi "Sabre" was a low-cost version introduced in 1997
that operated at 270 to 360 MHz.
It was fabricated in a 0.35 µm process and possessed a die size of 156 mm².
It dissipated 21 W and used a 1.9 V power supply. It had a 256 KB to 2
MB L2 cache.
In 1998, a version code-named Sapphire-Red, was fabricated in a 0.25 µm
process, enabling
the microprocessor to operate at 333 to 480 MHz. It dissipated 21 W at
440 MHz and used a 1.9 V power supply.
---------------------------------
my host machine is
lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 8
On-line CPU(s) list: 0-7
Thread(s) per core: 2
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 30
Model name: Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz
Stepping: 5
CPU MHz: 933.000
CPU max MHz: 1734,0000
CPU min MHz: 933,0000
BogoMIPS: 3458.22
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 6144K
NUMA node0 CPU(s): 0-7
Am 28.07.2015 um 11:54 schrieb Artyom Tarasenko:
> On Tue, Jul 28, 2015 at 9:52 AM, Dennis Luehring <dl.soluz@gmx.net> wrote:
> > (i've posted the question already on qemu-discuss@nongnu.org but was toled
> > to better use this mailing list)
> >
> > i've prepared an Debian 7.8.0 image for SPARC64/qemu emulation for C/C++
> > development before-real-hardware big-endian/unaligned tests
> >
> > i've benchmarked compiling of single pugixml.cpp
> > (https://github.com/zeux/pugixml/blob/master/src/pugixml.cpp)
> >
> > qemu-system-sparc64: >180sek
> > x64 native : ~ 2sek
> >
> > so my sparc64 emulation is around 90 times slower then native x64
> >
> > my system:
> >
> > using lastest qemu git 2.3.x, with virtio for harddisk/network and qcow2
> > image
> >
> > https://depositfiles.com/files/sj20aqwp0 (~280MB
> > press the "regular download" button, wait some seconds, solve the
> > chapca, "download file in regular mode by browser"
> >
> > there is pugi_sparc.txt in the 7z which describes how to start,use and
> > what is installed in the image
> >
> > qemu runs natively under a ubuntu 15.04 (x64), Core i7, 8GB system doing
> > nothing but qemu
> >
> > installed is
> >
> > gcc/g++ 4.6
> > make
> > sshd running
> >
> > compiling cmake 2.3.2 tooked around 10h
> > compiling pugixml takes also very very long
> >
> > "top perf" from guest and host while compiling pugixml don't show big
> > blockers or something over time
> > http://pastebin.com/D2fUpPrM
> >
> > anything i can do to speedup the emulation?
>
> Maybe try the fresh tcg optimizer improvements from Aurelien:
> https://lists.gnu.org/archive/html/qemu-devel/2015-07/msg05133.html
>
> Artyom
>
next prev parent reply other threads:[~2015-07-29 8:07 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
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 [this message]
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=55B889B2.2040609@gmx.net \
--to=dl.soluz@gmx.net \
--cc=atar4qemu@gmail.com \
--cc=aurelien@aurel32.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 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).