From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [PATCH RFC 0/12] Linux: FIFO-based event channel ABI Date: Mon, 6 May 2013 15:51:27 -0400 Message-ID: <20130506195127.GA22946@phenom.dumpdata.com> References: <1363727099-25519-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: <1363727099-25519-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: Keir Fraser , Wei Liu , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Tue, Mar 19, 2013 at 09:04:47PM +0000, David Vrabel wrote: > This is an RFC of Linux guest-side implementation of the FIFO-based > event channel ABI described in this design document: > > http://xenbits.xen.org/people/dvrabel/event-channels-C.pdf > > Refer also to the Xen series. > > Patch 1 fixes a regression introduced in 3.7 and is unrelated to this > series. > > Patch 2 is a obvious refactoring of common code. > > Patch 3-7 prepare for supporting multiple ABIs. > > Patch 8 adds the low-level evtchn_ops hooks. > > Patch 9-10 add an additional hook for ABI-specific per-port setup > (used for expanding the event array as more event are bound). > > Patch 11-12 add the ABI and the implementation. Main known > limitations are listed in patch 12. So what is the status of these patches? Are they going to be reposted at some point? > > David > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel >