From: jgross@suse.com
To: xen-devel@lists.xen.org, linux-scsi@vger.kernel.org,
target-devel@vger.kernel.org, JBottomley@parallels.com,
konrad.wilk@oracle.com, hch@infradead.org,
david.vrabel@citrix.com
Subject: [PATCH V3 0/4] Add XEN pvSCSI support
Date: Mon, 4 Aug 2014 10:27:46 +0200 [thread overview]
Message-ID: <1407140870-542-1-git-send-email-jgross@suse.com> (raw)
This series adds XEN pvSCSI support. With pvSCSI it is possible to use physical
SCSI devices from a XEN domain.
The support consists of a backend in the privileged Domain-0 doing the real
I/O and a frontend in the unprivileged domU passing I/O-requests to the backend.
The code is taken (and adapted) from the original pvSCSI implementation done
for Linux 2.6 in 2008 by Fujitsu.
[PATCH V2 1/4] Add XEN pvSCSI protocol description
[PATCH V2 2/4] Introduce xen-scsifront module
[PATCH V2 3/4] Introduce XEN scsiback module
[PATCH V2 4/4] add xen pvscsi maintainer
Changes in V3:
- added some comments to the protocol header file
- removed the CDB emulation from xen-scsiback, handled by core target
infrastructure
- several changes in xen-scsifront after comments from Christoph Hellwig
Changes in V2:
- use core target infrastructure by backend instead of pure SCSI passthrough
- add support for larger SG lists by putting them in grant page(s)
- add command abort capability
next reply other threads:[~2014-08-04 8:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 8:27 jgross [this message]
2014-08-04 8:27 ` [PATCH V3 1/4] Add XEN pvSCSI protocol description jgross
2014-08-04 10:10 ` [Xen-devel] " Jan Beulich
2014-08-04 10:39 ` Juergen Gross
2014-08-04 8:27 ` [PATCH V3 2/4] Introduce xen-scsifront module jgross
2014-08-04 12:16 ` David Vrabel
2014-08-04 8:27 ` [PATCH V3 3/4] Introduce XEN scsiback module jgross
2014-08-04 12:18 ` David Vrabel
2014-08-04 8:27 ` [PATCH V3 4/4] add xen pvscsi maintainer jgross
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=1407140870-542-1-git-send-email-jgross@suse.com \
--to=jgross@suse.com \
--cc=JBottomley@parallels.com \
--cc=david.vrabel@citrix.com \
--cc=hch@infradead.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=target-devel@vger.kernel.org \
--cc=xen-devel@lists.xen.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).