qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Hannes Reinecke <hare@suse.de>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Christoph Hellwig <hch@lst.de>,
	kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] virtio-blk: add SGI_IO passthru support
Date: Tue, 28 Apr 2009 18:52:13 +0200	[thread overview]
Message-ID: <200904281852.13916.borntraeger@de.ibm.com> (raw)
In-Reply-To: <49F730AD.8090705@codemonkey.ws>

Am Tuesday 28 April 2009 18:37:01 schrieb Anthony Liguori:
> Christoph Hellwig wrote:
> >> Should we be 
> >> handling some SCSI cmds internally to QEMU (like eject operations) and 
> >> supporting media=cdrom in -drive for if=virtio?
> >>     
> >
> > Not quite yet.  Eventually I want to support a virtio-scsi kind of
> > transport which would use the same virtio-blk protocol but only send
> > scsi commands.  We'd need a different driver on the Linux side for
> > it that registers to the scsi layer.  On the QEMU side it could either
> > do pass-through to a real scsi device using SG_IO or use the existing
> > command scsi emulator in scsi-disk.c.
> >   
> 
> Ah, excellent.  I think that's a great thing to do.  So do you think 
> virtio-scsi would deprecate virtio-blk?

There are lots of other block device drivers with strange characteristics. 
For example dasd/xpram disks with 4k block size or other disks with strange partitioning schemes. Doing a scsi emulation on top of these beasts looks possible but far from ideal. So I guess we will need virtio_blk for non-scsi block devices.

Christian

  reply	other threads:[~2009-04-28 16:52 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090427082606.GA32604@lst.de>
2009-04-27  8:29 ` [Qemu-devel] [PATCH] virtio-blk: add SGI_IO passthru support Christoph Hellwig
2009-04-27  9:15   ` Avi Kivity
2009-04-28  9:47     ` Christoph Hellwig
2009-04-27 14:36   ` [Qemu-devel] " Anthony Liguori
2009-04-28  9:51     ` Christoph Hellwig
2009-04-28 16:37       ` Anthony Liguori
2009-04-28 16:52         ` Christian Borntraeger [this message]
2009-04-29 10:48         ` Christoph Hellwig
2009-04-29 11:11           ` Paul Brook
2009-04-29 11:19             ` Christian Borntraeger
2009-04-29 11:29               ` Paul Brook
2009-04-29 11:21             ` Christoph Hellwig
2009-04-29 11:37               ` Paul Brook
2009-04-30 20:13                 ` Christoph Hellwig
2009-04-30 20:55                   ` Nicholas A. Bellinger
2009-04-30 21:49                   ` Paul Brook
2009-04-30 21:56                     ` Javier Guerra
2009-05-01  7:24                     ` Christoph Hellwig
2009-05-01 11:08                       ` Jamie Lokier
2009-05-01 14:28                         ` Christoph Hellwig
2009-05-05  5:21                   ` Rusty Russell
2009-04-28 19:09       ` Christian Borntraeger
2009-04-29 10:50         ` Christoph Hellwig
2009-04-29 11:07           ` Christian Borntraeger
2009-04-28  9:57   ` [Qemu-devel] [PATCH 2/2] virtio-blk: add SG_IO " Christoph Hellwig

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=200904281852.13916.borntraeger@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=anthony@codemonkey.ws \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rusty@rustcorp.com.au \
    /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).