From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mukesh Rathor Subject: Re: xenbus callback probe... Date: Tue, 16 Dec 2008 19:15:02 -0800 Message-ID: <49486EB6.3050003@oracle.com> References: Reply-To: mukesh.rathor@oracle.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Thanks. Now, that I played around a bit, am going in circles trying to figure how to keep very simple in my messaging driver. Basically, I'd like to keep it symmetric, no frontend/backend, just one file, dynamically loadable, kernel driver. When a driver is loaded in domU, it broadcasts ring-ref/event-chnl and causes dom0 callback to wake up and act on it. Since domU can't write to /local/domain/0/blah/bleh, is there some other generic way to broadcast it? I'd like to avoid a user level script. It almost appears xenbus_watch_path() may allow me to set callback on /local/domain/*/blah/bleh, but I don't have the xenbus_device ptr as it seems provided by xenbus_driver{} callbacks. Thanks in advance, Mukesh Keir Fraser wrote: > On 11/12/2008 03:14, "Mukesh Rathor" wrote: > >> Hi, >> >> I'm trying to figure what causes a probe callback to happen, any quick >> example? > > New directories appearing in xenstore under /local/domain/x/device/ > > -- Keir >