From: "Cédric Le Goater" <clg@redhat.com>
To: Jing Liu <jing2.liu@intel.com>, qemu-devel@nongnu.org
Cc: alex.williamson@redhat.com, pbonzini@redhat.com,
kevin.tian@intel.com, reinette.chatre@intel.com,
jing2.liu@linux.intel.com
Subject: Re: [PATCH v2 3/4] vfio/pci: use an invalid fd to enable MSI-X
Date: Tue, 19 Sep 2023 17:18:33 +0200 [thread overview]
Message-ID: <4ffebb9f-8453-169b-f617-05414fc717b4@redhat.com> (raw)
In-Reply-To: <20230918094507.409050-4-jing2.liu@intel.com>
On 9/18/23 11:45, Jing Liu wrote:
> Guests typically enable MSI-X with all of the vectors masked in the MSI-X
> vector table. To match the guest state of device, QEMU enables MSI-X by
> enabling vector 0 with userspace triggering and immediately release.
> However the release function actually does not release it due to already
> using userspace mode.
>
> It is no need to enable triggering on host and rely on the mask bit to
> avoid spurious interrupts. Use an invalid fd (i.e. fd = -1) is enough
> to get MSI-X enabled.
>
> After dynamic MSI-X allocation is supported, the interrupt restoring
> also need use such way to enable MSI-X, therefore, create a function
> for that.
>
> Suggested-by: Alex Williamson <alex.williamson@redhat.com>
> Signed-off-by: Jing Liu <jing2.liu@intel.com>
Reviewed-by: Cédric Le Goater <clg@redhat.com>
Thanks,
C.
> ---
> Changes since v1:
> - Revise Qemu to QEMU. (Cédric)
> - Use g_autofree to automatically release. (Cédric)
> - Just return 'ret' and let the caller of vfio_enable_msix_no_vec()
> report the error. (Cédric)
>
> Changes since RFC v1:
> - A new patch. Use an invalid fd to get MSI-X enabled instead of using
> userspace triggering. (Alex)
> ---
> hw/vfio/pci.c | 44 ++++++++++++++++++++++++++++++++++++--------
> 1 file changed, 36 insertions(+), 8 deletions(-)
>
> diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
> index 84987e46fd7a..0117f230e934 100644
> --- a/hw/vfio/pci.c
> +++ b/hw/vfio/pci.c
> @@ -369,6 +369,33 @@ static void vfio_msi_interrupt(void *opaque)
> notify(&vdev->pdev, nr);
> }
>
> +/*
> + * Get MSI-X enabled, but no vector enabled, by setting vector 0 with an invalid
> + * fd to kernel.
> + */
> +static int vfio_enable_msix_no_vec(VFIOPCIDevice *vdev)
> +{
> + g_autofree struct vfio_irq_set *irq_set = NULL;
> + int ret = 0, argsz;
> + int32_t *fd;
> +
> + argsz = sizeof(*irq_set) + sizeof(*fd);
> +
> + irq_set = g_malloc0(argsz);
> + irq_set->argsz = argsz;
> + irq_set->flags = VFIO_IRQ_SET_DATA_EVENTFD |
> + VFIO_IRQ_SET_ACTION_TRIGGER;
> + irq_set->index = VFIO_PCI_MSIX_IRQ_INDEX;
> + irq_set->start = 0;
> + irq_set->count = 1;
> + fd = (int32_t *)&irq_set->data;
> + *fd = -1;
> +
> + ret = ioctl(vdev->vbasedev.fd, VFIO_DEVICE_SET_IRQS, irq_set);
> +
> + return ret;
> +}
> +
> static int vfio_enable_vectors(VFIOPCIDevice *vdev, bool msix)
> {
> struct vfio_irq_set *irq_set;
> @@ -618,6 +645,8 @@ static void vfio_commit_kvm_msi_virq_batch(VFIOPCIDevice *vdev)
>
> static void vfio_msix_enable(VFIOPCIDevice *vdev)
> {
> + int ret;
> +
> vfio_disable_interrupts(vdev);
>
> vdev->msi_vectors = g_new0(VFIOMSIVector, vdev->msix->entries);
> @@ -640,8 +669,6 @@ static void vfio_msix_enable(VFIOPCIDevice *vdev)
> vfio_commit_kvm_msi_virq_batch(vdev);
>
> if (vdev->nr_vectors) {
> - int ret;
> -
> ret = vfio_enable_vectors(vdev, true);
> if (ret) {
> error_report("vfio: failed to enable vectors, %d", ret);
> @@ -655,13 +682,14 @@ static void vfio_msix_enable(VFIOPCIDevice *vdev)
> * MSI-X capability, but leaves the vector table masked. We therefore
> * can't rely on a vector_use callback (from request_irq() in the guest)
> * to switch the physical device into MSI-X mode because that may come a
> - * long time after pci_enable_msix(). This code enables vector 0 with
> - * triggering to userspace, then immediately release the vector, leaving
> - * the physical device with no vectors enabled, but MSI-X enabled, just
> - * like the guest view.
> + * long time after pci_enable_msix(). This code sets vector 0 with an
> + * invalid fd to make the physical device MSI-X enabled, but with no
> + * vectors enabled, just like the guest view.
> */
> - vfio_msix_vector_do_use(&vdev->pdev, 0, NULL, NULL);
> - vfio_msix_vector_release(&vdev->pdev, 0);
> + ret = vfio_enable_msix_no_vec(vdev);
> + if (ret) {
> + error_report("vfio: failed to enable MSI-X, %d", ret);
> + }
> }
>
> trace_vfio_msix_enable(vdev->vbasedev.name);
next prev parent reply other threads:[~2023-09-19 15:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 9:45 [PATCH v2 0/4] Support dynamic MSI-X allocation Jing Liu
2023-09-18 9:45 ` [PATCH v2 1/4] vfio/pci: detect the support of " Jing Liu
2023-09-18 9:45 ` [PATCH v2 2/4] vfio/pci: enable vector on " Jing Liu
2023-09-22 20:54 ` Alex Williamson
2023-09-25 6:04 ` Liu, Jing2
2023-09-18 9:45 ` [PATCH v2 3/4] vfio/pci: use an invalid fd to enable MSI-X Jing Liu
2023-09-19 15:18 ` Cédric Le Goater [this message]
2023-09-18 9:45 ` [PATCH v2 4/4] vfio/pci: enable MSI-X in interrupt restoring on dynamic allocation Jing Liu
2023-09-19 15:21 ` Cédric Le Goater
2023-09-21 6:48 ` Liu, Jing2
2023-09-22 20:56 ` [PATCH v2 0/4] Support dynamic MSI-X allocation Alex Williamson
2023-09-25 6:10 ` Liu, Jing2
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=4ffebb9f-8453-169b-f617-05414fc717b4@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=jing2.liu@intel.com \
--cc=jing2.liu@linux.intel.com \
--cc=kevin.tian@intel.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=reinette.chatre@intel.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).