From: "Nicholas A. Bellinger" <nab@daterainc.com>
To: target-devel <target-devel@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Nicholas Bellinger <nab@linux-iscsi.org>,
kvm-devel <kvm@vger.kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: [Qemu-devel] [PATCH 0/3] vhost/scsi: Enable virtio 1.0 host_feature bits
Date: Fri, 30 Jan 2015 08:35:47 +0000 [thread overview]
Message-ID: <1422606950-25291-1-git-send-email-nab@daterainc.com> (raw)
From: Nicholas Bellinger <nab@linux-iscsi.org>
Hi MST & Paolo,
Here are the associated QEMU vhost/scsi changes to enable KVM host
for expose F_HOTPLUG, F_T10_PI, and ANY_LAYOUT feature bits into
virtio 1.0 compatible guests.
Note this does not include VIRTIO_SCSI_F_CHANGE, which is currently
not supported by vhost/scsi kernel code host_feature bits.
Thank you,
--nab
Nicholas Bellinger (3):
vhost/scsi: Add VIRTIO_SCSI_F_HOTPLUG host_feature bit
vhost/scsi: Add VIRTIO_SCSI_F_T10_PI host_feature bit
vhost/scsi: Add VIRTIO_F_ANY_LAYOUT host_feature bit
hw/scsi/vhost-scsi.c | 2 ++
hw/scsi/virtio-scsi.c | 3 +++
hw/virtio/virtio-pci.c | 6 ++++++
include/hw/i386/pc.h | 18 +++++++++++++++++-
include/hw/virtio/virtio-scsi.h | 5 ++++-
5 files changed, 32 insertions(+), 2 deletions(-)
--
1.9.1
next reply other threads:[~2015-01-30 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 8:35 Nicholas A. Bellinger [this message]
2015-01-30 8:35 ` [Qemu-devel] [PATCH 1/3] vhost/scsi: Add VIRTIO_SCSI_F_HOTPLUG host_feature bit Nicholas A. Bellinger
2015-01-30 8:35 ` [Qemu-devel] [PATCH 2/3] vhost/scsi: Add VIRTIO_SCSI_F_T10_PI " Nicholas A. Bellinger
2015-01-30 8:35 ` [Qemu-devel] [PATCH 3/3] vhost/scsi: Add VIRTIO_F_ANY_LAYOUT " Nicholas A. Bellinger
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=1422606950-25291-1-git-send-email-nab@daterainc.com \
--to=nab@daterainc.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=nab@linux-iscsi.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=target-devel@vger.kernel.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 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).