From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boris Ostrovsky Subject: Re: [PATCH 0/3] xen: FIFO-based event channel fixes Date: Thu, 31 Jul 2014 12:16:31 -0400 Message-ID: <53DA6BDF.70503@oracle.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XCt25-0005zm-9y for xen-devel@lists.xenproject.org; Thu, 31 Jul 2014 16:16:45 +0000 In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: David Vrabel , xen-devel@lists.xenproject.org List-Id: xen-devel@lists.xenproject.org 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). -boris