qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Artyom Tarasenko <atar4qemu@gmail.com>
To: Torbjorn Granlund <tg@gmplib.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Reporting Heisenbugs in qemu
Date: Tue, 7 May 2013 23:29:20 +0200	[thread overview]
Message-ID: <CACXAS8ABdA5YAtESCUo1_4APuWnKve+OE6h4JXfE5zCNi-a54g@mail.gmail.com> (raw)
In-Reply-To: <8661yvqasu.fsf@shell.gmplib.org>

On Tue, May 7, 2013 at 1:38 PM, Torbjorn Granlund <tg@gmplib.org> wrote:
> The 2nd table of http://gmplib.org/devel/testsystems.html shows all
> emulated systems I am using, most of which are qemu-based.

Do I read it correct that qemu-system-ppc64 with the slowdown factor
of 33 is ~3 times faster than qemu-system-sparc64 with the slowdown
factor of 96 ?
Do they both use Debian Wheezy guest? You have a remark that ppc64 has
problems with its clock. Was it taken into account when the slowdown
factors were calculated?

Artyom

--
Regards,
Artyom Tarasenko

linux/sparc and solaris/sparc under qemu blog:
http://tyom.blogspot.com/search/label/qemu

  parent reply	other threads:[~2013-05-07 21:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-07 11:38 [Qemu-devel] Reporting Heisenbugs in qemu Torbjorn Granlund
2013-05-07 13:25 ` Mark Cave-Ayland
2013-05-07 15:50 ` Aurelien Jarno
2013-05-07 16:18   ` Torbjorn Granlund
2013-05-07 21:29 ` Artyom Tarasenko [this message]
2013-05-07 21:43   ` Torbjorn Granlund
2013-05-07 21:53     ` Artyom Tarasenko
2013-05-07 23:06       ` Torbjorn Granlund
2013-05-07 22:57   ` Aurelien Jarno
2013-05-08  7:25     ` Paolo Bonzini
2013-05-08  9:45       ` Torbjorn Granlund
2013-05-08 10:18         ` Paolo Bonzini
2013-05-09 18:15           ` Blue Swirl
2013-05-08 10:35         ` Aurelien Jarno
2013-05-09  0:28         ` Rob Landley

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=CACXAS8ABdA5YAtESCUo1_4APuWnKve+OE6h4JXfE5zCNi-a54g@mail.gmail.com \
    --to=atar4qemu@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=tg@gmplib.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).