From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [PATCH RFC 0/12] Linux: FIFO-based event channel ABI Date: Tue, 7 May 2013 13:26:48 +0100 Message-ID: <5188F308.8030801@citrix.com> References: <1363727099-25519-1-git-send-email-david.vrabel@citrix.com> <20130506195127.GA22946@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20130506195127.GA22946@phenom.dumpdata.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: Konrad Rzeszutek Wilk Cc: "Keir (Xen.org)" , Wei Liu , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 06/05/13 20:51, Konrad Rzeszutek Wilk wrote: > 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? Yes. It's not the highest priority right now so it might be a while before I can work on this. David