WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] Paravirt framebuffer frontend kernel support [1/

To: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Paravirt framebuffer frontend kernel support [1/5]
From: Markus Armbruster <armbru@xxxxxxxxxx>
Date: Thu, 02 Nov 2006 13:34:49 +0100
Cc: aliguori <aliguori@xxxxxxxxxxxxxxx>, Steven Smith <sos22@xxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, sos22@xxxxxxxxxxxxx, Jeremy Katz <katzj@xxxxxxxxxx>
Delivery-date: Thu, 02 Nov 2006 13:58:14 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20061102103643.GB3879@xxxxxxxxxxxxxxxxxxxxxx> (Ewan Mellor's message of "Thu, 2 Nov 2006 10:36:43 +0000")
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1157227080.11059.38.camel@xxxxxxxxxxxxxx> <20060904090045.GA4812@xxxxxxxxx> <87hczgrx07.fsf@xxxxxxxxxxxxxxxxx> <20060910093801.GA1874@xxxxxxxxx> <87wt7l68jm.fsf@xxxxxxxxxxxxxxxxx> <871womyxa3.fsf@xxxxxxxxxxxxxxxxx> <20061102103643.GB3879@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux)
Ewan Mellor <ewan@xxxxxxxxxxxxx> writes:

> On Thu, Nov 02, 2006 at 11:10:12AM +0100, Markus Armbruster wrote:
>
>> I'm now looking into a conversion to xenbus_driver API.  I started
>> with copying some voodoo from blkfront.c.  My
>> xenbus_register_frontend() succeeds.  Stupid question: what triggers
>> running of the probe function?  Because mine doesn't.
>
> Either the watch firing when the correct entries in the store are written (for
> hotplugging) or it probes those paths at startup.
>
> xenbus/xenbus_probe.c:
>
> frontend_changed ->
> dev_changed ->
> xenbus_probe_node ->
> device_register
>
> or
>
> xenbus_probe_init ->
> xenbus_probe ->
> xenbus_probe_devices ->
> xenbus_probe_device_type ->
> bus->probe ->
> xenbus_probe_frontend ->
> xenbus_probe_node ->
> device_register
>
> The device_register causes a the specific frontend device to be registered,
> which triggers the probe.
>
> HTH,
>
> Ewan.

Okay, thanks.  Next stupid question: I'm looking for a *user space*
xenbus_register_backend().  Where is it?

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel