WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: A simple XenBus Daemon prototype.

To: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: A simple XenBus Daemon prototype.
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 29 Apr 2005 11:24:25 +0100
Cc: Mike Wray <mike.wray@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 29 Apr 2005 10:26:59 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1114757521.14998.29.camel@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1114757521.14998.29.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 29 Apr 2005, at 07:52, Rusty Russell wrote:

Hi all,

        I've been working on the storage and daemon for maintaining device and
machine state for Xen.  Based somewhat loosely on designs by Mike Wray
and Anthony Liguori, as well as comments from Kier Fraser, it is now at
0.1 stage.  It's not actually useful yet, however.

Generally looking good. I have one kind of trivial comment, which is that calling it 'xenbus daemon' makes no sense. It's a registry daemon, or a store daemon, or something like that, but it sure doesn't look like a bus to me. :-)

I know there's confusion about what xenbus is actually intended to be. The way we've envisaged it in Cambridge is that it is just a convenient virtual bus abstraction within each guest OS. For example, Linux will have a xenbus driver that reads device state out of the repository (perhaps making use of a lower-level repository-access driver), and then presents the devices in sysfs and provides a neat interface for the specific drivers (blk, net, usb, whatever) to connect to the appropriate backend driver domain.

It was never our intention for the concept of a 'xenbus' to leak outside individual guest OSes and into the user-space control tools. The old xr (xen registry) naming scheme was just fine imo.

 -- Keir


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

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