From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: @introduceDomain with xenbus? Date: Thu, 06 Oct 2005 10:11:37 -0500 Message-ID: <43453EA9.70808@us.ibm.com> References: <5d7aca950510060634x3a71bed9mc75799201a0ad554@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5d7aca950510060634x3a71bed9mc75799201a0ad554@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: NAHieu Cc: xen-devel List-Id: xen-devel@lists.xenproject.org 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. Just waiting for some feedback on it... Regards, Anthony Liguori >Many Thanks. >Hieu > >_______________________________________________ >Xen-devel mailing list >Xen-devel@lists.xensource.com >http://lists.xensource.com/xen-devel > > >