[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Bug when disabling/enabling a PT device with MSI enabled


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Tom Rotenberg <tom.rotenberg@xxxxxxxxx>
  • Date: Tue, 24 Nov 2009 20:42:49 +0200
  • Delivery-date: Tue, 24 Nov 2009 10:43:15 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=cYHkVqgl9fbA3u9pR4hd/bDk3RvbicGtZ0ZXhfvdHIHheZbcfVsBYq/tWE1C7mSwDt OeQnY3y9S15roQdJJKiFTS1vhd9zuHtmWl93lAU7+c4hFsyA72FFx+8XOMjgFS7/dy8L aVehKM1G3NwCW93ewdIq09UEL5juaYNBPnoO4=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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?

Tom

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.