From: Jan Kiszka <jan.kiszka@web.de>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] KVM brokenness due to IO thread changes
Date: Tue, 28 Apr 2009 09:40:01 +0200 [thread overview]
Message-ID: <49F6B2D1.8070906@web.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 649 bytes --]
Hi,
this is a heads-up, maybe someone has some time to look into this over
the day: I seems like the IO thread changes caused a few regressions to
the KVM mode.
When I keep this feature disabled, I see strange hick-ups of the event
delivery mechanism, and the guest stops once in a while for a second or
so. Attaching strace makes the whole process terminate early (looks like
it triggers a race in the signal handling). And when I enable the IO
thread, I immediately get a deadlock on qemu_global_mutex.
Moreover:
CC i386-softmmu/vl.o
/data/qemu/vl.c:4380: warning: ‘qemu_calculate_timeout’ defined but not used
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next reply other threads:[~2009-04-28 7:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 7:40 Jan Kiszka [this message]
2009-04-28 12:51 ` [Qemu-devel] KVM brokenness due to IO thread changes Marcelo Tosatti
2009-04-28 19:56 ` Jan Kiszka
2009-04-28 20:09 ` Anthony Liguori
2009-04-28 22:21 ` Marcelo Tosatti
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=49F6B2D1.8070906@web.de \
--to=jan.kiszka@web.de \
--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 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).