From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [PATCH 0/3] xen: FIFO-based event channel fixes Date: Thu, 31 Jul 2014 17:17:39 +0100 Message-ID: <53DA6C23.6060500@citrix.com> References: <53DA6BDF.70503@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XCt7G-0006CG-9t for xen-devel@lists.xenproject.org; Thu, 31 Jul 2014 16:22:06 +0000 In-Reply-To: <53DA6BDF.70503@oracle.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: Boris Ostrovsky , xen-devel@lists.xenproject.org List-Id: xen-devel@lists.xenproject.org On 31/07/14 17:16, Boris Ostrovsky wrote: > On 07/31/2014 11:22 AM, David Vrabel wrote: >> Two fixes and one cleanup for the FIFO-based event channel ABI. >> >> The first fixes an early hang when resuming guests -- this often >> occured with PVHVM guests but PV guests for some reason got away with >> it... >> >> The second fixes a rare crash if 1023 event channels (or more) were >> used -- this would typically only affect dom0. > > Reviewed-by: Boris Ostrovsky@oracle.com > > (although evtchn_fifo_init_control_block() vs init_control_block() > naming in patch 1 is slightly confusing I think). I'll change the first to evtchn_fifo_alloc_control_block(). Is that ok? David