From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Abd-El-Malek <mabdelmalek@cmu.edu>
Subject: Xen bus drivers and the probe function
Date: Tue, 02 Oct 2007 01:39:35 -0400
Message-ID: <4701D997.5060108@cmu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Hello,

I'm writing a split driver for XenBus.  My understanding is that this is 
the "Xen way" for inter-domain discovery, bootstrapping the process by 
sharing grants and event channels.

When I look at the block driver, the probe method of the front- and 
back-ends seems to be doing the bulk of the initialization work.  In my 
sample driver, however, my probe function isn't called.  My module gets 
inserted and the initialization function correctly installs the XenBus 
driver.

Can someone please explain when the probe function is supposed to be 
called?  If there's no physical device "backing" the virtual device 
(i.e., virtual block driver is a counterexample), should I be relying on 
the probe method in the first place?

Thanks,
Mike