From: "Andreas Färber" <andreas.faerber@web.de>
To: Torbjorn Granlund <tg@gmplib.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu varying performance
Date: Wed, 28 Sep 2011 09:15:20 +0200 [thread overview]
Message-ID: <4E82C988.9020907@web.de> (raw)
In-Reply-To: <86ty7xfr7c.fsf@shell.gmplib.org>
Am 28.09.2011 02:25, schrieb Torbjorn Granlund:
> Another issue I ran into what the sh4 qemu performance. It is much
> worse than other qemu ports (except perhaps ppc64). What is the reason
> behind that? (The idle thing works well for sh4, though.)
>
> My host system runs FreeBSD 8.2. The Debian installs all use 6.0.2.
Is your host 32-bit? Which architecture?
Andreas
next prev parent reply other threads:[~2011-09-28 7:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 0:25 [Qemu-devel] Qemu varying performance Torbjorn Granlund
2011-09-28 7:15 ` Andreas Färber [this message]
2011-09-28 8:23 ` Torbjorn Granlund
2011-09-28 9:34 ` Edgar E. Iglesias
2011-09-29 14:53 ` Torbjorn Granlund
-- strict thread matches above, loose matches on Subject: below --
2005-01-26 2:49 [Qemu-devel] qemu " Lee
2005-01-26 13:34 ` Johannes Schindelin
2005-01-26 14:49 ` Daniel Egger
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=4E82C988.9020907@web.de \
--to=andreas.faerber@web.de \
--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).