From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Jan Kiszka <jan.kiszka@web.de>,
Luiz Capitulino <lcapitulino@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org, mtosatti@redhat.com,
mst@redhat.com, blauwirbel@gmail.com
Subject: Re: Slow PXE boot in qemu.git (fast in qemu-kvm.git)
Date: Tue, 12 Apr 2011 10:42:12 +0300 [thread overview]
Message-ID: <4DA40254.1050608@redhat.com> (raw)
In-Reply-To: <4DA39F50.8090108@codemonkey.ws>
On 04/12/2011 03:39 AM, Anthony Liguori wrote:
>> would say let it rest in peace. But maybe it points to a generic issues
>> that is just magnified by non-threaded mode.
> If it's most probably an architectural deficit of non-io-thread mode, I
>
> If gpxe is spinning waiting for I/O to complete, that's going to
> prevent select from running until the next signal (timer event).
Or the next signal (packet received on fd).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-04-12 7:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 23:25 Slow PXE boot in qemu.git (fast in qemu-kvm.git) Luiz Capitulino
2011-04-09 0:50 ` Anthony Liguori
2011-04-09 12:03 ` Stefan Hajnoczi
2011-04-10 8:19 ` Avi Kivity
2011-04-11 18:35 ` Luiz Capitulino
2011-04-11 19:00 ` Alex Williamson
2011-04-11 19:15 ` Luiz Capitulino
2011-04-11 20:04 ` Jan Kiszka
2011-04-11 20:14 ` Alex Williamson
2011-04-11 20:18 ` Jan Kiszka
2011-04-11 20:29 ` Jan Kiszka
2011-04-12 8:09 ` Paolo Bonzini
2011-04-11 21:05 ` Luiz Capitulino
2011-04-11 21:18 ` Jan Kiszka
2011-04-12 0:39 ` Anthony Liguori
2011-04-12 7:42 ` Avi Kivity [this message]
2011-04-09 10:34 ` Blue Swirl
2011-04-11 12:51 ` Luiz Capitulino
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=4DA40254.1050608@redhat.com \
--to=avi@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox