Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: thuth@linux.vnet.ibm.com, qemu-devel@nongnu.org,
	kvm@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH RFC v2 00/12] qemu: towards virtio-1 host support
Date: Tue, 25 Nov 2014 18:16:31 +0100	[thread overview]
Message-ID: <20141125181631.3f92d395.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <20141125164410.GA21646@redhat.com>

On Tue, 25 Nov 2014 18:44:10 +0200
"Michael S. Tsirkin" <mst@redhat.com> wrote:

> On Tue, Nov 25, 2014 at 02:24:11PM +0100, Cornelia Huck wrote:
> > Hi,
> > 
> > here's the next version of my virtio-1 qemu patchset. Using virtio-1
> > virtio-blk and virtio-net devices with a guest kernel built from
> > <1416829787-14252-1-git-send-email-mst@redhat.com> still seems to
> > work for the virtio-ccw transport.
> 
> I posted v4, would appreciate an explicit tested-by from you
> on that thread.

I was still reviewing v3 :)

I'll put it on my todo list for tomorrow.

> 
> > 
> > Changes from v1:
> > - rebased against current master
> > - don't advertise VERSION_1 for all devices, make devices switch it on
> >   individually
> 
> So from ccw perspective, all that's left is to convert more devices?
> 

I'll probably need to look into the explicit command reject for
FEATURES_OK, but other than that, only the individual devices are left
AFAICS.

      reply	other threads:[~2014-11-25 17:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25 13:24 [PATCH RFC v2 00/12] qemu: towards virtio-1 host support Cornelia Huck
2014-11-25 13:24 ` [PATCH RFC v2 01/12] linux-headers/virtio_config: Update with VIRTIO_F_VERSION_1 Cornelia Huck
2014-11-25 13:24 ` [PATCH RFC v2 02/12] virtio: cull virtio_bus_set_vdev_features Cornelia Huck
2014-11-25 13:24 ` [PATCH RFC v2 03/12] virtio: support more feature bits Cornelia Huck
2014-11-25 13:24 ` [PATCH RFC v2 04/12] s390x/virtio-ccw: fix check for WRITE_FEAT Cornelia Huck
2014-11-25 13:24 ` [PATCH RFC v2 05/12] virtio: introduce legacy virtio devices Cornelia Huck
2014-11-25 13:24 ` [PATCH RFC v2 06/12] virtio: allow virtio-1 queue layout Cornelia Huck
2014-11-25 13:24 ` [PATCH RFC v2 07/12] dataplane: allow virtio-1 devices Cornelia Huck
2014-11-25 17:55   ` Greg Kurz
2014-11-25 18:01     ` Cornelia Huck
2014-11-25 13:24 ` [PATCH RFC v2 08/12] s390x/css: Add a callback for when subchannel gets disabled Cornelia Huck
2014-11-25 13:24 ` [PATCH RFC v2 09/12] s390x/virtio-ccw: add virtio set-revision call Cornelia Huck
2014-11-25 13:24 ` [PATCH RFC v2 10/12] s390x/virtio-ccw: support virtio-1 set_vq format Cornelia Huck
2014-11-25 13:24 ` [PATCH RFC v2 11/12] virtio-net/virtio-blk: enable virtio 1.0 Cornelia Huck
2014-11-25 13:24 ` [PATCH RFC v2 12/12] s390x/virtio-ccw: " Cornelia Huck
2014-11-25 16:44 ` [PATCH RFC v2 00/12] qemu: towards virtio-1 host support Michael S. Tsirkin
2014-11-25 17:16   ` Cornelia Huck [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=20141125181631.3f92d395.cornelia.huck@de.ibm.com \
    --to=cornelia.huck@de.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@linux.vnet.ibm.com \
    --cc=virtualization@lists.linux-foundation.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