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] event notify during netfront and netback setup in Xen3.1

To: "Zang Hongyong" <zanghongyong@xxxxxxxxxx>
Subject: Re: [Xen-devel] event notify during netfront and netback setup in Xen3.1
From: "Grzegorz Miłoś" <gm281@xxxxxxxxx>
Date: Thu, 19 Jun 2008 16:36:43 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 19 Jun 2008 08:37:05 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=39vCOn5ja9dVM1WCVBuGXWcTsTQaiXefdK37A64Vs+4=; b=W7mr3W8RIrEGXztUNbTUR5YP3HA5GFkWsK8SOi4AyzFMbPrQlbZiRgoyaCq+/CO7Ym yQ/EvVW4vjj+rt7PKlTt8v9WT3CcmEqNPVQOL27lL2TPuqGds3bmspQ5mfllqVyUKudf bfOhTAR7ozGIIYimQl4eS/XY7q3VeLFjKYsTQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=EMfcdCdmNeQjO1xsuqxhd+7c9Qk05mqugaiCJ0rrqSFMPnXlp5hI5EIBaH8jMG2LOO syXirmbhiy4c3D4Ub/dNREKACrzbNx82D2MQx/octtTFrD1qFQWzvtcFzjAu6ElTB0mt fUUgJu0UeIhcy7U+GUnbSysBm+N4D4vx4Giq0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20080613004938.ABF77136821@xxxxxxxxxx>
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: <20080613004938.ABF77136821@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> hi
>  In Xen3.1 source
>  when setup
>   netfront: when netback changed XenBusState to InitWait, fuction 
> network_connect() called
>             in network_connect(),notify_remote_via_irq() was called, which 
> gives netback a kick.
>             then netfront changed Xenbusstate to Connected
>
>   but at the same time, netback has not bind its eventchannel to netfront 
> domain's event?
>   so how could this happen, when netback receive event from netfront domain?

Netfront allocates an unbound event channel in responce to the backend
entering InitWait state (network_connect() -> talk_to_backend() ->
setup_device() -> bind_listening_port_to_irqhandler() ->
bind_listening_port_to_irq() -> EVTCHNOP_alloc_unbound). Once the
channel is allocated, the frontend can queue events on it, even before
backend binds it. This happens later on, in responce to netfront
entering Connected state (bind_interdomain_evtchn_to_irqhandler() in
netif_map()).

Hope this helps
Gr(z)egor(z)

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

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