From: "Cédric Le Goater" <clg@redhat.com>
To: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
alex.williamson@redhat.com
Cc: qemu-devel@nongnu.org, chenxiang66@hisilicon.com,
longpeng2@huawei.com, linuxarm@huawei.com
Subject: Re: [PATCH] vfio/pci: Call vfio_prepare_kvm_msi_virq_batch() in MSI retry path
Date: Tue, 20 Jun 2023 16:43:50 +0200 [thread overview]
Message-ID: <65bfc353-c348-6810-6e06-f7237c9ad621@redhat.com> (raw)
In-Reply-To: <20230613140943.1786-1-shameerali.kolothum.thodi@huawei.com>
Hello Shameer,
On 6/13/23 16:09, Shameer Kolothum wrote:
> When vfio_enable_vectors() returns with less than requested nr_vectors
> we retry with what kernel reported back. But the retry path doesn't
> call vfio_prepare_kvm_msi_virq_batch() and this results in,
>
> qemu-system-aarch64: vfio: Error: Failed to enable 4 MSI vectors, retry with 1
> qemu-system-aarch64: ../hw/vfio/pci.c:602: vfio_commit_kvm_msi_virq_batch: Assertion `vdev->defer_kvm_irq_routing' failed
>
> Fixes: dc580d51f7dd ("vfio: defer to commit kvm irq routing when enable msi/msix")
> Reviewed-by: Longpeng <longpeng2@huawei.com>
> Signed-off-by: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
Looks correct to me,
Reviewed-by: Cédric Le Goater <clg@redhat.com>
Thanks,
C.
> ---
> hw/vfio/pci.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
> index 73874a94de..8fb2c53a63 100644
> --- a/hw/vfio/pci.c
> +++ b/hw/vfio/pci.c
> @@ -663,6 +663,8 @@ static void vfio_msi_enable(VFIOPCIDevice *vdev)
>
> vfio_disable_interrupts(vdev);
>
> + vdev->nr_vectors = msi_nr_vectors_allocated(&vdev->pdev);
> +retry:
> /*
> * Setting vector notifiers needs to enable route for each vector.
> * Deferring to commit the KVM routes once rather than per vector
> @@ -670,8 +672,6 @@ static void vfio_msi_enable(VFIOPCIDevice *vdev)
> */
> vfio_prepare_kvm_msi_virq_batch(vdev);
>
> - vdev->nr_vectors = msi_nr_vectors_allocated(&vdev->pdev);
> -retry:
> vdev->msi_vectors = g_new0(VFIOMSIVector, vdev->nr_vectors);
>
> for (i = 0; i < vdev->nr_vectors; i++) {
prev parent reply other threads:[~2023-06-20 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 14:09 [PATCH] vfio/pci: Call vfio_prepare_kvm_msi_virq_batch() in MSI retry path Shameer Kolothum via
2023-06-20 14:43 ` Cédric Le Goater [this message]
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=65bfc353-c348-6810-6e06-f7237c9ad621@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=chenxiang66@hisilicon.com \
--cc=linuxarm@huawei.com \
--cc=longpeng2@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=shameerali.kolothum.thodi@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).