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

Re: [Xen-devel] [PATCH] Add an ioctl interface for simple xenstore acces

To: Gerd Hoffmann <kraxel@xxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Add an ioctl interface for simple xenstore access
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Mon, 20 Mar 2006 08:52:05 +0000
Cc: Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>, Dan Smith <danms@xxxxxxxxxx>
Delivery-date: Mon, 20 Mar 2006 08:53:20 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <441E69FE.7070307@xxxxxxx>
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: <87r750pupr.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxx> <20060318071405.GD23816@xxxxxxxxxxxxxxxxxxx> <01789afa761fc8e2b1f398148de7370c@xxxxxxxxxxxx> <441C4B20.4000202@xxxxxxxxxx> <441E69FE.7070307@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Mon, Mar 20, 2006 at 09:38:22AM +0100, Gerd Hoffmann wrote:

> > We had discussed this in a previous thread and I thought you were okay
> > with this approach.  The /proc/xen/xenbus interface requires full
> > parsing of the XenBus protocol.  This requires libxenstore in domU. 
> > Today, libxenstore is shipped with the rest of the tools package on most
> > distros.  
> 
> Changing this and move libxenstore to another package (to avoid pulling
> in xend with python if everything you want is xenstore access) isn't a
> big problem ...
> 
> btw: are xenstore watches supposed to work inside domU?

Watches work in kernel space in domU (the frontends to the split device
drivers use them), but they don't work in userspace there.  The problem is
that there is no support in xenbus for blocking a userspace process waiting
for a watch to fire.

In domain 0, Xend uses a unix domain socket straight to Xenstored: it can
block on that, as it's not going through the Xenbus kernel-level driver.

If someone wanted to add such support, that would be appreciated.

Ewan.

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