qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v1 00/14] fp-test + hostfloat


From: Alex Bennée
Subject: Re: [Qemu-devel] [PATCH v1 00/14] fp-test + hostfloat
Date: Thu, 22 Mar 2018 08:56:36 +0000
User-agent: mu4e 1.1.0; emacs 26.0.91

Emilio G. Cota <address@hidden> writes:

<snip>
> For performance numbers see the last patch.

Just another random data point as we've been using himeno for our SVE
wor:

Master:

8:05:45  address@hidden:~/l/q/qemu.git] master ± 
./aarch64-linux-user/qemu-aarch64 sve.demo/himeno-v80
mimax = 129 mjmax = 65 mkmax = 65
imax = 128 jmax = 64 kmax =64
cpu : 33.430299 sec.
Loop executed for 200 times
Gosa : 1.688752e-03
MFLOPS measured : 98.519585
Score based on MMX Pentium 200MHz : 3.052978

Host FPU:

08:25:03 address@hidden:~/l/q/qemu.git] master ± 
./aarch64-linux-user/qemu-aarch64 sve.demo/himeno-v80
mimax = 129 mjmax = 65 mkmax = 65
imax = 128 jmax = 64 kmax =64
cpu : 15.067773 sec.
Loop executed for 200 times
Gosa : 1.688752e-03
MFLOPS measured : 218.581684
Score based on MMX Pentium 200MHz : 6.773526

Given SVE also beats v80 code thanks to avoiding marshalling overhead by
doing bigger vectors I expect that improvement to be even better. Once
the SVE patches are re-based I'll measure them.

By the way I've been talking to some of the people at connect about
tracking performance over time. I got pointed to LLVM's LNT tool
(example: https://lnt.llvm.org/) so I might see if I can get a server
set up that we can start pushing numbers to. Have you come across any
other such things?

--
Alex Bennée



reply via email to

[Prev in Thread] Current Thread [Next in Thread]