From: Wei Liu Subject: Re: [RFC PATCH 0/8] Xen: FIFO-based event channel ABI Date: Fri, 16 Aug 2013 17:55:28 +0100 Message-ID: <20130816165528.GG12674@zion.uk.xensource.com> References: <1376071720-17644-1-git-send-email-david.vrabel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1376071720-17644-1-git-send-email-david.vrabel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: David Vrabel Cc: Wei Liu , Keir Fraser , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Fri, Aug 09, 2013 at 07:08:32PM +0100, David Vrabel wrote: > This is an RFC of the FIFO-based event channel ABI described in this > design document: > > http://xenbits.xen.org/people/dvrabel/event-channels-D.pdf > > Changes in draft D include: > > - Only Xen writes to the HEAD field in the control block > > - Added a link_bits field to EVTCHNOP_init_control to return the > number of valid bits for the LINK field. > > Patch 1-4 do some preparatory work for supporting alternate ABIs. > > Patch 5-8 expand the number of evtchn objects a domain may have to Patch 5-6. :-) > changing how they are allocated. > > Patch 7-8 add the ABI and the implementation. Patch 8 list some of > the known limitations with this RFC implementation. > > Changes in v1: > > - Updates for Draft D of the design. > - 130,000+ event channels are now supported. > - event_port.c -> event_2l.c and only contains 2l functions. > - Addresses various review comments > - int -> unsigned in lots of places > - use write_atomic() to set HEAD > - removed MAX_EVTCHNS > - evtchn_ops are const. > - Pack struct evtchns better to reduce memory needed. > > David