xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: David Vrabel <david.vrabel@citrix.com>, xen-devel@lists.xenproject.org
Cc: Ross Lagerwall <ross.lagerwall@citrix.com>,
	Sander Eikelenboom <linux@eikelenboom.it>
Subject: Re: [PATCHv1] xen/events/fifo: Handle linked events when closing a PIRQ port
Date: Mon, 10 Aug 2015 12:09:50 -0400	[thread overview]
Message-ID: <55C8CCCE.9010503@oracle.com> (raw)
In-Reply-To: <1439216678-12407-1-git-send-email-david.vrabel@citrix.com>

On 08/10/2015 10:24 AM, David Vrabel wrote:
> Commit fcdf31a7c162de0c93a2bee51df4688ab0a348f8 (xen/events/fifo:
> Handle linked events when closing a port) did not handle closing a
> port bound to a PIRQ because these are closed from shutdown_pirq()
> which is called with interrupts disabled.
>
> Defer the close to a work queue where we can safely spin waiting for
> the LINKED bit to clear.  For simplicity, the close is always deferred
> even if it is not required (i.e., we're already in process context).
>
> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
> Cc: Ross Lagerwall <ross.lagerwall@citrix.com>

Reviewed-by: Boris Ostrovsky <bori.ostrovsky@oracle.com>

  reply	other threads:[~2015-08-10 16:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10 14:24 [PATCHv1] xen/events/fifo: Handle linked events when closing a PIRQ port David Vrabel
2015-08-10 16:09 ` Boris Ostrovsky [this message]
2015-08-10 16:47 ` linux
2015-08-10 17:16   ` David Vrabel
2015-09-16 15:26     ` Boris Ostrovsky
2015-09-16 15:34       ` David Vrabel
2015-09-16 17:34         ` Boris Ostrovsky

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=55C8CCCE.9010503@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=linux@eikelenboom.it \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).