From: Dennis Luehring <dl.soluz@gmx.net>
To: Richard Henderson <rth@twiddle.net>,
Artyom Tarasenko <atar4qemu@gmail.com>
Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
qemu-devel <qemu-devel@nongnu.org>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH] target-sparc: Store mmu index in TB flags
Date: Tue, 25 Aug 2015 21:17:46 +0200 [thread overview]
Message-ID: <55DCBF5A.9040003@gmx.net> (raw)
In-Reply-To: <55DCAF50.30807@twiddle.net>
Am 25.08.2015 um 20:09 schrieb Richard Henderson:
> But you're right, it would be nice to put together a coherent set of
> benchmarks. Ideally, a guest kernel plus minimal ramdisk with the tests
> pre-loaded so that we can boot and run ./benchmark at the prompt. That's
> the sort of thing we can easily upload to the wiki and share.
i've found these benchmarks in NetBSDs benchmarks packages
http://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/benchmarks/README.html
hint.serial-98.06.12
<http://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/benchmarks/hint/README.html>:
Scalable benchmark for testing CPU and memory performance
nbench-2.2.3
<http://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/benchmarks/nbench/README.html>:
Benchmark tool for CPU, FPU and memory
ramspeed-2.6.0
<http://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/benchmarks/ramspeed/README.html>:
RAMspeed, a cache and memory benchmarking tool
would allow to do benchmarking with NetBSD 6.1.5 under native x64,
qemu-amd64, qemu-sparc64 and qemu-alpha
based on more or less the "same" OS/source
next prev parent reply other threads:[~2015-08-25 19:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 4:19 [Qemu-devel] [PATCH] target-sparc: Store mmu index in TB flags Richard Henderson
2015-08-25 5:45 ` Dennis Luehring
2015-08-25 6:44 ` Artyom Tarasenko
2015-08-25 7:46 ` Dennis Luehring
2015-08-25 14:25 ` Richard Henderson
2015-08-25 14:37 ` Dennis Luehring
2015-08-25 18:09 ` Richard Henderson
2015-08-25 19:03 ` Dennis Luehring
2015-08-25 19:17 ` Dennis Luehring [this message]
2015-08-25 16:53 ` Artyom Tarasenko
2015-08-25 6:35 ` Artyom Tarasenko
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=55DCBF5A.9040003@gmx.net \
--to=dl.soluz@gmx.net \
--cc=atar4qemu@gmail.com \
--cc=aurelien@aurel32.net \
--cc=mark.cave-ayland@ilande.co.uk \
--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).