From mboxrd@z Thu Jan 1 00:00:00 1970 From: NAHieu Subject: Re: back/frontend drivers HelloWorld Date: Fri, 23 Sep 2005 20:37:38 +0900 Message-ID: <5d7aca95050923043774747da9@mail.gmail.com> References: <200509221746.32758.tiger@swsoft.mipt.ru> <5d7aca9505092302532b4e88eb@mail.gmail.com> <766473d1a313531c949034405df37ec5@cl.cam.ac.uk> Reply-To: NAHieu Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <766473d1a313531c949034405df37ec5@cl.cam.ac.uk> Content-Disposition: inline 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 , Anton Korenyushkin List-Id: xen-devel@lists.xenproject.org On 9/23/05, Keir Fraser 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. Yes, it is. But looks like xenstore is the only way to "notify" between userspace applications (like one runs in domU and another runs in dom0). Or there is another good solution ? Thanks, NAH