From: Rob Landley <rob@landley.net>
To: Artyom Tarasenko <atar4qemu@googlemail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Significant performance regression in qemu-system-mips.
Date: Thu, 25 Mar 2010 12:33:33 -0500 [thread overview]
Message-ID: <201003251233.34579.rob@landley.net> (raw)
In-Reply-To: <fb8d4f71003250220y585620f8r973721e91f57919b@mail.gmail.com>
On Thursday 25 March 2010 04:20:26 Artyom Tarasenko wrote:
> 2010/3/24 Rob Landley <rob@landley.net>:
> > I have a native build under qemu that gets killed if it doesn't produce a
> > line of output for 60 seconds (hang detection enforced by the host
> > monitoring qemu's stdout with --nographic, not from within qemu).
> >
> > In the most recent release version, it never came close to triggering on
> > mips with a 30 second timeout. In the current -git version (well, as of
> > Thursday anyway), it triggers frequently (about 90% of the time) even
> > with a 60 second timeout.
>
> Are other platforms affected as well? Do your automated tests run
> against qemu-sparc meanwhile?
That was the only platform I hit this particular regression on. It affects
mips, mipsel, and mips64.
The arm, x86, and x86-64 targets built to the end just fine.
Sparc works fine from a performance perspective (the timeout doesn't trigger),
it just dies building strace with:
In file included from file.c:88:^M
/usr/bin/../include/asm/stat.h:56: error: expected specifier-qualifier-list
before 'uid16_t'^
Which is either an strace bug or something wrong with the kernel headers,
either way I need too track that down and fix it.
Powerpc got broken by the 2.6.32->2.6.33 kernel upgrade (the hard drives don't
work because something broke in DMA interrupt handling, I'm bisecting it), so
I can't comment on its performance at the moment. I'll get back to you on
that one.
As far as I can tell the sh4 linux-kernel maintainer officially doesn't care
about anybody who isn't employed by his company, so I'm not sure I still care
about supporting that platform. It's not real hardware, it's a one-company
toy:
http://permalink.gmane.org/gmane.linux.ports.sh.devel/7233
http://permalink.gmane.org/gmane.linux.ports.sh.devel/7237
There aren't any system emulations for m68k and alpha upstream in qemu yet,
although I live in hope...
Rob
--
Latency is more important than throughput. It's that simple. - Linus Torvalds
next prev parent reply other threads:[~2010-03-25 17:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 20:34 [Qemu-devel] Significant performance regression in qemu-system-mips Rob Landley
2010-03-25 9:20 ` Artyom Tarasenko
2010-03-25 17:33 ` Rob Landley [this message]
2010-03-25 23:25 ` Aurelien Jarno
2010-03-25 23:57 ` Alexander Graf
2010-03-26 2:44 ` Rob Landley
2010-04-01 13:49 ` Andreas Färber
2010-04-01 23:42 ` Alexander Graf
2010-04-02 8:56 ` Aurelien Jarno
2010-04-03 5:49 ` Rob Landley
2010-03-26 9:53 ` Rob Landley
2010-03-26 19:00 ` Aurelien Jarno
2010-03-26 21:47 ` Rob Landley
2010-03-27 12:32 ` Aurelien Jarno
2010-03-27 23:01 ` Rob Landley
2010-03-28 14:57 ` Aurelien Jarno
2010-03-28 18:40 ` Rob Landley
2010-03-28 16:33 ` [Qemu-devel] " Paolo Bonzini
2010-04-01 21:33 ` [Qemu-devel] " Aurelien Jarno
2010-04-03 4:58 ` 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=201003251233.34579.rob@landley.net \
--to=rob@landley.net \
--cc=atar4qemu@googlemail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.