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] how to read value from xenstore inside kernel

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] how to read value from xenstore inside kernel
From: Kuriakose Mathew <kmathew123@xxxxxxxxx>
Date: Fri, 28 Aug 2009 17:21:40 +0530
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Fri, 28 Aug 2009 04:52:02 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=LLntPu52650gL/huhkOOj79v2kzCeROij4EnJCvKWiA=; b=HX4aqHNpKcKB/qTD9VQAhxmZ8huPjAqRKzk3WDjt5Mqm4Fa0ZCGGL8i1K/ZDTlLPaP xxfoBJM5dTd19fCXr2pLrv3JajKlvjs0rsB2z2QpxyGVal6dJSLt5YPAa177iG85E5bD Xc93/PU92P6jUHqkCdEVpq+jvkOaGi+ShnCM4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Ci+nC3lONeqJFYp2u9ndAAyAyVPBvuOa/MTZR2+J7BMXt3yrrJFaUpImKKOdw1o/3s O0usjNK43A3q2Nk79iXMfH6MT0H6WPd+8juKNIiNtp+VSMY7V3RzHqkQ6Ys0vNmbpAbr 32SwNBSMFMFqJzcuxJ6fkcLxxzi9RD1lzD21c=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D0177CEF8@trantor>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <9e81bde0908162340h42011f5cn7606c962fda89da4@xxxxxxxxxxxxxx> <20090817143826.GA4551@xxxxxxxxxxxxxxxxxxx> <9e81bde0908171055q5504683cm19cb2c70e24dfb88@xxxxxxxxxxxxxx> <20090817182023.GA6144@xxxxxxxxxxxxxxxxxxx> <9e81bde0908250357j5678af58ob56633561bf5a2bb@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D0177CE13@trantor> <9e81bde0908280152r35c7b06ck866ab69487e0aa16@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D0177CEF6@trantor> <9e81bde0908280441h2961f63bkf858c6812caeb81e@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D0177CEF8@trantor>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
The .node  member I initialized while declaring  and .callback I initialized in netbacl init function (just above where I use register_xenbus_watch )as  shown below. (used balloon.c as guideline)


static struct xenbus_watch target_watch =
{
    .node = "memory/target"
   
};

static int __init netback_init(void)
{
......
target_watch.callback = watch_target;
... register_xenbus_watch(&target_watch);
...
}

Thanks
Mathew

On Fri, Aug 28, 2009 at 5:14 PM, James Harper <james.harper@xxxxxxxxxxxxxxxx> wrote:
> When I reboot , it is hung at the point above the
> 'register_xenbus_watch(&target_watch)' .
> Neither of the printk messages are dispayed.
>

Please show the code where you initialize target_watch

James

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