| commit | 7ec7ae4b973d1471f6f39fc2b6481f69c2b39593 | |
| author | Paolo Bonzini <pbonzini@redhat.com> | |
| Thu, 9 Mar 2017 11:58:30 +0000 (9 12:58 +0100) | ||
| committer | Jason Wang <jasowang@redhat.com> | |
| Tue, 14 Mar 2017 07:39:55 +0000 (14 15:39 +0800) | ||
| tree | 5d4a6d243040c6d8720c6012bce5ea3df72f5a26 | treesnapshot (tar.gz zip) |
| parent | 5bac3c39c82e149515c10643acafd1d292433775 | commitdiff |
e1000e: correctly tear down MSI-X memory regions
MSI-X has been disabled by the time the e1000e device is unrealized, hence
msix_uninit is never called. This causes the object to be leaked, which
shows up as a RAMBlock with empty name when attempting migration.
Reported-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: qemu-stable@nongnu.org
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Tested-by: Laurent Vivier <lvivier@redhat.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
MSI-X has been disabled by the time the e1000e device is unrealized, hence
msix_uninit is never called. This causes the object to be leaked, which
shows up as a RAMBlock with empty name when attempting migration.
Reported-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: qemu-stable@nongnu.org
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Tested-by: Laurent Vivier <lvivier@redhat.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
| hw/net/e1000e.c | diffblobblamehistory |