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] shared memory and event channel

To: Mark Williamson <mark.williamson@xxxxxxxxxxxx>, Keir Fraser <keir@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] shared memory and event channel
From: tgh <wwwwww4187@xxxxxxxxxxx>
Date: Fri, 21 Dec 2007 16:39:35 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Amit Singh <amit.singh@xxxxxxxxxxx>
Delivery-date: Fri, 21 Dec 2007 00:40:17 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200711280145.31839.mark.williamson@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: <0A8CFEC45B7F4C419F7543867C474423B7788E@xxxxxxxxxxxxxxxxxxxxxx> <200711280145.31839.mark.williamson@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.7 (Windows/20060909)
hi
I read the code of eventchannel,and I am confused by the viarable named as"consumer_is_xen"in the evtchn struct, what is the function of consumer_is_xen? and does dom use eventchannel to communicate with hypervisor? why not the hypercall? and in which condition is eventchannel used in this way,that is ,the dom issues an event to hypervisor or xen,and xen is a consumer?

Thanks in advance




Mark Williamson 写道:
   For each domUs there is unique shared memory(2-way circular queue) and
event-channel(one shared memory and event-channel per domU) or there is
only one shared memory and interdomain event-channel(for every DomU)?

Each domain has a separate shared memory page and event channel. Actually, in general, there are multiple shared memory areas and event channels per domU.

Each virtual device (e.g. virtual network interface) may require its own separate shared memory page and event channel to talk to the backend. So if you have a domain with two vifs it'll need two shared memory pages and two event channels.

The block driver will also want a memory page and event channel for each virtual block device.

And so on.

Hope this helps,

Cheers,
Mark



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

<Prev in Thread] Current Thread [Next in Thread>