From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Dan Magenheimer" Subject: RE: xenbus call too early? Date: Fri, 2 May 2008 15:25:14 -0600 Message-ID: <20080502152514828.00000041924@djm-pc> References: <20080502164136.GT4432@implementation.uk.xensource.com> Reply-To: "dan.magenheimer@oracle.com" Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20080502164136.GT4432@implementation.uk.xensource.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: Samuel Thibault Cc: "Xen-Devel (E-mail)" List-Id: xen-devel@lists.xenproject.org > Dan Magenheimer, le Fri 02 May 2008 10:13:55 -0600, a =E9crit : > > I added a xenbus_printk call that causes boot to fail, > > I suspect because I am calling it before xenbus is up > > and working. > > > > (Same code works fine if called later.) > > > > Is there a function that does is_xenbus_ready()? > > If not, what's the best way to do the equivalent? > = > There apparently is a xenstored_ready variable. Thanks, but hmmm..., it doesn't look like this is accessed anywhere, nor is it EXPORTed so it wouldn't be accessible from a module. >>From more code reading, I'm guessing the right way to do this is to key off of a xenstore_notifier call which can set the local static equivalent of xenstored_ready. True? Thanks, Dan