[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [PATCH 9/9] In pci_frontend_disable_msi do not alter the dev->irq.



The MSI subsystem keeps track of the IRQ number before enabling
MSI and it will write the old IRQ once it has completed disabling
MSI functionality of the device.

Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
---
 drivers/pci/xen-pcifront.c |    4 +---
 1 files changed, 1 insertions(+), 3 deletions(-)

diff --git a/drivers/pci/xen-pcifront.c b/drivers/pci/xen-pcifront.c
index ca95b23..cc3b51b 100644
--- a/drivers/pci/xen-pcifront.c
+++ b/drivers/pci/xen-pcifront.c
@@ -368,9 +368,7 @@ void pci_frontend_disable_msi(struct pci_dev *dev)
                printk(KERN_DEBUG "get no response from backend for disable 
MSI\n");
                return;
        }
-       if (likely(!err))
-               dev->irq = op.value;
-       else
+       if (err)
                /* how can pciback notify us fail? */
                printk(KERN_DEBUG "get fake response frombackend \n");
 }
-- 
1.6.2.5


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.