From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org, mtosatti@redhat.com,
alex.williamson@redhat.com, mst@redhat.com, blauwirbel@gmail.com
Subject: Re: Slow PXE boot in qemu.git (fast in qemu-kvm.git)
Date: Sun, 10 Apr 2011 11:19:22 +0300 [thread overview]
Message-ID: <4DA1680A.5080901@redhat.com> (raw)
In-Reply-To: <4D9FAD71.5020503@codemonkey.ws>
On 04/09/2011 03:50 AM, Anthony Liguori wrote:
>
> Maybe we're missing a coalesced io in qemu.git?
e1000 coalesced mmio is in qemu.git (always the chance it's broken, of
course). I don't think it would make a 5X difference in any case.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: kvm@vger.kernel.org, mst@redhat.com, mtosatti@redhat.com,
qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>,
blauwirbel@gmail.com, alex.williamson@redhat.com
Subject: [Qemu-devel] Re: Slow PXE boot in qemu.git (fast in qemu-kvm.git)
Date: Sun, 10 Apr 2011 11:19:22 +0300 [thread overview]
Message-ID: <4DA1680A.5080901@redhat.com> (raw)
In-Reply-To: <4D9FAD71.5020503@codemonkey.ws>
On 04/09/2011 03:50 AM, Anthony Liguori wrote:
>
> Maybe we're missing a coalesced io in qemu.git?
e1000 coalesced mmio is in qemu.git (always the chance it's broken, of
course). I don't think it would make a 5X difference in any case.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-04-10 8:19 UTC|newest]
Thread overview: 36+ 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-08 23:25 ` [Qemu-devel] " Luiz Capitulino
2011-04-09 0:50 ` Anthony Liguori
2011-04-09 0:50 ` [Qemu-devel] " Anthony Liguori
2011-04-09 12:03 ` Stefan Hajnoczi
2011-04-09 12:03 ` [Qemu-devel] " Stefan Hajnoczi
2011-04-10 8:19 ` Avi Kivity [this message]
2011-04-10 8:19 ` Avi Kivity
2011-04-11 18:35 ` Luiz Capitulino
2011-04-11 18:35 ` [Qemu-devel] " Luiz Capitulino
2011-04-11 19:00 ` Alex Williamson
2011-04-11 19:00 ` [Qemu-devel] " Alex Williamson
2011-04-11 19:15 ` Luiz Capitulino
2011-04-11 19:15 ` [Qemu-devel] " Luiz Capitulino
2011-04-11 20:04 ` Jan Kiszka
2011-04-11 20:04 ` [Qemu-devel] " Jan Kiszka
2011-04-11 20:14 ` Alex Williamson
2011-04-11 20:14 ` [Qemu-devel] " Alex Williamson
2011-04-11 20:18 ` Jan Kiszka
2011-04-11 20:18 ` [Qemu-devel] " Jan Kiszka
2011-04-11 20:29 ` Jan Kiszka
2011-04-11 20:29 ` [Qemu-devel] " Jan Kiszka
2011-04-12 8:09 ` Paolo Bonzini
2011-04-12 8:09 ` [Qemu-devel] " Paolo Bonzini
2011-04-11 21:05 ` Luiz Capitulino
2011-04-11 21:05 ` [Qemu-devel] " Luiz Capitulino
2011-04-11 21:18 ` Jan Kiszka
2011-04-11 21:18 ` [Qemu-devel] " Jan Kiszka
2011-04-12 0:39 ` Anthony Liguori
2011-04-12 0:39 ` [Qemu-devel] " Anthony Liguori
2011-04-12 7:42 ` Avi Kivity
2011-04-12 7:42 ` [Qemu-devel] " Avi Kivity
2011-04-09 10:34 ` Blue Swirl
2011-04-09 10:34 ` [Qemu-devel] " Blue Swirl
2011-04-11 12:51 ` Luiz Capitulino
2011-04-11 12:51 ` [Qemu-devel] " 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=4DA1680A.5080901@redhat.com \
--to=avi@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.com \
--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 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.