qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin O'Connor <kevin@koconnor.net>
To: "Marc Marí" <markmb@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC 2/7] fw_cfg dma interface
Date: Wed, 22 Jul 2015 13:18:04 -0400	[thread overview]
Message-ID: <20150722171804.GA2717@morn.localdomain> (raw)
In-Reply-To: <20150722103112.1d97386b@markmb_rh>

On Wed, Jul 22, 2015 at 10:31:12AM +0200, Marc Marí wrote:
> On Wed, 22 Jul 2015 00:24:34 -0400
> "Kevin O'Connor" <kevin@koconnor.net> wrote:
> > On Tue, Jul 21, 2015 at 06:03:41PM +0200, Marc Marí wrote:
> > > From: Gerd Hoffmann <kraxel@redhat.com>
> > > 
> > > First draft of a fw_cfg dma interface.  Designed as add-on to the
> > > extisting fw_cfg interface, i.e. there is no select register.  There
> > > are four 32bit registers:  Target address (low and high bits),
> > > transfer length, control register.
> > 
> > If I read this interface correctly, a guest will have at least six
> > faults to complete a typical fw_cfg dma transfer (select, target low,
> > target high, transfer length, control register write, control register
> > read).  I wonder if using a DMA transfer descriptor might be more
> > efficient.
[...]
> That is probably faster and more flexible. I think it's a good step
> forward. But, on the other side, is this a too big break of what is
> actually implemented in MMIO?
> 
> At the end we will have MMIO version, with a select and a data
> register, and DMA version, with a 64 bit address register. How can we
> differentiate between versions? Laszlo talks about the ID, but this is
> already in one of the fields (so you need to know the protocol to get
> the protocol). How could we do this transition more seamless?

Well, one way would be to place a 64bit MMIO (or IO) register at a
magic address.  The firmware could then read the magic address and
check it against a signature (eg, "QEMU CFG").  If the signature
matches then it would know it could use the DMA version of the fw_cfg
interface (by issuing writes, instead of reads, to the magic address).
The firmware would then not have to use the older select/data fw_cfg
interface at all.

Another possibility would be to place the new fw_cfg dma register
address into a named fw_cfg "file" (eg, "fw_cfg_dma").  The firmware
could then use the existing select/data fw_cfg interface to check if
the new dma interface is available by scanning for that "fw_cfg_dma"
file.  This has the advantage of not requiring a new "magic address",
but has the disadvantage of a more complex probe.

Just a thought,
-Kevin

  reply	other threads:[~2015-07-22 17:18 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-21 16:03 [Qemu-devel] [RFC 0/7] fw_cfg dma interface Marc Marí
2015-07-21 16:03 ` [Qemu-devel] [RFC 1/7] fw_cfg: document fw_cfg_modify_iXX() update functions Marc Marí
2015-07-21 19:28   ` Laszlo Ersek
2015-07-21 16:03 ` [Qemu-devel] [RFC 2/7] fw_cfg dma interface Marc Marí
2015-07-21 19:44   ` Laszlo Ersek
2015-07-22  8:19     ` Marc Marí
2015-07-22 10:01       ` Laszlo Ersek
2015-07-22 11:30     ` Andrew Jones
2015-07-22 11:40       ` Laszlo Ersek
2015-07-22  4:24   ` Kevin O'Connor
2015-07-22  8:31     ` Marc Marí
2015-07-22 17:18       ` Kevin O'Connor [this message]
2015-07-23 13:13         ` Laszlo Ersek
2015-07-23 13:35           ` Peter Maydell
2015-07-23 13:45             ` Laszlo Ersek
2015-07-23 13:48               ` Marc Marí
2015-07-23 14:14             ` Kevin O'Connor
2015-07-22  9:31     ` Stefan Hajnoczi
2015-07-21 16:03 ` [Qemu-devel] [RFC 3/7] fw_cfg dma: adapt to vmstate changes Marc Marí
2015-07-21 16:16   ` Stefan Hajnoczi
2015-07-21 16:03 ` [Qemu-devel] [RFC 4/7] enable fw_cfg dma for arm virt Marc Marí
2015-07-21 17:04   ` Peter Maydell
2015-07-21 19:48     ` Laszlo Ersek
2015-07-22  8:44     ` Marc Marí
2015-07-21 16:03 ` [Qemu-devel] [RFC 5/7] fw_cfg file sort Marc Marí
2015-07-21 16:18   ` Stefan Hajnoczi
2015-07-21 19:53     ` Laszlo Ersek
2015-07-22  8:46       ` Marc Marí
2015-07-21 16:03 ` [Qemu-devel] [RFC 6/7] Add offset register to fw_cfg DMA interface Marc Marí
2015-07-21 16:26   ` Stefan Hajnoczi
2015-07-21 20:06     ` Laszlo Ersek
2015-07-21 20:16       ` Kevin O'Connor
2015-07-21 20:36         ` Laszlo Ersek
2015-07-22  4:11           ` Kevin O'Connor
2015-07-22  9:03           ` Marc Marí
2015-07-21 16:34   ` Stefan Hajnoczi
2015-07-21 16:03 ` [Qemu-devel] [RFC 7/7] fw_cfg DMA for x86 Marc Marí
2015-07-21 17:14   ` Peter Maydell
2015-07-22  9:06     ` Marc Marí

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=20150722171804.GA2717@morn.localdomain \
    --to=kevin@koconnor.net \
    --cc=kraxel@redhat.com \
    --cc=markmb@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).