From mboxrd@z Thu Jan 1 00:00:00 1970 From: Harry Butterworth Subject: Re: xen_blk driver Date: Tue, 03 May 2005 10:35:28 +0100 Message-ID: <1115112929.7563.1.camel@localhost> References: <20050503092356.GJ3325@idi.ntnu.no> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20050503092356.GJ3325@idi.ntnu.no> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?UTF-8?Q?H=E5=B6=A1rd?= Bjerke Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org The blkfront code sends xend a "driver status up" message in wait_for_blkif. Xend uses this as a stimulus to notify the blkfront code about available block devices. On Tue, 2005-05-03 at 11:23 +0200, H?ard Bjerke wrote: > I have some trouble understanding the interface between the blkfront and blkback drivers. When a dom1 is created, after xlblk_init() is called, the wait_for_blkif() routine waits for a connection of some kind until it times out with a "xen_blk: Timeout connecting to device!". Is this a connection from Xend, Xen or dom0 it's waiting for? How is this connection timed to occur exactly when wait_for_blkif() is looping? > > Hvard > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >