From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Gerd Hoffmann <kraxel@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: kvm-devel <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>,
Nicholas Bellinger <nab@linux-iscsi.org>,
Hannes Reinecke <hare@suse.de>, Christoph Hellwig <hch@lst.de>,
Paul Brook <paul@codesourcery.com>
Subject: [Qemu-devel] [PATCH 0/5] *** SUBJECT HERE ***
Date: Mon, 14 Jun 2010 02:44:04 -0700 [thread overview]
Message-ID: <1276508644-3005-1-git-send-email-nab@linux-iscsi.org> (raw)
From: Nicholas Bellinger <nab@linux-iscsi.org>
Greetings Gerd, Hannes and co,
This series adds initial support for a hw/scsi-bsg.c backstore for scsi-bus
compatible HBA emulation in QEMU-KVM on Linux hosts supporting the BSG driver.
This code is available from the scsi-bsg branch in the megasas/scsi friendly QEMU-KVM tree at:
http://git.kernel.org/?p=virt/kvm/nab/qemu-kvm.git;a=shortlog;h=refs/heads/scsi-bsg
Note that this initial code is being posted for review and to see how useful a BSG backstore
would be for QEMU-KVM and Linux hosts. Note that in order for BSG I/O to function using vectored
AIO a kernel patch to linux/block/bsg.c:bsg_map_hdr() is currently required running on a bit paired
user/kernel enviroment. The kernel patch in question is here:
http://marc.info/?l=linux-scsi&m=127649585524598&w=2
The first three patches involve updating block code to support the BSG backstore for scsi-bsg.
The forth patch adds the minor changes to hw/scsi-bus.c and hw/scsi-disk.c in order to
function with scsi-bsg.
And the fifth patch adds the main hw/scsi-bsg.c logic necessary to run the new struct
SCSIDeviceInfo and for BSG AIO using struct iovec and paio_submit_len() to function.
So far this patch series has been tested with a Linux based x86_64 KVM host and guest
using the hw/megasas.c 8708EM2 HBA Emulation with TCM_Loop virtual SAS Port LUNs.
Comments are welcome,
Signed-off-by: Nicholas A. Bellinger <nab@linux-iscsi.org>
Nicholas Bellinger (5):
[block]: Add top level BSG support
[block]: Add BSG qemu_open() in block/raw.c:raw_open()
[block]: Add paio_submit_len() non sector sized AIO
[scsi]: Add BSG support for scsi-bus and scsi-disk
[scsi-bsg]: Add initial support for BSG based SCSIDeviceInfo
Makefile.objs | 2 +-
block.c | 23 ++-
block.h | 1 +
block/raw-posix-aio.h | 3 +
block/raw-posix.c | 17 ++-
block/raw.c | 20 ++
block_int.h | 5 +
hw/scsi-bsg.c | 588 +++++++++++++++++++++++++++++++++++++++++++++++++
hw/scsi-bus.c | 3 +-
hw/scsi-disk.c | 4 +
posix-aio-compat.c | 28 +++
11 files changed, 687 insertions(+), 7 deletions(-)
create mode 100644 hw/scsi-bsg.c
next reply other threads:[~2010-06-14 9:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 9:44 Nicholas A. Bellinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-03-26 19:02 [Qemu-devel] [PATCH 00/10] Today's compilation fixes Blue Swirl
2010-03-31 16:23 ` [Qemu-devel] [PATCH 0/5] *** SUBJECT HERE *** 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=1276508644-3005-1-git-send-email-nab@linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@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 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).