linux-kernel - Re: [PATCH v4 0/3] virtio-scsi driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAOJsxLHwT0o=mS2nCSxjtwdfOif7oZkT_ZED3UOybFACVG6WvQ@mail.gmail.com>
Date:	Wed, 1 Feb 2012 09:31:12 +0200
From:	Pekka Enberg <penberg@...nel.org>
To:	Paolo Bonzini <pbonzini@...hat.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-scsi <linux-scsi@...r.kernel.org>,
	"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Sasha Levin <levinsasha928@...il.com>
Subject: Re: [PATCH v4 0/3] virtio-scsi driver

Hello Paolo,

On Mon, Jan 30, 2012 at 10:48 AM, Paolo Bonzini <pbonzini@...hat.com> wrote:
> On 01/20/2012 05:45 PM, Paolo Bonzini wrote:
>>
>> This is the first implementation of the virtio-scsi driver, a virtual
>> HBA that will be supported by KVM.  It implements a subset of the spec,
>> in particular it does not implement asynchronous notifications for either
>> LUN reset/removal/addition or CD-ROM media events, but it is already
>> functional and usable.
>>
>> Other matching bits:
>>
>> - spec at http://people.redhat.com/pbonzini/virtio-spec.pdf
>>
>> - QEMU implementation at git://github.com/bonzini/qemu.git,
>>   branch virtio-scsi
>>
>> Please review.  I would like this to be included in 3.3, since the
>> possibility of regressions is obviously zero.
>>
>> Paolo Bonzini (3):
>>   virtio-scsi: first version
>>   virtio-scsi: add error handling
>>   virtio-scsi: add power management support
>>
>> v3->v4: renamed VIRTIO_SCSI_S_UNDERRUN to VIRTIO_SCSI_S_OVERRUN;
>>     fixed 32-bit compilation; added power management support;
>>     adjusted calls to virtqueue_add_buf
>>
>>  drivers/scsi/Kconfig        |    8 +
>>  drivers/scsi/Makefile       |    1 +
>>  drivers/scsi/virtio_scsi.c  |  594
>> +++++++++++++++++++++++++++++++++++++++++++
>>  include/linux/virtio_ids.h  |    1 +
>>  include/linux/virtio_scsi.h |  114 +++++++++
>>  5 files changed, 718 insertions(+), 0 deletions(-)
>>  create mode 100644 drivers/scsi/virtio_scsi.c
>>  create mode 100644 include/linux/virtio_scsi.h
>
> Ping?

What's the benefit of virtio-scsi over virtio-blk? Are we going to
support both or eventually phase out virtio-blk?

Have the virtio specification changes been reviewed? Can we guarantee
stable ABI for the virtio-scsi driver?

                        Pekka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/