On Tue, 2011-04-12 at 11:02 +0300, Avi Kivity wrote: > On 04/12/2011 10:48 AM, Ren, Yongjie wrote: > > Hi All, > > This is KVM test result against kvm.git 7a7ada1bfb958d2ad722d0df9299f1b0136ec1d4 based on kernel 2.6.39-rc2+, and qemu-kvm.git df85c051d780bca0ee2462cfeb8ef6d9552a19b0. > > > > We found 1 bug about "NIC cannot work when it had been used before ". > > The VT-d bug 730441 (qemu bugzilla) concerning "nomsi NIC" is fixed. > > > > New issue: > > 1.[VT-d] NIC cannot work when it had been used before > > https://bugs.launchpad.net/qemu/+bug/754591 > > > > += Alex. > This is caused by the patch below. When we do a reset via PCI sysfs, the device state is saved and restored around the reset. When the state is restored, the saved state is invalidated. Now when we go to free the device, we call the "I know what I'm doing" __pci_reset_function(), which doesn't save/restore state, then try to do a restore, but there's nothing saved, so the device only has reset values... oops. Jan, do you actually have a test case where you can see a difference restoring the original saved state? I'm tempted to suggest we just revert this patch. Otherwise it seems like we an interface to extract and reload the original saved state for the device. Thanks, Alex commit ed78661f2614d3c9f69c23e280db3bafdabdf5bb Author: Jan Kiszka <jan.kiszka@xxxxxxxxxxx> Date: Tue Nov 16 22:30:05 2010 +0100 KVM: Save/restore state of assigned PCI device The guest may change states that pci_reset_function does not touch. So we better save/restore the assigned device across guest usage. Acked-by: Alex Williamson <alex.williamson@xxxxxxxxxx> Acked-by: Michael S. Tsirkin <mst@xxxxxxxxxx> Signed-off-by: Jan Kiszka <jan.kiszka@xxxxxxxxxxx> Signed-off-by: Marcelo Tosatti <mtosatti@xxxxxxxxxx> diff --git a/virt/kvm/assigned-dev.c b/virt/kvm/assigned-dev.c index 7623408..d389207 100644 --- a/virt/kvm/assigned-dev.c +++ b/virt/kvm/assigned-dev.c @@ -197,7 +197,8 @@ static void kvm_free_assigned_device(struct kvm *kvm, { kvm_free_assigned_irq(kvm, assigned_dev); - pci_reset_function(assigned_dev->dev); + __pci_reset_function(assigned_dev->dev); + pci_restore_state(assigned_dev->dev); pci_release_regions(assigned_dev->dev); pci_disable_device(assigned_dev->dev); @@ -514,6 +515,7 @@ static int kvm_vm_ioctl_assign_device(struct kvm *kvm, } pci_reset_function(dev); + pci_save_state(dev); match->assigned_dev_id = assigned_dev->assigned_dev_id; match->host_segnr = assigned_dev->segnr; @@ -544,6 +546,7 @@ out: mutex_unlock(&kvm->lock); return r; out_list_del: + pci_restore_state(dev); list_del(&match->list); pci_release_regions(dev); out_disable: -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
