[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] event notify during netfront and netback setup in Xen3.1

  • To: "Zang Hongyong" <zanghongyong@xxxxxxxxxx>
  • 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
  • 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=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

> 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

Hope this helps

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.