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] back/frontend drivers HelloWorld

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] back/frontend drivers HelloWorld
From: NAHieu <nahieu@xxxxxxxxx>
Date: Sun, 25 Sep 2005 02:40:36 +0900
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sat, 24 Sep 2005 17:38:20 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=mdEuapz9zkoRISgpKvTwAWxGaAZ2582u7vyiTLJ9mpIszJyPx8FNw13vMjgpR6PId7aFTfF87SfE7N6+SEdwQg4jgj5tyL8rucaqXvEX7Fy7ienfsuTSUcj7Ieq5XCdSSaMqvdivRnb/mQW6dtWKgdcfoVE4gX5AIPSzTdxz+9E=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <766473d1a313531c949034405df37ec5@xxxxxxxxxxxx>
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: <200509221746.32758.tiger@xxxxxxxxxxxxxx> <fca75d25983158236837abcbeb5c6af7@xxxxxxxxxxxx> <5d7aca9505092302532b4e88eb@xxxxxxxxxxxxxx> <766473d1a313531c949034405df37ec5@xxxxxxxxxxxx>
Reply-to: NAHieu <nahieu@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 9/23/05, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
>
> On 23 Sep 2005, at 10:53, NAHieu wrote:
>
> >> You bootstrap yourself via xenbus. You have a pre-agreed location in
> >> the xenstore hieararchy where the frontend driver writes key-value
> >> pairs containing the grant reference for the page containing the
> >> message rings, and an event channel for async notifications.
> >>
> >
> > I imagine that we can get rid of event channel, and use xenstore to
> > notify. That is certainly OK, but I doubt about its efficientcy. What
> > do you think?
>
> Very mad. It's easy to set up an inter-domain event channel betwene
> domains A and B:
>   1. A executes something like evtchn = EVTCHNOP_alloc_unbound(B)
>   2. A writes 'evtchn' into xenstore.
>   3. B reads 'evtchn' from xenstore
>   4. B executes something like EVTCHNOP_bind_interdomain(A,evtchn)

It seems I also need to use bind_evtchn_to_irq() to handle event sent
from event-channel?


Could you tell me which code in Xen uses the above 1->4 setup
procedure? I searched for some examples, but couldnt find any.


Great thanks,
Hieu

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