From: "Longpeng(Mike)" via <qemu-devel@nongnu.org>
To: <alex.williamson@redhat.com>
Cc: <pbonzini@redhat.com>, <qemu-devel@nongnu.org>,
<kvm@vger.kernel.org>, <arei.gonglei@huawei.com>,
<huangzhichao@huawei.com>, <yechuan@huawei.com>,
"Longpeng(Mike)" <longpeng2@huawei.com>
Subject: [PATCH v6 3/5] vfio: simplify the failure path in vfio_msi_enable
Date: Sat, 26 Mar 2022 14:02:24 +0800 [thread overview]
Message-ID: <20220326060226.1892-4-longpeng2@huawei.com> (raw)
In-Reply-To: <20220326060226.1892-1-longpeng2@huawei.com>
Use vfio_msi_disable_common to simplify the error handling
in vfio_msi_enable.
Signed-off-by: Longpeng(Mike) <longpeng2@huawei.com>
---
hw/vfio/pci.c | 16 ++--------------
1 file changed, 2 insertions(+), 14 deletions(-)
diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
index a1916e2e36..6f49e71cd4 100644
--- a/hw/vfio/pci.c
+++ b/hw/vfio/pci.c
@@ -47,6 +47,7 @@
static void vfio_disable_interrupts(VFIOPCIDevice *vdev);
static void vfio_mmap_set_enabled(VFIOPCIDevice *vdev, bool enabled);
+static void vfio_msi_disable_common(VFIOPCIDevice *vdev);
/*
* Disabling BAR mmaping can be slow, but toggling it around INTx can
@@ -658,24 +659,12 @@ retry:
"MSI vectors, retry with %d", vdev->nr_vectors, ret);
}
- for (i = 0; i < vdev->nr_vectors; i++) {
- VFIOMSIVector *vector = &vdev->msi_vectors[i];
- if (vector->virq >= 0) {
- vfio_remove_kvm_msi_virq(vector);
- }
- qemu_set_fd_handler(event_notifier_get_fd(&vector->interrupt),
- NULL, NULL, NULL);
- event_notifier_cleanup(&vector->interrupt);
- }
-
- g_free(vdev->msi_vectors);
- vdev->msi_vectors = NULL;
+ vfio_msi_disable_common(vdev);
if (ret > 0) {
vdev->nr_vectors = ret;
goto retry;
}
- vdev->nr_vectors = 0;
/*
* Failing to setup MSI doesn't really fall within any specification.
@@ -683,7 +672,6 @@ retry:
* out to fall back to INTx for this device.
*/
error_report("vfio: Error: Failed to enable MSI");
- vdev->interrupt = VFIO_INT_NONE;
return;
}
--
2.23.0
next prev parent reply other threads:[~2022-03-26 6:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 6:02 [PATCH v6 0/5] optimize the downtime for vfio migration Longpeng(Mike) via
2022-03-26 6:02 ` [PATCH v6 1/5] vfio: simplify the conditional statements in vfio_msi_enable Longpeng(Mike) via
2022-03-26 6:02 ` [PATCH v6 2/5] vfio: move re-enabling INTX out of the common helper Longpeng(Mike) via
2022-03-26 6:02 ` Longpeng(Mike) via [this message]
2022-03-26 6:02 ` [PATCH v6 4/5] Revert "vfio: Avoid disabling and enabling vectors repeatedly in VFIO migration" Longpeng(Mike) via
2022-03-26 6:02 ` [PATCH v6 5/5] vfio: defer to commit kvm irq routing when enable msi/msix Longpeng(Mike) via
2022-03-28 20:12 ` [PATCH v6 0/5] optimize the downtime for vfio migration Alex Williamson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220326060226.1892-4-longpeng2@huawei.com \
--to=qemu-devel@nongnu.org \
--cc=alex.williamson@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=huangzhichao@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=longpeng2@huawei.com \
--cc=pbonzini@redhat.com \
--cc=yechuan@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).