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] @introduceDomain with xenbus?

To: Anthony Liguori <aliguori@xxxxxxxxxx>
Subject: Re: [Xen-devel] @introduceDomain with xenbus?
From: NAHieu <nahieu@xxxxxxxxx>
Date: Fri, 7 Oct 2005 01:01:30 +0900
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 06 Oct 2005 15:59:00 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GvY0ZxIgrEHaEcsGUAUPtYZxlC1rjXjo0v8d0p3UjnxXvgGyBChe8MxXmtGr8eJV/YuvDG2E9pcLwGk44Ie1izUyqhyJggTAmnylKJA/NAL0WWOnYmJQLOGuiW3Np9XRvPDRtRWZUTeZVqTzoYMK5FPtjckUAt+ZFdpXWCw8n7U=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <43453EA9.70808@xxxxxxxxxx>
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: <5d7aca950510060634x3a71bed9mc75799201a0ad554@xxxxxxxxxxxxxx> <43453EA9.70808@xxxxxxxxxx>
Reply-to: NAHieu <nahieu@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 10/7/05, Anthony Liguori <aliguori@xxxxxxxxxx> wrote:
> NAHieu wrote:
>
> >Hi,
> >
> >I am writing a kernel module in dom0 to watch for @introduceDomain.
> >The callback procedure is prototyped as (registerd with
> >register_xenbus_watch()) :
> >
> >static void new_domain(struct xenbus_watch *watch, const char *node)
> >
> >In this callback, what we can get is node=="@introduceDomain"  when
> >the watch fired. Is that all we have? If I want to know which domain
> >(include domain-name and domid) caused this event, where to look for?
> >
> >
> I have a patch to extend the watches to include arbitrary data
> specifically so we can get the domain id for an
> @{introduce,release}Domain watch.
>

Great. Otherwise I must enum for the domains myself.

Thanks.
Hieu

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

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