Re: [Xen-devel] [PATCH v2 2/7] libxl: add new hotplug interface support to hotplug script callers

[Roger Pau Monné <roger.pau@xxxxxxxxxx>]

On 11/04/13 18:33, Ian Jackson wrote:
> Roger Pau Monne writes ("[Xen-devel] [PATCH v2 2/7] libxl: add new hotplug 
> interface support to hotplug script callers"):
>> +This document specifies the new libxl hotplug interface. This new
>> +interface has been designed to operate better with complex hotplug
>> +scripts, that need to perform several operations and can take a
>> +considerable time to execute.
>> +
>> +Hotplug scripts are expected to take a parameter, passed by the caller
>> +and provide a block device as output, that will be attached to the guest.
> 
>> +PREPARE
>> +-------
>> +
>> +This is the first operation that the hotplug script will be requested to
>> +execute. This operation is executed before the disk is connected, to
>> +give the hotplug script the chance to offload some work from the "add"
>> +operation, that is performed later.
> 
> But in fact in your implementation this is only called right before
> add, isn't it ?

It depends on the caller, for example if using libxl_device_disk_add,
libxl will take care of calling prepare before add (so external API is
not changed), on the other hand, when creating a new domain, the prepare
functions will be called much before calling add, so we can prepare the
device before the domain is paused when doing migration. If you take a
look at patch 3/7, you will see that on domain create disks are prepared
at initiate_domain_create.

> 
> Also, IIRC part of the point of this new interface is that for target
> devices which can't be accessed simultaneously from different hosts,
> during migration you'd be able to do costly setup during the initial
> part of the migration and merely "activate" the devices later.

Yes, that's right, prepare will be called while the domain is still
running on the sender side, so we can offload as much work as possible
to this phase.

> Am I missing something ?
> 
> Thanks,
> Ian.
> 


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