From: Laszlo Ersek <lersek@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: peter.maydell@linaro.org, Drew Jones <drjones@redhat.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
qemu-devel@nongnu.org"Richard W.M. Jones" <rjones@redhat.com>,
Christoffer Dall <christoffer.dall@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v2] arm: add fw_cfg to "virt" board
Date: Tue, 09 Dec 2014 16:41:09 +0100 [thread overview]
Message-ID: <54871815.4040103@redhat.com> (raw)
In-Reply-To: <1418117468.30093.24.camel@nilsson.home.kraxel.org>
On 12/09/14 10:31, Gerd Hoffmann wrote:
> Hi,
>
>> So... after playing with this thing for some time, it's become clear
>> that "MMIO traps" are painfully slow on the aarch64 platform we've been
>> working on (using KVM).
>
> So, as we don't have compatibility requirements, and we also can't play
> tricks like using x86 string instructions: How about a completely
> different, dma-style interface for fw_cfg access?
>
> One register for the (physical) target address.
> One register for the transfer size.
> One register for the fw_cfg entry.
> Possibly one register for the fw_cfg offset (not really needed, but
> avoids the need for side effects such as writing fw_cfg entry register
> clearing the offset).
> One register to kick the transfer.
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.
Anyway I'm certainly not opposed to performance, so if someone can
thoroughly refute everything they said in that thread, go ahead.
Thanks!
Laszlo
next prev parent reply other threads:[~2014-12-09 15:41 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 [this message]
2014-12-09 15:47 ` Peter Maydell
2014-12-09 15:54 ` Richard W.M. Jones
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=54871815.4040103@redhat.com \
--to=lersek@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=drjones@redhat.com \
--cc=kraxel@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 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).