This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Possible regression in "passthough: add no_wb option for pci

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Possible regression in "passthough: add no_wb option for pci conf write"
From: Simon Horman <horms@xxxxxxxxxxxx>
Date: Sun, 6 Dec 2009 16:55:03 +1100
Cc: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>, Qing He <qing.he@xxxxxxxxx>
Delivery-date: Sat, 05 Dec 2009 21:55:27 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14)
> passthough: add no_wb option for pci conf write
> Current pt_pci_write_config always writes back to real pci conf
> space. However, in the case of MSI address and data registers,
> if guest changes the affinity of the interrupt, stale data will
> be written to these registers. This is particularly a problem
> if Xen uses per-CPU vector, where the interrupt in question fails
> to work. This patch fixes this by adding an option to disable the
> write back of certain controls.

This patch seems to cause the creation of passing a domain
to fail when passing through either an intel 82576 or 82572EI.
I didn't try any others.

Xen-devel mailing list