From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <JBeulich@suse.com>
Subject: Re: FIFO-based event channel ABI design (draft B)
Date: Fri, 15 Feb 2013 15:36:08 +0000
Message-ID: <511E63F802000078000BECAA@nat28.tlf.novell.com>
References: <511E46FD.3010605@citrix.com>
	<511E5CD202000078000BEC4F@nat28.tlf.novell.com>
	<511E51A4.9020503@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>
In-Reply-To: <511E51A4.9020503@citrix.com>
Content-Disposition: inline
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: David Vrabel <david.vrabel@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>, xen-devel <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

>>> On 15.02.13 at 16:17, David Vrabel <david.vrabel@citrix.com> wrote:
> On 15/02/13 15:05, Jan Beulich wrote:
>> Additionally, I think the number of significant bits of the LINK field
>> should actually be obtained from the hypervisor, rather than being
>> baked at 17 (for the time being). This again is an implementation
>> detail (and the value could easily be command line controllable).
> 
> I'd considered something like this but decided to defer this to a future
> date when it needed to be extended.
> 
> How about adding an EVTCHNOP_get_limit which gets the maximum permitted
> port?  The guest can then round up the result of this to get the maximum
> number of LINK bits.

I'd actually want to make this an output of the setup operation.
Whether to return a bit count or the number of ports is secondary
to me.

Jan