All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Xie, Huawei" <huawei.xie@intel.com>,
	Stefan Hajnoczi <stefanha@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] Would virtio support 64 bit address for vring virtqueue?
Date: Wed, 04 Sep 2013 16:22:55 +0930	[thread overview]
Message-ID: <87li3d6ptk.fsf@rustcorp.com.au> (raw)
In-Reply-To: <C37D651A908B024F974696C65296B57B019806B8@SHSMSX101.ccr.corp.intel.com>

"Xie, Huawei" <huawei.xie@intel.com> writes:
> If this is the case, one possible fix would be:
> 	Write two continuous 32bit DWORD to combine a 64bit address
> 	Use the upper 12 bits of PFN val to indicate if it is combined write
> In this way, we wouldn't break other virtio driver, register layout
> and only need a few lines of modification.

Note that (with OASIS) we are currently working on a v1.0 of the virtio
spec.  I recommend the OASIS virtio-dev mailing list
( https://www.oasis-open.org/mlmanage/ ) and in particular the thread on
Michael Tsirkin's proposal on using PCI capabilities:

https://lists.oasis-open.org/archives/virtio-comment/201308/msg00087.html

Cheers,
Rusty.

      reply	other threads:[~2013-09-04  7:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-28  3:18 [Qemu-devel] Would virtio support 64 bit address for vring virtqueue? Xie, Huawei
2013-08-28  8:07 ` Stefan Hajnoczi
2013-08-28  9:22   ` Xie, Huawei
2013-08-28 11:45     ` Laszlo Ersek
2013-08-28 12:20       ` Christian Borntraeger
2013-08-28 15:30       ` Xie, Huawei
2013-08-28 17:35         ` Anthony Liguori
2013-08-28 21:02           ` H. Peter Anvin
2013-08-28 21:28             ` Anthony Liguori
2013-08-28 21:38               ` Richard Henderson
2013-08-28 10:16   ` Xie, Huawei
2013-09-04  6:52     ` Rusty Russell [this message]

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=87li3d6ptk.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=huawei.xie@intel.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.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 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.