From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Xen-unstable: pci-passthrough "irq 16: nobody cared" on HVM guest shutdown on irq of device not passed through. Date: Wed, 8 Oct 2014 08:56:53 -0400 Message-ID: <20141008125653.GA13480@laptop.dumpdata.com> References: <1408854407.20140925190202@eikelenboom.it> <1722134266.20140925204551@eikelenboom.it> <1028558175.20140926000905@eikelenboom.it> <54252AEA02000078000396CD@mail.emea.novell.com> <628393041.20140926111854@eikelenboom.it> <5425514802000078000398D9@mail.emea.novell.com> <735469568.20140927160041@eikelenboom.it> <4410685169.20141001155255@eikelenboom.it> <20141007134100.GD2604@laptop.dumpdata.com> <543419BB020000780003D026@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Xbqnf-0008Bn-3A for xen-devel@lists.xenproject.org; Wed, 08 Oct 2014 12:57:03 +0000 Content-Disposition: inline In-Reply-To: <543419BB020000780003D026@mail.emea.novell.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: Jan Beulich Cc: Sander Eikelenboom , xen-devel List-Id: xen-devel@lists.xenproject.org On Tue, Oct 07, 2014 at 03:50:03PM +0100, Jan Beulich wrote: > >>> On 07.10.14 at 15:41, wrote: > > Could you attach also the full dmesg under baremetal with 'debug' and all > > kinds of debug enabled ? That should help a bit in figuring out why > > they get MSIs under baremetal but legacy interrupts under Xen. > > The messages he sent don't really suggest that. The legacy pin > based IRQ always gets set up when a device gets enabled, no > matter whether in the end it would actually get used. And afaict > other messages clearly hint at MSI being used for the PCIe stuff. Correct. I fear that in the domain0 we have set an event for this particular GSI (16) which is also in use in the guest (and then somehow we did not tear this down when the PCIe setup the MSI). Xen will send events to both domains - and since domain0 does not have an IRQ handler for it - it will activate its anti-IRQ storm routine and disabling the IRQ line. > > Jan >