xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: linux@eikelenboom.it
Cc: xen-devel@lists.xenproject.org,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Ross Lagerwall <ross.lagerwall@citrix.com>
Subject: Re: [PATCHv1] xen/events/fifo: Handle linked events when closing a PIRQ port
Date: Mon, 10 Aug 2015 18:16:36 +0100	[thread overview]
Message-ID: <55C8DC74.70809@citrix.com> (raw)
In-Reply-To: <3b1a3ef1046357c95dd25a8610b1fd11@eikelenboom.it>

On 10/08/15 17:47, linux@eikelenboom.it wrote:
> On 2015-08-10 16:24, 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>
>> ---
>> Cc: Sander Eikelenboom <linux@eikelenboom.it>
> 
> Hi David,
> 
> Tested your patch, don't know for sure but this doesn't seem to work out.
> I end up with this event channel error on dom0 boot.
> 
> Which ends in state:
> Name                                        ID   Mem VCPUs    State   
> Time(s)
> (null)                                       0  1536     6     r-----   
>  183.8
> 
> -- 
> Sander
> 
> (XEN) [2015-08-10 16:35:34.584] PCI add device 0000:0d:00.0
> (XEN) [2015-08-10 16:35:34.891] PCI add device 0000:0c:00.0
> (XEN) [2015-08-10 16:35:35.123] PCI add device 0000:0b:00.0
> (XEN) [2015-08-10 16:35:35.325] PCI add device 0000:0a:00.0
> (XEN) [2015-08-10 16:35:35.574] PCI add device 0000:09:00.0
> (XEN) [2015-08-10 16:35:35.642] PCI add device 0000:09:00.1
> (XEN) [2015-08-10 16:35:35.872] PCI add device 0000:05:00.0
> (XEN) [2015-08-10 16:35:36.044] PCI add device 0000:06:01.0
> (XEN) [2015-08-10 16:35:36.109] PCI add device 0000:06:02.0
> (XEN) [2015-08-10 16:35:36.293] PCI add device 0000:08:00.0
> (XEN) [2015-08-10 16:35:36.603] PCI add device 0000:07:00.0
> (XEN) [2015-08-10 16:35:36.906] PCI add device 0000:04:00.0
> (XEN) [2015-08-10 16:35:37.074] PCI add device 0000:03:06.0
> (XEN) [2015-08-10 16:35:39.456] PCI: Using MCFG for segment 0000 bus 00-ff
> (XEN) [2015-08-10 16:35:49.623] d0: Forcing read-only access to MFN fed00
> (XEN) [2015-08-10 16:35:51.374] event_channel.c:472:d0v0 EVTCHNOP
> failure: error -17

This didn't happen on the test box I used but I can see it is possible
to rebind a PIRQ whose close is still deferred.

I'm going to revert fcdf31a7c162de0c93a2bee51df4688ab0a348f8
(xen/events/fifo: Handle linked events when closing a port) for now.

David

  reply	other threads:[~2015-08-10 17:16 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
2015-08-10 16:47 ` linux
2015-08-10 17:16   ` David Vrabel [this message]
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=55C8DC74.70809@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=boris.ostrovsky@oracle.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).