vfio/pci: Update stale comment

In preparation for surrounding code change it is helpful to
ensure that existing comments are accurate.

Remove inaccurate comment about direct access and update
the rest of the comment to reflect the purpose of writing
the cached MSI message to the device.

Suggested-by: Alex Williamson <alex.williamson@redhat.com>
Link: https://lore.kernel.org/lkml/20230330164050.0069e2a5.alex.williamson@redhat.com/
Signed-off-by: Reinette Chatre <reinette.chatre@intel.com>
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
Link: https://lore.kernel.org/r/5b605ce7dcdab5a5dfef19cec4d73ae2fdad3ae1.1683740667.git.reinette.chatre@intel.com
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>

diff --git a/drivers/vfio/pci/vfio_pci_intrs.c b/drivers/vfio/pci/vfio_pci_intrs.c
index e40eca69a293768bb3e05aafc9d779e36f7d5ec7..867327e159c1e6c00719818122a0f3ad1fecfe03 100644 (file)
--- a/drivers/vfio/pci/vfio_pci_intrs.c
+++ b/drivers/vfio/pci/vfio_pci_intrs.c
@@ -428,11 +428,9 @@ static int vfio_msi_set_vector_signal(struct vfio_pci_core_device *vdev,
        }
 
        /*
-        * The MSIx vector table resides in device memory which may be cleared
-        * via backdoor resets. We don't allow direct access to the vector
-        * table so even if a userspace driver attempts to save/restore around
-        * such a reset it would be unsuccessful. To avoid this, restore the
-        * cached value of the message prior to enabling.
+        * If the vector was previously allocated, refresh the on-device
+        * message data before enabling in case it had been cleared or
+        * corrupted (e.g. due to backdoor resets) since writing.
         */
        cmd = vfio_pci_memory_lock_and_enable(vdev);
        if (msix) {