From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [PATCH v2] xen/events/fifo: Handle linked events when closing a port Date: Tue, 4 Aug 2015 15:57:26 +0100 Message-ID: <55C0D2D6.8040807@citrix.com> References: <1438349442-19339-1-git-send-email-ross.lagerwall@citrix.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 1ZMder-0006Sd-O0 for xen-devel@lists.xenproject.org; Tue, 04 Aug 2015 14:57:37 +0000 In-Reply-To: <1438349442-19339-1-git-send-email-ross.lagerwall@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: Ross Lagerwall , xen-devel@lists.xenproject.org Cc: Boris Ostrovsky , David Vrabel List-Id: xen-devel@lists.xenproject.org On 31/07/15 14:30, Ross Lagerwall wrote: > When a channel is closed and the event is still linked into a queue, > ensure that it is unlinked before completing. If it is not unlinked and > the port is subsequently reused, events may be missed. > > If the CPU to which the event channel bound is online, spin until the > event is handled by that CPU. If that CPU is offline, it can't handle > the event, so clear the event queue during the close, dropping the > events. > > This fixes missing interrupts (and subsequent disk stalls) when > offlining a CPU. Applied to for-linus-4.2 and tagged for stable, thanks. David