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

[Xen-devel] [PATCH] linux-2.6.18/pciback: notify hypervisor about devices intended to be assigned to guests


  • To: "xen-devel" <xen-devel@xxxxxxxxxxxxx>
  • From: "Jan Beulich" <JBeulich@xxxxxxxx>
  • Date: Tue, 12 Mar 2013 16:18:29 +0000
  • Delivery-date: Tue, 12 Mar 2013 16:19:08 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

For MSI-X capable devices the hypervisor wants to write protect the
MSI-X table and PBA, yet it can't assume that resources have been
assigned to their final values at device enumeration time. Thus have
pciback do that notification, as having the device controlled by it is
a prerequisite to assigning the device to guests anyway.

Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>

--- a/drivers/xen/pciback/pci_stub.c
+++ b/drivers/xen/pciback/pci_stub.c
@@ -14,6 +14,7 @@
 #include <linux/wait.h>
 #include <asm/atomic.h>
 #include <xen/evtchn.h>
+#include <xen/interface/physdev.h>
 #include "pciback.h"
 #include "conf_space.h"
 #include "conf_space_quirks.h"
@@ -82,19 +83,38 @@ static struct pcistub_device *pcistub_de
 static void pcistub_device_release(struct kref *kref)
 {
        struct pcistub_device *psdev;
+       struct pci_dev *dev;
 
        psdev = container_of(kref, struct pcistub_device, kref);
+       dev = psdev->dev;
+
+       dev_dbg(&dev->dev, "pcistub_device_release\n");
 
-       dev_dbg(&psdev->dev->dev, "pcistub_device_release\n");
+       if (pci_find_capability(dev, PCI_CAP_ID_MSIX)) {
+               struct physdev_pci_device ppdev = {
+                       .seg = pci_domain_nr(dev->bus),
+                       .bus = dev->bus->number,
+                       .devfn = dev->devfn
+               };
+               int err = HYPERVISOR_physdev_op(PHYSDEVOP_release_msix,
+                                               &ppdev);
+
+#if CONFIG_XEN_COMPAT < 0x040300
+               if (err != -ENOSYS)
+#endif
+               if (err)
+                       dev_warn(&dev->dev, "MSI-X release failed (%d)\n",
+                                err);
+       }
 
        /* Clean-up the device */
-       pciback_reset_device(psdev->dev);
-       pciback_config_free_dyn_fields(psdev->dev);
-       pciback_config_free_dev(psdev->dev);
-       kfree(pci_get_drvdata(psdev->dev));
-       pci_set_drvdata(psdev->dev, NULL);
+       pciback_reset_device(dev);
+       pciback_config_free_dyn_fields(dev);
+       pciback_config_free_dev(dev);
+       kfree(pci_get_drvdata(dev));
+       pci_set_drvdata(dev, NULL);
 
-       pci_dev_put(psdev->dev);
+       pci_dev_put(dev);
 
        kfree(psdev);
 }
@@ -313,6 +333,22 @@ static int __devinit pcistub_init_device
        if (err)
                goto config_release;
 
+       if (pci_find_capability(dev, PCI_CAP_ID_MSIX)) {
+               struct physdev_pci_device ppdev = {
+                       .seg = pci_domain_nr(dev->bus),
+                       .bus = dev->bus->number,
+                       .devfn = dev->devfn
+               };
+
+               err = HYPERVISOR_physdev_op(PHYSDEVOP_prepare_msix, &ppdev);
+#if CONFIG_XEN_COMPAT < 0x040300
+               if (err != -ENOSYS)
+#endif
+               if (err)
+                       dev_err(&dev->dev, "MSI-X preparation failed (%d)\n",
+                               err);
+       }
+
        /* Now disable the device (this also ensures some private device
         * data is setup before we export)
         */



Attachment: xen-pciback-MSI-X-prepare.patch
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

 


Rackspace

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