qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>
Subject: [Qemu-devel] virtio 1.0 state?
Date: Fri, 22 May 2015 15:56:13 +0200	[thread overview]
Message-ID: <1432302973.12533.63.camel@nilsson.home.kraxel.org> (raw)

  Hi,

Where we are in terms of virtio 1.0 support in qemu?

There hasn't been much activity in mst's virtio-1.0 branch recently, at
least not in the public version of it.  And it doesn't rebase easily to
latest master any more ;(

What are the blocking issues?  Anything I can do to speed up things?
Any chance we can get the core changes merged (64bit features for
example), even if virtio 1.0 support for virtio-pci is not ready yet?

cheers,
  Gerd

             reply	other threads:[~2015-05-22 13:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22 13:56 Gerd Hoffmann [this message]
2015-05-26  9:10 ` [Qemu-devel] virtio 1.0 state? Cornelia Huck
2015-05-27 14:47   ` Gerd Hoffmann
2015-05-28 10:29   ` Gerd Hoffmann
2015-05-28 11:06     ` Cornelia Huck
2015-05-28 12:11       ` Michael S. Tsirkin

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=1432302973.12533.63.camel@nilsson.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=mst@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 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).