From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Vrabel <david.vrabel@citrix.com>
Subject: Re: [RFC PATCH V4 18/18] libxl: add
 evtchn_extended_allowed flag
Date: Thu, 7 Mar 2013 11:23:40 +0000
Message-ID: <513878BC.8010303@citrix.com>
References: <1362486640-14707-1-git-send-email-wei.liu2@citrix.com>	<1362486640-14707-19-git-send-email-wei.liu2@citrix.com>	<20789.63420.221613.601890@mariner.uk.xensource.com>	<1362503503.4748.46.camel@zion.uk.xensource.com>	<20790.11694.181357.789414@mariner.uk.xensource.com>	<20130305175133.GB11446@zion.uk.xensource.com>	<513631BC.9020105@citrix.com>	<20130305180815.GC11446@zion.uk.xensource.com>
	<1362590185.29093.5.camel@zion.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <1362590185.29093.5.camel@zion.uk.xensource.com>
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: Wei Liu <wei.liu2@citrix.com>
Cc: "Keir (Xen.org)" <keir@xen.org>, Ian Campbell <Ian.Campbell@citrix.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>, David Vrabel <david.vrabel@citrix.com>, "jbeulich@suse.com" <jbeulich@suse.com>
List-Id: xen-devel@lists.xenproject.org

On 06/03/13 17:16, Wei Liu wrote:
> Let's start with documentation. I came up with two options for libxl, I
> plan to choose one from them. The first one is generic, the second one
> is 3-level ABI centric.
> 
> =item B<max_event_channels=NUMBER>
> 

I would remove all references to specific ABIs where possible.  Perhaps:

"=item B<max_event_channels=NUMBER>

Maximum number of event channels a guest can use.  Use this to limit the
amount of Xen resources the guest may use for event channels.

The default value for this option is 1024 which is sufficient for a
normal guest. Driver or service domains may need more.

Depending on architecture and the support available in the guest, the
guest may be restricted to less than this limit."

David