From: Paolo Bonzini <pbonzini@redhat.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/5] virtio-blk: disable scsi passthrough for 1.0 device
Date: Mon, 13 Jul 2015 17:13:26 +0200 [thread overview]
Message-ID: <55A3D596.9060401@redhat.com> (raw)
In-Reply-To: <20150713164129.52a8a2ed.cornelia.huck@de.ibm.com>
On 13/07/2015 16:41, Cornelia Huck wrote:
> On Mon, 13 Jul 2015 16:34:30 +0200
> Paolo Bonzini <pbonzini@redhat.com> wrote:
>> On 13/07/2015 15:20, Cornelia Huck wrote:
>>> This would imply that any transitional device cannot offer scsi,
>>> doesn't it?
>>>
>>> We have two layers interacting here: virtio-blk which may or may not
>>> offer scsi support, and the transport layer which may or may not offer
>>> VERSION_1 support. Failing scsi commands if VERSION_1 has been
>>> negotiated makes sense to me; but I don't want to disable scsi config a
>>> priori because the driver might negotiate VERSION_1. This would imply
>>> that virtio-blk over virtio-ccw would never offer scsi once we enable
>>> virtio-1 support, and it kind of defeats the purpose of a transitional
>>> device for me.
>>>
>>> (The other way round - fail negotiating revison 1 if the device was
>>> configured with scsi support - makes more sense to me.)
>>
>> For newer machine types, it would make sense to block VIRTIO_BLK_F_SCSI
>> altogether if !blk->conf.scsi. Would that fix the problem for you too?
>
> This is probably a sensible approach, and it can be contained in
> virtio-block, no?
Yes, I think so.
Paolo
next prev parent reply other threads:[~2015-07-13 15:13 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 5:46 [Qemu-devel] [PATCH 1/5] virtio-pci: ignore unaligned read/write in virtio_address_space_read()/write() Jason Wang
2015-07-13 5:46 ` [Qemu-devel] [PATCH 2/5] virtio-blk: disable scsi passthrough for 1.0 device Jason Wang
2015-07-13 7:46 ` Michael S. Tsirkin
2015-07-13 9:00 ` Jason Wang
2015-07-13 9:56 ` Kevin Wolf
2015-07-13 11:51 ` Cornelia Huck
2015-07-13 12:22 ` Michael S. Tsirkin
2015-07-13 12:30 ` Cornelia Huck
2015-07-13 12:36 ` Michael S. Tsirkin
2015-07-13 13:20 ` Cornelia Huck
2015-07-13 14:34 ` Paolo Bonzini
2015-07-13 14:41 ` Cornelia Huck
2015-07-13 15:13 ` Paolo Bonzini [this message]
2015-07-13 15:35 ` Michael S. Tsirkin
2015-07-14 17:43 ` Cornelia Huck
2015-07-15 10:59 ` Michael S. Tsirkin
2015-07-15 11:46 ` Cornelia Huck
2015-07-15 12:01 ` Michael S. Tsirkin
2015-07-15 12:43 ` Cornelia Huck
2015-07-15 13:16 ` Michael S. Tsirkin
2015-07-15 13:40 ` Cornelia Huck
2015-07-15 14:11 ` Michael S. Tsirkin
2015-07-15 14:30 ` Cornelia Huck
2015-07-15 14:39 ` Michael S. Tsirkin
2015-07-15 15:38 ` Cornelia Huck
2015-07-15 18:51 ` Michael S. Tsirkin
2015-07-16 12:37 ` Cornelia Huck
2015-07-16 12:47 ` Michael S. Tsirkin
2015-07-16 17:22 ` Paolo Bonzini
2015-07-17 7:18 ` Cornelia Huck
2015-07-13 11:27 ` Michael S. Tsirkin
2015-07-13 5:46 ` [Qemu-devel] [PATCH 3/5] virtio-blk: set VIRTIO_F_ANY_LAYOUT when 1.0 is supported Jason Wang
2015-07-13 5:46 ` [Qemu-devel] [PATCH 4/5] Revert "virtio-net: enable virtio 1.0" Jason Wang
2015-07-13 6:16 ` Cornelia Huck
2015-07-13 7:22 ` Michael S. Tsirkin
2015-07-13 8:46 ` Cornelia Huck
2015-07-13 8:29 ` Jason Wang
2015-07-13 5:46 ` [Qemu-devel] [PATCH 5/5] virtio-net: unbreak any layout Jason Wang
2015-07-13 6:50 ` Paolo Bonzini
2015-07-13 8:30 ` Jason Wang
2015-07-13 7:24 ` Michael S. Tsirkin
2015-07-13 8:22 ` Michael S. Tsirkin
2015-07-13 10:54 ` Greg Kurz
2015-07-13 11:13 ` Michael S. Tsirkin
2015-07-13 8:30 ` Jason Wang
2015-07-13 7:36 ` [Qemu-devel] [PATCH 1/5] virtio-pci: ignore unaligned read/write in virtio_address_space_read()/write() Michael S. Tsirkin
2015-07-13 7:53 ` Gerd Hoffmann
2015-07-13 8:00 ` Michael S. Tsirkin
2015-07-13 8:39 ` Gerd Hoffmann
2015-07-13 8:37 ` 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=55A3D596.9060401@redhat.com \
--to=pbonzini@redhat.com \
--cc=cornelia.huck@de.ibm.com \
--cc=jasowang@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--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 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).