From: "Richard W.M. Jones" <rjones@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Drew Jones <drjones@redhat.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Alexander Graf <agraf@suse.de>, Gerd Hoffmann <kraxel@redhat.com>,
Laszlo Ersek <lersek@redhat.com>,
Christoffer Dall <christoffer.dall@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v2] arm: add fw_cfg to "virt" board
Date: Tue, 9 Dec 2014 15:54:00 +0000 [thread overview]
Message-ID: <20141209155400.GB15695@redhat.com> (raw)
In-Reply-To: <CAFEAcA9yY0av8Gk4JNp=5V41T-qdtTZdmh=7U2QFBiFOkMWwBA@mail.gmail.com>
On Tue, Dec 09, 2014 at 03:47:44PM +0000, Peter Maydell wrote:
> On 9 December 2014 at 15:41, Laszlo Ersek <lersek@redhat.com> wrote:
> > Again, this was the idea that Rich had in 2010 (see the links in the
> > discussion thus far). It was rejected back then (which is why I didn't
> > even try to resurrect it now), and Peter has now asked if anything has
> > changed that would make that approach more acceptable now.
> >
> > "Avi and Gleb not hanging around so they can't block the approach now"
> > might or might not be such a change; I don't know. But, I tend to trust
> > their opinion, even if dates back to 2010 in this case.
>
> Yeah, this is about my point of view. A direct-write-to-memory
> fw_cfg doesn't seem too unreasonable to me, but it would be nice
> to see a solidly argued case from its proponents to counterbalance
> the previous rejection.
The argument for is that it's essentially instantaneous.
This is a big deal for libguestfs where even our new initrd (1.5 MB)
takes a noticable fraction of a second to load, and we want to get our
total start-up time down to 3 seconds to match x86.
> > Anyway I'm certainly not opposed to performance, so if someone can
> > thoroughly refute everything they said in that thread, go ahead.
>
> As far as I can tell the main line of argument was "if you're
> using fw_cfg to transfer huge amounts of data you're doing
> something wrong".
>
> Is ARM much higher overhead than x86 for these accesses?
On a slightly related topic, virtio-mmio traps are slow:
https://bugzilla.redhat.com/show_bug.cgi?id=1123555
This also kills libguestfs performance -- throughput this time, rather
than start-up time.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
next prev parent reply other threads:[~2014-12-09 16:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 16:59 [Qemu-devel] [PATCH v2] arm: add fw_cfg to "virt" board Laszlo Ersek
2014-12-05 18:42 ` Peter Maydell
2014-12-05 18:53 ` Laszlo Ersek
2014-12-08 14:01 ` Laszlo Ersek
2014-12-08 14:41 ` Peter Maydell
2014-12-08 14:43 ` Peter Maydell
2014-12-08 19:39 ` Laszlo Ersek
2014-12-08 21:19 ` Laszlo Ersek
2014-12-08 21:34 ` Peter Maydell
2014-12-08 23:20 ` Laszlo Ersek
2014-12-08 23:18 ` Christopher Covington
2014-12-08 23:51 ` Peter Maydell
2014-12-09 0:05 ` Laszlo Ersek
2014-12-09 9:31 ` Gerd Hoffmann
2014-12-09 15:41 ` Laszlo Ersek
2014-12-09 15:47 ` Peter Maydell
2014-12-09 15:54 ` Richard W.M. Jones [this message]
2014-12-10 11:13 ` Paolo Bonzini
2014-12-10 13:10 ` Andrew Jones
2014-12-09 0:05 ` Laszlo Ersek
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=20141209155400.GB15695@redhat.com \
--to=rjones@redhat.com \
--cc=agraf@suse.de \
--cc=ard.biesheuvel@linaro.org \
--cc=christoffer.dall@linaro.org \
--cc=drjones@redhat.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=peter.maydell@linaro.org \
--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.