Messages in this thread Patch in this message | | | From | Konrad Rzeszutek Wilk <> | Subject | [PATCH v1 6/6] xen/pciback: Don't call xen_pcibk_config_init_dev when device de-assigned. | Date | Wed, 30 Apr 2014 09:54:11 -0400 |
| |
When the device is de-assigned from a guest (but still owned by xen-pciback) we would needlessly free all of its dynamic entries.
That we should not do - that is only to be done when the device has been removed from xen-pciback. That is, when the reference count has reached zero - and we end up calling pcistub_device_release which does this.
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> --- drivers/xen/xen-pciback/pci_stub.c | 2 -- 1 file changed, 2 deletions(-)
diff --git a/drivers/xen/xen-pciback/pci_stub.c b/drivers/xen/xen-pciback/pci_stub.c index d57a173..158d53df 100644 --- a/drivers/xen/xen-pciback/pci_stub.c +++ b/drivers/xen/xen-pciback/pci_stub.c @@ -288,8 +288,6 @@ void pcistub_put_pci_dev(struct pci_dev *dev) /* And cleanup up our emulated fields. */ xen_pcibk_config_reset_dev(dev); - xen_pcibk_config_free_dyn_fields(dev); - xen_unregister_device_domain_owner(dev); spin_lock_irqsave(&found_psdev->lock, flags); -- 1.8.5.3
| |