This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-tools] Recent xenstore updates

To: "Rusty Russell" <rusty@xxxxxxxxxxxxxxx>, "Xen Tools" <xen-tools@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-tools] Recent xenstore updates
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Thu, 4 Aug 2005 14:09:40 +0100
Delivery-date: Thu, 04 Aug 2005 13:07:56 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-tools-request@lists.xensource.com?subject=help>
List-id: Xen control tools developers <xen-tools.lists.xensource.com>
List-post: <mailto:xen-tools@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-tools>, <mailto:xen-tools-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-tools>, <mailto:xen-tools-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-tools-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcWY8VxCxG7I54ICTlWNRgv4rbW7bQAA8zOQ
Thread-topic: [Xen-tools] Recent xenstore updates
> FYI, I just pushed the accumulated xenstore daemon updates to 
> the xen-devel list.  Some bug fixes, some cleaning, some 
> simplification, much more testing.  The only API change is 
> that watches no longer have a priority (they all fire 
> simultaneously now), but noone used that arg anyway.

The priority stuff looked like it was going to be useful to implement
simple 'work flow' e.g. when a domain dies, enable the core dump daemon
to hook in and run to completion before the domain reaper daemon, before
the reboot daemon etc

What's the story for doing the above without support for priorites? Are
we going to have to create some other convention that enables the
various dameons to serialize themselves into the right (partial)order?


Xen-tools mailing list

<Prev in Thread] Current Thread [Next in Thread>