From: "Cédric Le Goater" <clg@redhat.com>
To: Joao Martins <joao.m.martins@oracle.com>,
Zhenzhong Duan <zhenzhong.duan@intel.com>,
qemu-devel@nongnu.org
Cc: alex.williamson@redhat.com, avihaih@nvidia.com, chao.p.peng@intel.com
Subject: Re: [PATCH v4 3/5] vfio/pci: Disable INTx in vfio_realize error path
Date: Thu, 29 Jun 2023 17:13:33 +0200 [thread overview]
Message-ID: <393d930c-da04-4c86-0f77-615c511df77b@redhat.com> (raw)
In-Reply-To: <29b6ecd3-d0a1-c914-9bba-cb99d95acd8d@oracle.com>
On 6/29/23 13:24, Joao Martins wrote:
> On 29/06/2023 09:40, Zhenzhong Duan wrote:
>> When vfio realize fails, INTx isn't disabled if it has been enabled.
>> This may confuse host side with unhandled interrupt report.
>>
>> Add a new label to be used for vfio_intx_enable() failed case.
>>
>> Fixes: a9994687cb9b ("vfio/display: core & wireup")
>> Fixes: b290659fc3dd ("hw/vfio/display: add ramfb support")
>> Fixes: c62a0c7ce34e ("vfio/display: add xres + yres properties")
>
> Sounds to me the correct Fixes tag is the same as first patch i.e.:
>
> Fixes: c5478fea27ac ("vfio/pci: Respond to KVM irqchip change notifier")
>
>> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
>
> Looks good, but see some clarifications below.
>
>> ---
>> hw/vfio/pci.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
>> index ab6645ba60af..54a8179d1c64 100644
>> --- a/hw/vfio/pci.c
>> +++ b/hw/vfio/pci.c
>> @@ -3167,7 +3167,7 @@ static void vfio_realize(PCIDevice *pdev, Error **errp)
>> kvm_irqchip_add_change_notifier(&vdev->irqchip_change_notifier);
>> ret = vfio_intx_enable(vdev, errp);
>> if (ret) {
>> - goto out_deregister;
>> + goto out_intx_disable;
>> }
>> }
>>
>> @@ -3220,6 +3220,8 @@ static void vfio_realize(PCIDevice *pdev, Error **errp)
>> return;
>>
>> out_deregister:
>> + vfio_disable_interrupts(vdev);
>
> You are calling vfio_disable_interrupts() when what you want is
> vfio_intx_disable() ? But I guess your thinking was to call
> vfio_disable_interrupt() which eventually calls vfio_intx_disable() in case INTx
> was really setup, thus saving the duplicated check. The MSIx/MSI in realize() I
> don't think they will be enabled at this point. Let me know if I misunderstood.
>
>> +out_intx_disable:
>
> Maybe 'out_intx_teardown' or 'out_intx_deregister' because you are not really
> disabling INTx.
or simply extract from vfio_disable_interrupts() :
if (vdev->interrupt == VFIO_INT_INTx) {
vfio_intx_disable(vdev);
}
and add the above code before cleaning up the intx routing
notifier without any new goto labels.
Thanks,
C.
>
>> pci_device_set_intx_routing_notifier(&vdev->pdev, NULL);
>> if (vdev->irqchip_change_notifier.notify) {
>> kvm_irqchip_remove_change_notifier(&vdev->irqchip_change_notifier);
>
next prev parent reply other threads:[~2023-06-29 15:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 8:40 [PATCH v4 0/5] VFIO migration related refactor and bug fix Zhenzhong Duan
2023-06-29 8:40 ` [PATCH v4 1/5] vfio/pci: Fix a segfault in vfio_realize Zhenzhong Duan
2023-06-29 10:57 ` Joao Martins
2023-06-29 13:06 ` Cédric Le Goater
2023-06-29 8:40 ` [PATCH v4 2/5] vfio/pci: Free leaked timer in vfio_realize error path Zhenzhong Duan
2023-06-29 10:59 ` Joao Martins
2023-06-29 13:09 ` Cédric Le Goater
2023-06-29 8:40 ` [PATCH v4 3/5] vfio/pci: Disable INTx " Zhenzhong Duan
2023-06-29 11:24 ` Joao Martins
2023-06-29 15:13 ` Cédric Le Goater [this message]
2023-06-29 15:33 ` Joao Martins
2023-06-30 1:19 ` Duan, Zhenzhong
2023-06-29 8:40 ` [PATCH v4 4/5] vfio/pci: Free resources when vfio_migration_realize fails Zhenzhong Duan
2023-06-29 11:45 ` Joao Martins
2023-06-29 15:23 ` Cédric Le Goater
2023-06-30 1:23 ` Duan, Zhenzhong
2023-06-29 8:40 ` [PATCH v4 5/5] vfio/migration: Refactor and fix print of "Migration disabled" Zhenzhong Duan
2023-06-29 12:44 ` Joao Martins
2023-06-29 15:20 ` Avihai Horon
2023-06-29 15:42 ` Joao Martins
2023-06-29 22:12 ` Alex Williamson
2023-06-30 1:38 ` Duan, Zhenzhong
2023-06-29 16:40 ` Cédric Le Goater
2023-06-30 1:40 ` Duan, Zhenzhong
2023-06-30 6:01 ` [PATCH v4 0/5] VFIO migration related refactor and bug fix Cédric Le Goater
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=393d930c-da04-4c86-0f77-615c511df77b@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=avihaih@nvidia.com \
--cc=chao.p.peng@intel.com \
--cc=joao.m.martins@oracle.com \
--cc=qemu-devel@nongnu.org \
--cc=zhenzhong.duan@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).