[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] @introduceDomain with xenbus?


  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: NAHieu <nahieu@xxxxxxxxx>
  • Date: Thu, 6 Oct 2005 22:34:39 +0900
  • Delivery-date: Thu, 06 Oct 2005 13:32:09 +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:mime-version:content-type:content-transfer-encoding:content-disposition; b=lC3wnFD4VxN/X1Ckisf58Primq7FToVJBu4LWO2ACumnAOJRKRm/YzceyE/8Tln0mSSwngzdyfDAPnfSyPMVw2oBraeHqbU/OrZrvsSCbWFmC6+PcA3I/F+rOE3oJ4bGm/bRR+rnjAQTR04i1qpGh0ryIG8Xz6lThdJ3NE7toPw=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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?

Many Thanks.
Hieu

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.