From mboxrd@z Thu Jan  1 00:00:00 1970
From: Wei Liu <wei.liu2@citrix.com>
Subject: [RFC PATCH V2] Implement 3-level event channel support
	in Xen
Date: Mon, 21 Jan 2013 14:30:40 +0000
Message-ID: <1358778654-29559-1-git-send-email-wei.liu2@citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: xen-devel@lists.xen.org
Cc: ian.campbell@citrix.com, jbeulich@suse.com, david.vrabel@citrix.com
List-Id: xen-devel@lists.xenproject.org

This is version 2 of the patch series. I've broken down the series to small
patches. I also added more comments in the commit log.

Apart from normal fixes and cleanups, the differences between V1 and V2 are:
* Use function pointers to get rid of switch statments
* Do not manipulate VCPU state
* No more gcc-ism code in public headers
* Consolidate some boilerplates using macros

The compat shim is not implemented at the moment. Will do this when we reach
consensus on the interface.

Under what curcumstance should we enable 3-level event channel is still open
for discussion.


Thanks
Wei.