qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: kwolf@redhat.com, qemu-block@nongnu.org, mst@redhat.com,
	jasowang@redhat.com, qemu-devel@nongnu.org, agraf@suse.de,
	stefanha@redhat.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 3/3] virtio-blk: switch off scsi-passthrough by default
Date: Fri, 16 Oct 2015 13:07:28 +0200	[thread overview]
Message-ID: <5620DA70.1050702@de.ibm.com> (raw)
In-Reply-To: <20151016124403.2fa55ceb.cornelia.huck@de.ibm.com>

Am 16.10.2015 um 12:44 schrieb Cornelia Huck:
> On Fri, 16 Oct 2015 12:32:52 +0200
> Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> 
>> Am 16.10.2015 um 12:25 schrieb Cornelia Huck:
>>> Devices that are compliant with virtio-1 do not support scsi
>>> passthrough any more (and it has not been a recommended setup
>>> anyway for quite some time). To avoid having to switch it off
>>> explicitly in newer qemus that turn on virtio-1 by default, let's
>>> switch the default to scsi=false for 2.5.
>>>
>>> Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
>>> ---
>>>  hw/block/virtio-blk.c | 2 +-
>>>  include/hw/compat.h   | 6 +++++-
>>>  2 files changed, 6 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/hw/block/virtio-blk.c b/hw/block/virtio-blk.c
>>> index 8beb26b..999dbd7 100644
>>> --- a/hw/block/virtio-blk.c
>>> +++ b/hw/block/virtio-blk.c
>>> @@ -975,7 +975,7 @@ static Property virtio_blk_properties[] = {
>>>      DEFINE_PROP_STRING("serial", VirtIOBlock, conf.serial),
>>>      DEFINE_PROP_BIT("config-wce", VirtIOBlock, conf.config_wce, 0, true),
>>>  #ifdef __linux__
>>> -    DEFINE_PROP_BIT("scsi", VirtIOBlock, conf.scsi, 0, true),
>>> +    DEFINE_PROP_BIT("scsi", VirtIOBlock, conf.scsi, 0, false),
>>>  #endif
>>>      DEFINE_PROP_BIT("request-merging", VirtIOBlock, conf.request_merging, 0,
>>>                      true),
>>> diff --git a/include/hw/compat.h b/include/hw/compat.h
>>> index 095de5d..93e71af 100644
>>> --- a/include/hw/compat.h
>>> +++ b/include/hw/compat.h
>>> @@ -2,7 +2,11 @@
>>>  #define HW_COMPAT_H
>>>
>>>  #define HW_COMPAT_2_4 \
>>> -        /* empty */
>>> +        {\
>>> +            .driver   = "virtio-blk-device",\
>>> +            .property = "scsi",\
>>> +            .value    = "true",\
>>
>> does that work?
> 
> It did for me :)
> 
>>
>> If yes, would it make sense to convert the things in HW_COMPAT_2_3 from
>> pci to device, e.g.
>>
>>
>>         {\
>> -           .driver   = "virtio-blk-pci",\
>> +           .driver   = "virtio-blk-device",\
>>             .property = "any_layout",\
>>             .value    = "off",\
>> ...
> 
> Not sure: We don't have 2.3 compat for ccw... but would give a better
> template for later changes.

Yes. But this can be an addon patch. 

Lets keep this patch as is to have scsi=off as default for virtio 1.0

(some iotests do fail because of this)

Christian

  reply	other threads:[~2015-10-16 11:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16 10:25 [Qemu-devel] [PATCH v2 0/3] virtio-blk: no scsi-passthrough by default Cornelia Huck
2015-10-16 10:25 ` [Qemu-devel] [PATCH v2 1/3] s390x: include HW_COMPAT_* props Cornelia Huck
2015-10-16 10:30   ` Christian Borntraeger
2015-10-16 10:25 ` [Qemu-devel] [PATCH v2 2/3] ppc/spapr: add 2.4 compat props Cornelia Huck
2015-10-16 10:25 ` [Qemu-devel] [PATCH v2 3/3] virtio-blk: switch off scsi-passthrough by default Cornelia Huck
2015-10-16 10:32   ` Christian Borntraeger
2015-10-16 10:44     ` Cornelia Huck
2015-10-16 11:07       ` Christian Borntraeger [this message]
2015-10-18  7:59         ` Michael S. Tsirkin
2015-10-19 11:53           ` Cornelia Huck
2015-10-19 11:57             ` Michael S. Tsirkin
2015-10-19 12:21               ` Cornelia Huck
2015-10-16 12:40 ` [Qemu-devel] [PATCH v2 0/3] virtio-blk: no " Paolo Bonzini
2015-10-21 10:12 ` Stefan Hajnoczi

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=5620DA70.1050702@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=agraf@suse.de \
    --cc=cornelia.huck@de.ibm.com \
    --cc=jasowang@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@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).