From: Paolo Bonzini <pbonzini@redhat.com>
To: Xiexiangyou <xiexiangyou@huawei.com>
Cc: "qemu-devel-request@nongnu.org" <qemu-devel-request@nongnu.org>,
Luonengjun <luonengjun@huawei.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Huangpeng (Peter)" <peter.huangpeng@huawei.com>
Subject: Re: [Qemu-devel] [RFH] Qemu main thread is blocked in g_poll in windows guest
Date: Tue, 15 Oct 2013 14:30:23 +0200 [thread overview]
Message-ID: <525D355F.4060504@redhat.com> (raw)
In-Reply-To: <7A2C95E1327F7148AB122F200A3EFA403447CBE1@SZXEMA502-MBX.china.huawei.com>
Il 15/10/2013 14:18, Xiexiangyou ha scritto:
> (gdb) bt
> #0 0x00007f9ba661a423 in poll () from /lib64/libc.so.6
> #1 0x000000000059460f in os_host_main_loop_wait (timeout=4294967295) at main-loop.c:226
> #2 0x00000000005946a4 in main_loop_wait (nonblocking=0) at main-loop.c:464
> #3 0x0000000000619309 in main_loop () at vl.c:2182
> #4 0x000000000061fb5e in main (argc=54, argv=0x7fff879830c8, envp=0x7fff87983280) at vl.c:4611
This backtrace looks okay. poll is not holding the "iothread lock" and
thus the VCPU thread can run QEMU code.
It also looks like the VCPU thread is doing nothing special besides
running KVM_RUN. Did you take the backtrace during one of these "hangups"?
Paolo
next prev parent reply other threads:[~2013-10-15 12:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 10:21 [Qemu-devel] [RFH] Qemu main thread is blocked in g_poll in windows guest Xiexiangyou
2013-10-15 11:52 ` Paolo Bonzini
2013-10-15 12:18 ` Xiexiangyou
2013-10-15 12:30 ` Paolo Bonzini [this message]
2013-10-16 4:03 ` Xiexiangyou
2014-02-20 19:59 ` Andrey Korolyov
2013-10-21 13:56 ` David Weber
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=525D355F.4060504@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=luonengjun@huawei.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel-request@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=xiexiangyou@huawei.com \
/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).