@introduceDomain with xenbus?

@introduceDomain with xenbus?

[NAHieu]

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

Re: @introduceDomain with xenbus?

[Anthony Liguori]

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
>
>  
>

Re: @introduceDomain with xenbus?

[NAHieu]

On 10/7/05, Anthony Liguori <aliguori@us.ibm.com> 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