From: Paolo Bonzini <pbonzini@redhat.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
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: Mon, 05 Dec 2011 11:08:54 +0100 [thread overview]
Message-ID: <4EDC9836.2000508@redhat.com> (raw)
In-Reply-To: <1322950969.11728.24.camel@pasglop>
On 12/03/2011 11:22 PM, Benjamin Herrenschmidt wrote:
>> > 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...)
For the record, firmware updates won't run under virt unless you make
qemu runs with CAP_SYS_RAWIO.
Paolo
next prev parent reply other threads:[~2011-12-05 10:09 UTC|newest]
Thread overview: 19+ 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
2011-12-05 10:08 ` Paolo Bonzini [this message]
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
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=4EDC9836.2000508@redhat.com \
--to=pbonzini@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@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 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.