From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: Re: [PATCH 1/2] virtio-scsi: first version
Date: Sun, 04 Dec 2011 09:22:49 +1100 [thread overview]
Message-ID: <1322950969.11728.24.camel@pasglop> (raw)
In-Reply-To: <4EDA5E7F.30508@redhat.com>
On Sat, 2011-12-03 at 18:38 +0100, Paolo Bonzini wrote:
> On 12/03/2011 12:07 AM, Benjamin Herrenschmidt wrote:
> > This is typically the one thing you should -really- obtain from the
> > other side. This is the number one reason why we cannot today reliably
> > emulate a SCSI controller in qemu -and- pass-through the SCSI commands
> > to the host /dev/sg or equivalent (only full device emulation is
> > reliable).
> >
> > This is also typically what something like virtio-scsi allows us to fix,
> > so let's fix it. IE. we have the ability to query the "limits" of the
> > real HBA / transport on the host side and to pass them along to the
> > guest, which enables us to do real pass-through.
>
> You can fix this in QEMU; READ and WRITE commands can be split in
> multiple parts. The scsi-block device I added recently does this.
You can split -some- commands... it's clumsy and not always legit, you
don't always know all commands (what about vendor commands such as
firmware updates etc...) and it can be really tricky with tagged queues
and barriers.
> However, it seems like a simple change, so I'll do it. I'll add
> max_sectors and cmd_per_lun to the config space.
Sounds like a good start :-)
Cheers,
Ben.
next prev parent reply other threads:[~2011-12-03 22:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 13:54 [PATCH 0/2] virtio-scsi driver Paolo Bonzini
2011-11-30 13:54 ` [PATCH 1/2] virtio-scsi: first version Paolo Bonzini
2011-12-01 6:33 ` Sasha Levin
2011-12-01 8:36 ` Paolo Bonzini
2011-12-01 8:55 ` Sasha Levin
2011-12-02 0:29 ` Rusty Russell
2011-12-02 23:07 ` Benjamin Herrenschmidt
2011-12-03 17:38 ` Paolo Bonzini
2011-12-03 22:22 ` Benjamin Herrenschmidt [this message]
2011-12-05 10:08 ` Paolo Bonzini
2011-11-30 13:54 ` [PATCH 2/2] virtio-scsi: add error handling Paolo Bonzini
-- strict thread matches above, loose matches on Subject: below --
2011-12-05 17:29 [PATCH v2 0/2] virtio-scsi driver Paolo Bonzini
2011-12-05 17:29 ` [PATCH 1/2] virtio-scsi: first version Paolo Bonzini
2011-12-06 18:09 ` James Bottomley
2011-12-07 9:41 ` Paolo Bonzini
2011-12-07 14:35 ` James Bottomley
2011-12-08 13:09 ` Paolo Bonzini
2011-12-09 20:06 ` James Bottomley
2011-12-10 16:37 ` Paolo Bonzini
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=1322950969.11728.24.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=stefanha@linux.vnet.ibm.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