diff mbox

[v4,09/10] vfio-pci: pass the aer error to guest

Message ID 1458554926-7844-10-git-send-email-caoj.fnst@cn.fujitsu.com
State New
Headers show

Commit Message

Cao jin March 21, 2016, 10:08 a.m. UTC 
From: Chen Fan <chen.fan.fnst@cn.fujitsu.com>

when the vfio device encounters an uncorrectable error in host,
the vfio_pci driver will signal the eventfd registered by this
vfio device, resulting in the qemu eventfd handler getting
invoked.

this patch is to pass the error to guest and let the guest driver
recover from the error.

Signed-off-by: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
---
 hw/vfio/pci.c | 54 ++++++++++++++++++++++++++++++++++++++++++++++++------
 1 file changed, 48 insertions(+), 6 deletions(-)
diff mbox

Patch

diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
index 718cde7..d2f47ee 100644
--- a/hw/vfio/pci.c
+++ b/hw/vfio/pci.c
@@ -2611,6 +2611,11 @@  static void vfio_err_notifier_handler(void *opaque)
 {
     VFIOPCIDevice *vdev = opaque;
     PCIDevice *pdev = &vdev->pdev;
+    Error *local_err = NULL;
+    PCIEAERMsg msg = {
+        .severity = 0,
+        .source_id = (pci_bus_num(pdev->bus) << 8) | pdev->devfn,
+    };
 
     if (!event_notifier_test_and_clear(&vdev->err_notifier)) {
         return;
@@ -2622,6 +2627,16 @@  static void vfio_err_notifier_handler(void *opaque)
         int devfn;
 
         /*
+         * in case the real hardware configuration has been changed,
+         * here we should recheck the bus reset capability.
+         */
+        vfio_check_hot_bus_reset(vdev, &local_err);
+        if (local_err) {
+            error_report_err(local_err);
+            goto stop;
+        }
+
+        /*
          * If one device has aer capability on a bus, when aer occurred,
          * we should notify all devices on the bus there was an aer arrived,
          * then we are able to vote the device #0 to do host bus reset.
@@ -2638,15 +2653,42 @@  static void vfio_err_notifier_handler(void *opaque)
             tmp = DO_UPCAST(VFIOPCIDevice, pdev, dev);
             tmp->aer_occurred = true;
         }
+
+        /*
+         * we should read the error details from the real hardware
+         * configuration spaces, here we only need to do is signaling
+         * to guest an uncorrectable error has occurred.
+         */
+        if (pdev->exp.aer_cap) {
+            uint8_t *aer_cap = pdev->config + pdev->exp.aer_cap;
+            uint32_t uncor_status;
+            bool isfatal;
+
+            uncor_status = vfio_pci_read_config(pdev,
+                               pdev->exp.aer_cap + PCI_ERR_UNCOR_STATUS, 4);
+
+            /*
+             * if the error is not emitted by this device, we can
+             * just ignore it.
+             */
+            if (!(uncor_status & ~0UL)) {
+                return;
+            }
+
+            isfatal = uncor_status & pci_get_long(aer_cap + PCI_ERR_UNCOR_SEVER);
+
+            msg.severity = isfatal ? PCI_ERR_ROOT_CMD_FATAL_EN :
+                                     PCI_ERR_ROOT_CMD_NONFATAL_EN;
+
+            pcie_aer_msg(pdev, &msg);
+            return;
+        }
     }
 
+stop:
     /*
-     * TBD. Retrieve the error details and decide what action
-     * needs to be taken. One of the actions could be to pass
-     * the error to the guest and have the guest driver recover
-     * from the error. This requires that PCIe capabilities be
-     * exposed to the guest. For now, we just terminate the
-     * guest to contain the error.
+     * If the aer capability is not exposed to the guest. we just
+     * terminate the guest to contain the error.
      */
 
     error_report("%s(%s) Unrecoverable error detected. Please collect any data possible and then kill the guest", __func__, vdev->vbasedev.name);