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/
Home Products Support Community News


Re: [Xen-devel] simple backend, frontend

To: Keir Fraser <keir.fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] simple backend, frontend
From: Deepak Manohar <mjdeepak@xxxxxxxxx>
Date: Fri, 12 Nov 2004 16:03:05 -0500
Cc: andrew.warfield@xxxxxxxxxxxx, mark.williamson@xxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 12 Nov 2004 21:34:13 +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:references; b=LxFnC4fe+rDMFeDAETaDnFISNr+IEUSwat+PO+uCwKJknQpvkPgwnS0B6//ifHQKnX/kRKIwiCGBj92Zc7hQAFr4MNipPQZgw1CJjkmmDJznMoj6Flh0lFft6vFYM+iD2wQd+3w9opepEjnBfCAq9AkfqOSXG8VV60P0MtXHEes=
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: <E1CSWhC-0004SE-00@xxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <fdef3c24041111112178c14610@xxxxxxxxxxxxxx> <E1CSWhC-0004SE-00@xxxxxxxxxxxxxxxxx>
Reply-to: Deepak Manohar <mjdeepak@xxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Hi Keir,

> To set up an event channel and shared memory between two domains you
> need some out-of-band communication, which may or may not be xend.
> Instead the communication could be done via an interdomain IP network,
> for example. However you arrange it, each domain probably needs to
> know the domid of the other guy. Also both ends need to know the
> address of the page they are to share, and the remote port for teh
> shared event channel.
>  -- Keir

 ok lets say that via some out of band comm channel i inform both
domains about the remote port of the shared event channel and the
address of the shared page.

 can u tell me in which file is the api to perform operations on a
shared event channel? is it in xen/common/event_channel.c or is it in
linux-2.6.9-xen-sparse/drivers/xen/evtchn/evtchn.c or

im confused which of the above api is accessible for a module in the
xenolinux kernel.

further more why arent these files in the linux-2.4.27-xen-sparse
directory? (everything works fine so it is not a prob - but i thought
the same file structure might have been followed for 2.4 and 2.6)



On Fri, 12 Nov 2004 08:22:14 +0000, Keir Fraser
<keir.fraser@xxxxxxxxxxxx> wrote:
> >  Now if I need to add another custom backend using the same method as
> > the netif or blkif backends dont I have to modify Xend as well?
> >
> > Is there a simpler way of establishing event channels between domains
> > by directly accessing the API in xen/common/event_channel.c
> >
> >  Some assumptions that Im making - the frontend will be started only
> > after the backend is running. Im primarily going to be using this
> > frontend/backend for transferring large data between a user domain and
> > the control domain.  So I will have to establish shared mem pages as
> > well.

This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
Xen-devel mailing list