xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@citrix.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
	Ian Jackson <ian.jackson@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH v2 0/9] tools: Allow HVM domains emulated access to disks provided by hotplug scripts
Date: Wed, 23 Mar 2016 10:36:27 +0000	[thread overview]
Message-ID: <56F271AB.2050901@citrix.com> (raw)
In-Reply-To: <alpine.OSX.2.20.1603231107450.753@mac>

On 23/03/16 10:10, Roger Pau Monné wrote:
> On Mon, 21 Mar 2016, George Dunlap wrote:
> 
>> 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.
>>
>> 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
> 
> Hello,
> 
> Is this available in some git repo? It would be easier for me to rebase my 
> FreeBSD hotplug series on top of it, but if not I can pick the patches 
> myself from the mailing list.

I've pushed it here:

git://xenbits.xenproject.org/people/gdunlap/xen.git
out/hotplug-script-improvements/v2

NB this has the fix to patch 6 as well.

 -George

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2016-03-23 10:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21 18:16 [PATCH v2 0/9] tools: Allow HVM domains emulated access to disks provided by hotplug scripts George Dunlap
2016-03-21 18:16 ` [PATCH v2 1/9] tools/hotplug: Add a "dummy" hotplug script for testing George Dunlap
2016-03-21 18:16 ` [PATCH v2 2/9] libxl: Remove redundant setting of phyical-device George Dunlap
2016-03-21 18:16 ` [PATCH v2 3/9] tools/hotplug: Write physical-device-path in addition to physical-device George Dunlap
2016-03-21 18:16 ` [PATCH v2 4/9] libxl: Move check for local access to a funciton George Dunlap
2016-03-21 18:16 ` [PATCH v2 5/9] libxl: Rearrange qemu upstream disk argument code George Dunlap
2016-03-21 18:16 ` [PATCH v2 6/9] libxl: Share logic for finding path between qemuu and pygrub George Dunlap
2016-03-22 10:38   ` George Dunlap
2016-03-21 18:16 ` [PATCH v2 7/9] libxl: Allow local access for block devices with hotplug scripts George Dunlap
2016-03-21 18:17 ` [PATCH v2 8/9] docs: Document block-script protocol George Dunlap
2016-03-22 12:52   ` Roger Pau Monné
2016-03-23 11:19     ` George Dunlap
2016-03-23 12:14       ` Roger Pau Monné
2016-03-24 16:29         ` George Dunlap
2016-03-24 16:51           ` Roger Pau Monné
2016-03-21 18:17 ` [PATCH v2 9/9] DO NOT APPLY libxl: Change hotplug script interface to use physical-device-path George Dunlap
2016-03-23 10:10 ` [PATCH v2 0/9] tools: Allow HVM domains emulated access to disks provided by hotplug scripts Roger Pau Monné
2016-03-23 10:36   ` George Dunlap [this message]

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=56F271AB.2050901@citrix.com \
    --to=george.dunlap@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=ian.jackson@citrix.com \
    --cc=roger.pau@citrix.com \
    --cc=wei.liu2@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).