From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Bug when disabling/enabling a PT device with MSI enabled Date: Tue, 24 Nov 2009 14:48:15 -0500 Message-ID: <20091124194815.GB29566@phenom.dumpdata.com> References: <8686c3cd0911241042n1b6f84a9u3623518baa021cc2@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <8686c3cd0911241042n1b6f84a9u3623518baa021cc2@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Tom Rotenberg Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Tue, Nov 24, 2009 at 08:42:49PM +0200, Tom Rotenberg wrote: > Hi, > > I am using the xen-3,4, and i am doing pass-through for a device with > MSI enabled (the device of-course supports MSI) to a domU with Windows > XP. When i disable and then re-enable the device using Windows device > manager, everything looks like it's working fine, but the device seems > to malfunction. > After digging a little bit, i saw that the problem is, because the bit > of the interrupt-status (bit 3) in the status register (offset 0x6 in > the PCI config space) was turned on somehow - this proibably caused > the MSI to malfunction (because the IntX assertion was enabled - thus > disabling the MSI) - and this lead to the problem i experienced. > > Any ideas on how to solve this issue? Looks like QEMU is not doing its job. It ought to be tracking when an MSI devices transforms to a INTx PCI device (and vice-versa) and make the appropiate Xen calls. Look in ioemu-dir/hw/pass-through.c