From: David Vrabel <david.vrabel@citrix.com>
To: Ross Lagerwall <ross.lagerwall@citrix.com>,
xen-devel@lists.xenproject.org
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
David Vrabel <david.vrabel@citrix.com>
Subject: Re: [PATCH v2] xen/events/fifo: Handle linked events when closing a port
Date: Tue, 4 Aug 2015 15:57:26 +0100 [thread overview]
Message-ID: <55C0D2D6.8040807@citrix.com> (raw)
In-Reply-To: <1438349442-19339-1-git-send-email-ross.lagerwall@citrix.com>
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
prev parent reply other threads:[~2015-08-04 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 13:30 [PATCH v2] xen/events/fifo: Handle linked events when closing a port Ross Lagerwall
2015-07-31 13:45 ` David Vrabel
2015-08-04 14:57 ` David Vrabel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55C0D2D6.8040807@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=ross.lagerwall@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.