From: George Dunlap <george.dunlap@citrix.com>
To: xen-devel@lists.xen.org
Cc: George Dunlap <george.dunlap@citrix.com>
Subject: [PATCH v3 0/9] tools: Allow HVM domains emulated access to disks provided by hotplug scripts
Date: Thu, 24 Mar 2016 17:22:31 +0000 [thread overview]
Message-ID: <1458840160-26733-1-git-send-email-george.dunlap@citrix.com> (raw)
In order for HVM domains to provide emulated access to disks provided
by hotplug scripts, qemu needs access to a "cooked" version of the
disk. In the case of hotplug scripts, this "cooked" version is
available in the form of a block device passed to blkback. Make this
"cooked" version available to qemu.
This series also starts to work towards a rationalized interface to
the block hotplug scripts, on which hotplug scripts for FreeBSD can be
added.
git://xenbits.xenproject.org/people/gdunlap/xen.git out/hotplug-script-improvements/v3
Changes in v3:
- Fix stray comma
- Make it clear that block-script.txt inputs are Linux-specific
Changes since v1:
- Split one of the patches into two
George Dunlap (8):
tools/hotplug: Add a "dummy" hotplug script for testing
libxl: Remove redundant setting of phyical-device
tools/hotplug: Write physical-device-path in addition to
physical-device
libxl: Move check for local access to a funciton
libxl: Rearrange qemu upstream disk argument code
libxl: Share logic for finding path between qemuu and pygrub
libxl: Allow local access for block devices with hotplug scripts
docs: Document block-script protocol
Ian Jackson (1):
DO NOT APPLY libxl: Change hotplug script interface to use
physical-device-path
docs/misc/block-scripts.txt | 96 +++++++++++++++++++++++++++
tools/hotplug/Linux/Makefile | 1 +
tools/hotplug/Linux/block-common.sh | 16 ++---
tools/hotplug/Linux/block-dummy | 107 ++++++++++++++++++++++++++++++
tools/libxl/libxl.c | 128 ++++++++++++++++++++++++++----------
tools/libxl/libxl_dm.c | 82 +++++++++++++++--------
tools/libxl/libxl_internal.h | 11 +++-
tools/libxl/libxl_linux.c | 70 +++++++++++++++++++-
8 files changed, 433 insertions(+), 78 deletions(-)
create mode 100644 docs/misc/block-scripts.txt
create mode 100644 tools/hotplug/Linux/block-dummy
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2016-03-24 17:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 17:22 George Dunlap [this message]
2016-03-24 17:22 ` [PATCH v3 1/9] tools/hotplug: Add a "dummy" hotplug script for testing George Dunlap
2016-03-24 17:22 ` [PATCH v3 2/9] libxl: Remove redundant setting of phyical-device George Dunlap
2016-03-24 17:22 ` [PATCH v3 3/9] tools/hotplug: Write physical-device-path in addition to physical-device George Dunlap
2016-04-01 14:15 ` Ian Jackson
2016-03-24 17:22 ` [PATCH v3 4/9] libxl: Move check for local access to a funciton George Dunlap
2016-04-01 14:16 ` Ian Jackson
2016-03-24 17:22 ` [PATCH v3 5/9] libxl: Rearrange qemu upstream disk argument code George Dunlap
2016-04-01 14:18 ` Ian Jackson
2016-04-01 14:31 ` Ian Jackson
2016-04-04 15:11 ` George Dunlap
2016-04-04 16:59 ` Ian Jackson
2016-04-04 17:11 ` Andrew Cooper
2016-04-04 17:16 ` Andrew Cooper
2016-04-05 9:28 ` George Dunlap
2016-03-24 17:22 ` [PATCH v3 6/9] libxl: Share logic for finding path between qemuu and pygrub George Dunlap
2016-04-01 14:19 ` Ian Jackson
2016-03-24 17:22 ` [PATCH v3 7/9] libxl: Allow local access for block devices with hotplug scripts George Dunlap
2016-04-01 14:20 ` Ian Jackson
2016-03-24 17:22 ` [PATCH v3 8/9] docs: Document block-script protocol George Dunlap
2016-04-01 14:20 ` Ian Jackson
2016-03-24 17:22 ` [PATCH v3 9/9] DO NOT APPLY libxl: Change hotplug script interface to use physical-device-path George Dunlap
2016-04-01 14:36 ` [PATCH v3 0/9] tools: Allow HVM domains emulated access to disks provided by hotplug scripts Ian Jackson
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=1458840160-26733-1-git-send-email-george.dunlap@citrix.com \
--to=george.dunlap@citrix.com \
--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).