All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Cc: Paul Brook <paul@codesourcery.com>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] new scsi-generic abstraction, use SG_IO
Date: Sat, 28 Mar 2009 12:30:51 -0500	[thread overview]
Message-ID: <49CE5ECB.1040905@us.ibm.com> (raw)
In-Reply-To: <20090318133633.GA24254@lst.de>

Christoph Hellwig wrote:
> Okay, I started looking into how to handle scsi-generic I/O in the
> new world order.
>
> I think the best is to use the SG_IO ioctl instead of the read/write
> interface as that allows us to support scsi passthrough on disk/cdrom
> devices, too.  See Hannes patch on the kvm list from August for an
> example.
>
> Now that we always do ioctls we don't need another abstraction than
> bdrv_ioctl for the synchronous requests for now, and for asynchronous
> requests I've added a aio_ioctl abstraction keeping it simple.
>
> Long-term we might want to move the ops to a higher-level abstraction
> and let the low-level code fill out the request header, but I'm lazy
> enough to leave that to the people trying to support scsi-passthrough
> on a non-Linux OS.
>
> Tested lightly by issuing various sg_ commands from sg3-utils in a guest
> to a host CDROM device.
>
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
>   

Applied.  Thanks.

Regards,

Anthony Liguori

      parent reply	other threads:[~2009-03-28 17:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18 13:36 [Qemu-devel] [PATCH] new scsi-generic abstraction, use SG_IO Christoph Hellwig
2009-03-18 13:46 ` [Qemu-devel] " Avi Kivity
2009-03-18 13:52   ` Christoph Hellwig
2009-03-28 17:30 ` Anthony Liguori [this message]

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=49CE5ECB.1040905@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=paul@codesourcery.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.