Xen devel - Feb 2006 - [PATCH] For detecting resume operation in hotplug scripts

Hello!

I have previously posted a patch with changes to the xenbus for being
able to detect the reason why a frontend is created, which can be either
due to domain creation or a restore. The attached patch now puts this
functionality into XenD and allows driver implementations in Xend to
read the state and see whether a domain is currently being resumed or
created and write this value into the xenstore for hotplug scripts to
read it. The state of a domain being resumed is set when a
XendDomainInfo object is created and reset at the end of the restore
function.

Please let me know about comments.

Signed-off-by: Stefan Berger <stefanb@us.ibm.com>



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

On 2 Feb 2006, at 21:34, Stefan Berger wrote:
> I have previously posted a patch with changes to the xenbus for being
> able to detect the reason why a frontend is created, which can be 
> either
> due to domain creation or a restore. The attached patch now puts this
> functionality into XenD and allows driver implementations in Xend to
> read the state and see whether a domain is currently being resumed or
> created and write this value into the xenstore for hotplug scripts to
> read it. The state of a domain being resumed is set when a
> XendDomainInfo object is created and reset at the end of the restore
> function.
>
> Please let me know about comments.
This looks much more palatable than the previous patch, thanks!

  -- Keir


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