From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Thibault Subject: Re: xenbus call too early? Date: Fri, 2 May 2008 17:41:36 +0100 Message-ID: <20080502164136.GT4432@implementation.uk.xensource.com> References: <20080502101355093.00000041924@djm-pc> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Return-path: Content-Disposition: inline In-Reply-To: <20080502101355093.00000041924@djm-pc> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dan Magenheimer Cc: "Xen-Devel (E-mail)" List-Id: xen-devel@lists.xenproject.org Hello, Dan Magenheimer, le Fri 02 May 2008 10:13:55 -0600, a écrit : > 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. Samuel