From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: Xen-unstable: Xen panic when shutting down HVM
 guest with PCI passthrough: RIP: e008:[<ffff82d0801099b1>]
 evtchn_move_pirqs+0x90/0xbf
Date: Thu, 5 Jun 2014 17:22:11 +0100
Message-ID: <53909933.5020109@citrix.com>
References: <495141585.20140605165458@eikelenboom.it>
	<539086BC.7070200@citrix.com>
	<1617474467.20140605180343@eikelenboom.it>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Andrew.Cooper3@citrix.com>) id 1WsaQi-0000GO-0G
	for xen-devel@lists.xenproject.org; Thu, 05 Jun 2014 16:22:16 +0000
In-Reply-To: <1617474467.20140605180343@eikelenboom.it>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: George Dunlap <george.dunlap@eu.citrix.com>, xen-devel@lists.xenproject.org, Juergen Gross <jgross@suse.com>, Jan Beulich <jbeulich@suse.com>
List-Id: xen-devel@lists.xenproject.org

On 05/06/14 17:03, Sander Eikelenboom wrote:
> Thursday, June 5, 2014, 5:03:24 PM, you wrote:
>
>> On 05/06/14 15:54, Sander Eikelenboom       wrote:
>>   
>> Hi,
>> When shutting down a HVM guest with PCI passthrough Xen panics with the panic 
>> below (complete xl-dmesg attached).
>> # addr2line -e xen-syms ffff82d0801099b1
>> /usr/src/new/xen-unstable/xen/common/event_channel.c:1326
>> which is:
>>         pirq_set_affinity(d, chn->u.pirq.irq, mask);
>>   
>>   
>>      This is presumably an ordering issue on destroy.
>>   
>>      Does reverting bac6334b5 fix the problem?
>>   
>>      ~Andrew
> Hi Andrew,
>
> That seems to have been a good hunch, after reverting that commit i have been
> able to repeatedly create and shutdown the guest with passthrough, without a crash.
>
> --
> Sander  
>

CC'ing George and Juergen as the authors of the identified patch

c/s bac6334b5 "move domain to cpupool0 before destroying it" appears to
cause the crash identified the root of this thread.

It appears to now move event channels after having torn parts of the
event channel infrastructure.

~Andrew