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] Handle for events?

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Handle for events?
From: "Srujan D. Kotikela" <ksrujandas@xxxxxxxxx>
Date: Fri, 8 Oct 2010 11:11:29 -0500
Delivery-date: Fri, 08 Oct 2010 09:28:27 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=jxOJUVCpM1PKacYAPRqD6zxh5MKKtxSUacWtN2OL9Bc=; b=P2YbKf01udomd4pteg7e8UVKXjViLfzPTfM/7XsYto6uKPiSeaF7duJziR7imDnnZ6 qsLhdm+UJ9hmcH2ScEinRcxYjg5xrR49CiSGxDzR8glj/KV6PRu9MGLR7KdCwKQbyHo+ mEvtvjG5c7n0q7nVmz8BjCUBPWd94xH57ohDM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=QT9IqazTIFRn/o1AH3U/4eqbtiFkwAin0imLDdolVqmfIXKTJH+vBKHB/ikI/3aqLZ Tw6xFdwkXR/1IbT884hRsTc/ZJxsKtqs3kMA0ACKsmMDv20ZdUwpIbqX1HbfT9cKof6k RLYqjwgZ+NzCd3F/dm8/GLKYoICsCx/qnSqx4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTimqZS_5+rjO5uv9ZBnTKM9feAnupe9KbhZkrug5@xxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTi=TafOCtvaBtfQbmRWyKA1y3_N+fjAT1XzWHZba@xxxxxxxxxxxxxx> <4CA36471.5040503@xxxxxxxx> <AANLkTimHQ=-4ppSs2LuQGmA5v-39EvB59CHM1uFKUW=6@xxxxxxxxxxxxxx> <4CA36965.4040208@xxxxxxxx> <AANLkTim2isZwXL=+xmHN5E66RZv+rtG+iSWGQb63XHyp@xxxxxxxxxxxxxx> <4CA3745A.10900@xxxxxxxx> <AANLkTimqZS_5+rjO5uv9ZBnTKM9feAnupe9KbhZkrug5@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

Hi Jeremy,

I was going through the code in mini-os. The hypervisor_callback, which handles all the events, is defined in the x86_64.S file. In xen sources I see xen/arch/x86/x86_64/entry.S with no such callback function.

>From what I read in the Xen Definitive guide, There is a single handler for all events (hypervisor_callback) which in turn should call individual handlers, which are registered before hand, for each event. I have few questions regarding this:

1. Is there a default event handler for Dom0 kernel (like hypervisor_callback in mini-os). If so, what is the function to register event handlers for specific port/channel (I tried searching the code and couldn't find any)?

2. If no default handler exists how are the handlers for xen_console and xen_store events or any other events setup?

3. Is the ./xen/arch/x86/x86_64/entry.S analogous to ./extras/mini-os/arch/x86/x86_64.S? I mean If I have to write event handler, should I edit entry.S?

--
Srujan D. Kotikela



On Wed, Sep 29, 2010 at 12:16 PM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
 On 09/29/2010 09:34 AM, Srujan D. Kotikela wrote:
> Sorry,
>
> But from what I read I may not get notifications on /dev/xen/evtchn if
> my xen-evtchn module is not functioning. However if it is statically
> compiled it wont be found as a module. I can confirm it's working by
> checking if there are directories in my /proc/xen
>
> correct me if I am wrong.

/proc/xen is irrelevant to xen-evtchn; you would not expect to see any
changes in /proc/xen as a result of xen-evtchn being present or absent.

>
> I am calling notify() and I am getting a return value 0 but no
> notification mesages in /dev/xen/evtchn

You should look carefully at the existing examples of how to use that
device to see where you're going wrong.

   J


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>