[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Regression in PCI pass-through from qemu-xen changeset "passthrough: Fix older kernel assigned device resume failure problem"
Simon Horman writes ("Re: [Xen-devel] Regression in PCI pass-through from qemu-xen changeset "passthrough: Fix older kernel assigned device resume failure problem""): On Sat, May 02, 2009 at 12:10:15PM +1000, Simon Horman wrote: > Changeset "passthrough: Fix older kernel assigned device resume failure > problem" (dbb8aafa702b8b4f5568e08641d98471fd04e0f8) in > qemu-xen-unstable.git appears to cause a regression. This changeset was > applied between the xen-3.4.0-rc2 and xen-3.4.0-rc3 tags of > qemu-xen-unstable.git. ... > The problem that I am seeing is that with this changeset applied > I am not able to correctly initialise Intel network cards. Though > I assume the problem is not specific to this hardware. Thanks ... Cui, Dexuan writes ("[PATCH][ioemu] fix PCI bar mapping"): > dbb8aafa702b8b4f5568e08641d98471fd04e0f8 has a bug: > The virtual CMD value we get from reg_entry->data is not the proper value > because reg_entry->data only holds the emulated bits and the > PCI_COMMAND_IO/PCI_COMMAND_MEMORY bits are not in it. > Instead, we can use pt_pci_read_config(&ptdev->dev, PCI_COMMAND, 2) to get > the proper value. ... Cui, do you think this is likely to fix Simon's problem ? I'm about to apply it, in any case, but I was wondering if we have another problem too. Thanks, Ian. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |