All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Jason Wang <jasowang@redhat.com>, qemu-devel@nongnu.org
Cc: cornelia.huck@de.ibm.com, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH V4 0/3] Set correct blk feature for virtio 1.0
Date: Mon, 27 Jul 2015 13:56:15 +0200	[thread overview]
Message-ID: <55B61C5F.10702@redhat.com> (raw)
In-Reply-To: <1437990561-22134-1-git-send-email-jasowang@redhat.com>



On 27/07/2015 11:49, Jason Wang wrote:
> Hi all:
> 
> This series tries to set feature correctly for virtio-blk when virtio
> 1.0 is supported. Two isssues were addressed according to the spec:
> 
> - scsi passthrough was not support in 1.0. This is done through: 1)
>   let get_features() can fail 2) fail the get_features() when both
>   scsi and virtio 1.0 is enabled.
> - any layout must be set for transitional device. This is done by set
>   any layout when 1.0 is supported.
> 
> Changes from V3:
> - rebase on top of Michael's any_layout fixes

With my fixup to the error message,

Acked-by: Paolo Bonzini <pbonzini@redhat.com>

Paolo

> Changes from V2:
> - Keep scsi=on by default since virtio 1.0 is disabled by default
> - Advertise VIRTIO_BLK_F_SCSI unconditionally if virtio 1.0 is
>   disabled
> 
> Changes from V1:
> - Split virtio-net changes out of the series
> - Enable VIRTIO_BLK_F_SCSI only when scsi is set
> - Disable scsi by default and compat it for legacy machine types
> - Let get_features() can fail and fail the initialization of
>   virito-blk when both 1.0 and scsi were supported.
> 
> Jason Wang (3):
>   virtio: get_features() can fail
>   virtio-blk: fail get_features when both scsi and 1.0 were set
>   virtio-blk: only clear VIRTIO_F_ANY_LAYOUT for legacy device
> 
>  hw/9pfs/virtio-9p-device.c  |  3 ++-
>  hw/block/virtio-blk.c       | 15 ++++++++++++---
>  hw/char/virtio-serial-bus.c |  3 ++-
>  hw/display/virtio-gpu.c     |  3 ++-
>  hw/input/virtio-input.c     |  3 ++-
>  hw/net/virtio-net.c         |  3 ++-
>  hw/scsi/vhost-scsi.c        |  3 ++-
>  hw/scsi/virtio-scsi.c       |  3 ++-
>  hw/virtio/virtio-balloon.c  |  3 ++-
>  hw/virtio/virtio-bus.c      |  3 ++-
>  hw/virtio/virtio-rng.c      |  2 +-
>  include/hw/virtio/virtio.h  |  4 +++-
>  12 files changed, 34 insertions(+), 14 deletions(-)
> 

      parent reply	other threads:[~2015-07-27 11:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27  9:49 [Qemu-devel] [PATCH V4 0/3] Set correct blk feature for virtio 1.0 Jason Wang
2015-07-27  9:49 ` [Qemu-devel] [PATCH V4 1/3] virtio: get_features() can fail Jason Wang
2015-07-27  9:49 ` [Qemu-devel] [PATCH V4 2/3] virtio-blk: fail get_features when both scsi and 1.0 were set Jason Wang
2015-07-27 10:28   ` Paolo Bonzini
2015-07-27 10:39     ` Cornelia Huck
2015-07-27 11:23       ` Michael S. Tsirkin
2015-07-27 11:26     ` Michael S. Tsirkin
2015-07-27 11:30       ` Paolo Bonzini
2015-07-28  2:57       ` Jason Wang
2015-07-27  9:49 ` [Qemu-devel] [PATCH V4 3/3] virtio-blk: only clear VIRTIO_F_ANY_LAYOUT for legacy device Jason Wang
2015-07-27 10:30   ` Paolo Bonzini
2015-07-27 11:22     ` Michael S. Tsirkin
2015-07-27 11:30       ` Paolo Bonzini
2015-07-27 13:28       ` Cornelia Huck
2015-07-27 15:27         ` Michael S. Tsirkin
2015-07-27 11:56 ` Paolo Bonzini [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=55B61C5F.10702@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=jasowang@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 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.