From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [RFC PATCH V3 21/22] Only allow extended event channel on Dom0 and driver domains Date: Thu, 28 Feb 2013 12:43:16 +0000 Message-ID: <512F50E4.6020201@citrix.com> References: <1361975655-22295-1-git-send-email-wei.liu2@citrix.com> <1361975655-22295-22-git-send-email-wei.liu2@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1361975655-22295-22-git-send-email-wei.liu2@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: Wei Liu Cc: "Keir (Xen.org)" , Ian Campbell , "jbeulich@suse.com" , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 27/02/13 14:34, Wei Liu wrote: > For non-Dom0 domains, add a flag to indicate whether it can use extended event > channel, admins can specify this flag when creating a driver domain. > > The rationale behide this option is, a) extended event channel will > consume global mapping space in Xen, b) likely that only Dom0 and driver > domains need this. I would prefer the toolstack to limit the max port that the guest can use (see the EVTCHNOP_set_limit sub-op I proposed), than this single bit (which isn't useful for the FIFO-based proposal). David