qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: cornelia.huck@de.ibm.com, pbonzini@redhat.com,
	qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH V3 2/3] virtio-blk: fail get_features when both scsi and 1.0 were set
Date: Wed, 22 Jul 2015 17:45:23 +0800	[thread overview]
Message-ID: <55AF6633.5060701@redhat.com> (raw)
In-Reply-To: <20150722093145.GD12010@redhat.com>



On 07/22/2015 05:31 PM, Daniel P. Berrange wrote:
> On Wed, Jul 22, 2015 at 01:59:51PM +0800, Jason Wang wrote:
>> SCSI passthrough was no longer supported in virtio 1.0, so this patch
>> fail the get_features() when both 1.0 and scsi is set. And also only
>> advertise VIRTIO_BLK_F_SCSI for legacy virtio-blk device.
> Why is SCSI passthrough support not available in virtio 1.0 ? This
> will cause a regression for any users of that as & when QEMU changes
> to use virtio 1.0 by default. Can we not fix this regression instead.
>
> Regards,
> Daniel


I can find some discussion here:

http://comments.gmane.org/gmane.comp.emulators.virtio.devel/865

Paolo may know more about this.

  reply	other threads:[~2015-07-22  9:45 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-22  5:59 [Qemu-devel] [PATCH V3 0/3] Set correct blk feature for virtio 1.0 Jason Wang
2015-07-22  5:59 ` [Qemu-devel] [PATCH V3 1/3] virtio: get_features() can fail Jason Wang
2015-07-22  5:59 ` [Qemu-devel] [PATCH V3 2/3] virtio-blk: fail get_features when both scsi and 1.0 were set Jason Wang
2015-07-22  8:58   ` Cornelia Huck
2015-07-22  9:21     ` Michael S. Tsirkin
2015-07-22 10:25       ` Cornelia Huck
2015-07-22 10:32         ` Michael S. Tsirkin
2015-07-22 10:38           ` Cornelia Huck
2015-07-22 10:44             ` Michael S. Tsirkin
2015-07-22 10:55               ` Cornelia Huck
2015-07-22 14:53                 ` Michael S. Tsirkin
2015-07-22 16:11                   ` Cornelia Huck
2015-07-22 16:34                     ` Michael S. Tsirkin
2015-07-23  9:07                       ` Cornelia Huck
2015-07-23  9:37                         ` Paolo Bonzini
2015-07-23 10:15                           ` Cornelia Huck
2015-07-22  9:35     ` Jason Wang
2015-07-22 10:23       ` Cornelia Huck
2015-07-22  9:25   ` Michael S. Tsirkin
2015-07-22  9:52     ` Jason Wang
2015-07-22 10:12       ` Michael S. Tsirkin
2015-07-22 10:13         ` Michael S. Tsirkin
2015-07-22  9:31   ` Daniel P. Berrange
2015-07-22  9:45     ` Jason Wang [this message]
2015-07-22 10:19     ` Michael S. Tsirkin
2015-07-22 11:40       ` Paolo Bonzini
2015-07-22 11:46         ` Daniel P. Berrange
2015-07-22 11:53           ` Paolo Bonzini
2015-07-22 14:56             ` Michael S. Tsirkin
2015-07-22 16:15         ` Michael S. Tsirkin
2015-07-22 16:42           ` Paolo Bonzini
2015-07-22  5:59 ` [Qemu-devel] [PATCH V3 3/3] virtio-blk: set VIRTIO_F_ANY_LAYOUT when 1.0 is supported Jason Wang

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=55AF6633.5060701@redhat.com \
    --to=jasowang@redhat.com \
    --cc=berrange@redhat.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@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).