From mboxrd@z Thu Jan  1 00:00:00 1970
From: Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH] Paravirt framebuffer frontend kernel support
	[1/5]
Date: Thu, 02 Nov 2006 16:02:48 +0100
Message-ID: <87irhxyjqf.fsf@pike.pond.sub.org>
References: <1157227080.11059.38.camel@aglarond.local>
	<20060904090045.GA4812@cam.ac.uk> <87hczgrx07.fsf@pike.pond.sub.org>
	<20060910093801.GA1874@cam.ac.uk> <87wt7l68jm.fsf@pike.pond.sub.org>
	<871womyxa3.fsf@pike.pond.sub.org>
	<20061102103643.GB3879@leeni.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20061102103643.GB3879@leeni.uk.xensource.com> (Ewan Mellor's
	message of "Thu, 2 Nov 2006 10:36:43 +0000")
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: Ewan Mellor <ewan@xensource.com>
Cc: aliguori <aliguori@mail.utexas.edu>, Steven Smith <sos22@cam.ac.uk>, xen-devel <xen-devel@lists.xensource.com>, sos22@srcf.ucam.org, Jeremy Katz <katzj@redhat.com>
List-Id: xen-devel@lists.xenproject.org

Ewan Mellor <ewan@xensource.com> 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.

Err, I still don't get it.  What exactly makes the guest run the
frontend's probe?  I figure you're trying to tell me that it runs when
a certain xenstore entry is present at startup, or when it gets
created later.  Corrrect?  Which entry exactly?  I tried a few (more
voodoo), but no luck.