From: "Cédric Le Goater" <clg@redhat.com>
To: Tomita Moeko <tomitamoeko@gmail.com>,
Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel@nongnu.org, "Corvin Köhne" <c.koehne@beckhoff.com>,
edmund.raile@proton.me,
"Edmund Raile" <edmund.raile@protonmail.com>
Subject: Re: [PATCH v2] vfio/igd: Fix incorrect error propagation in vfio_pci_igd_opregion_detect()
Date: Mon, 26 May 2025 18:57:04 +0200 [thread overview]
Message-ID: <22265d1d-207b-4e84-bd4d-7a2f56cb1348@redhat.com> (raw)
In-Reply-To: <20250522151636.20001-1-tomitamoeko@gmail.com>
On 5/22/25 17:16, Tomita Moeko wrote:
> In vfio_pci_igd_opregion_detect(), errp will be set when the device does
> not have OpRegion or is hotplugged. This errp will be propagated to
> pci_qdev_realize(), which interprets it as failure, causing unexpected
> termination on devices without OpRegion like SR-IOV VFs or discrete
> GPUs. Fix it by not setting errp in vfio_pci_igd_opregion_detect().
>
> This patch also checks if the device has OpRegion before hotplug status
> to prevent unwanted warning messages on non-IGD devices.
>
> Fixes: c0273e77f2d7 ("vfio/igd: Detect IGD device by OpRegion")
> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2968
> Reported-by: Edmund Raile <edmund.raile@protonmail.com>
> Link: https://lore.kernel.org/qemu-devel/30044d14-17ec-46e3-b9c3-63d27a5bde27@gmail.com
> Tested-by: Edmund Raile <edmund.raile@protonmail.com>
> Signed-off-by: Tomita Moeko <tomitamoeko@gmail.com>
> ---
> v2:
> * Add Tested-by from Edmund Raile. Thanks for the contribution.
> * Rebased on vfio-next
> * Fix typos.
Edmund, Alex,
Could you please send a R-b ?
Thanks,
C.
> hw/vfio/igd.c | 22 ++++++++++------------
> 1 file changed, 10 insertions(+), 12 deletions(-)
>
> diff --git a/hw/vfio/igd.c b/hw/vfio/igd.c
> index 5b6341c5bf..e7a9d1ffc1 100644
> --- a/hw/vfio/igd.c
> +++ b/hw/vfio/igd.c
> @@ -187,23 +187,21 @@ static bool vfio_pci_igd_opregion_init(VFIOPCIDevice *vdev,
> }
>
> static bool vfio_pci_igd_opregion_detect(VFIOPCIDevice *vdev,
> - struct vfio_region_info **opregion,
> - Error **errp)
> + struct vfio_region_info **opregion)
> {
> int ret;
>
> - /* Hotplugging is not supported for opregion access */
> - if (vdev->pdev.qdev.hotplugged) {
> - error_setg(errp, "IGD OpRegion is not supported on hotplugged device");
> - return false;
> - }
> -
> ret = vfio_device_get_region_info_type(&vdev->vbasedev,
> VFIO_REGION_TYPE_PCI_VENDOR_TYPE | PCI_VENDOR_ID_INTEL,
> VFIO_REGION_SUBTYPE_INTEL_IGD_OPREGION, opregion);
> if (ret) {
> - error_setg_errno(errp, -ret,
> - "Device does not support IGD OpRegion feature");
> + return false;
> + }
> +
> + /* Hotplugging is not supported for opregion access */
> + if (vdev->pdev.qdev.hotplugged) {
> + warn_report("IGD device detected, but OpRegion is not supported "
> + "on hotplugged device.");
> return false;
> }
>
> @@ -524,7 +522,7 @@ static bool vfio_pci_igd_config_quirk(VFIOPCIDevice *vdev, Error **errp)
> }
>
> /* IGD device always comes with OpRegion */
> - if (!vfio_pci_igd_opregion_detect(vdev, &opregion, errp)) {
> + if (!vfio_pci_igd_opregion_detect(vdev, &opregion)) {
> return true;
> }
> info_report("OpRegion detected on Intel display %x.", vdev->device_id);
> @@ -695,7 +693,7 @@ static bool vfio_pci_kvmgt_config_quirk(VFIOPCIDevice *vdev, Error **errp)
> return true;
> }
>
> - if (!vfio_pci_igd_opregion_detect(vdev, &opregion, errp)) {
> + if (!vfio_pci_igd_opregion_detect(vdev, &opregion)) {
> /* Should never reach here, KVMGT always emulates OpRegion */
> return false;
> }
next prev parent reply other threads:[~2025-05-26 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 15:16 [PATCH v2] vfio/igd: Fix incorrect error propagation in vfio_pci_igd_opregion_detect() Tomita Moeko
2025-05-26 16:57 ` Cédric Le Goater [this message]
2025-05-27 7:42 ` Corvin Köhne
2025-05-27 7:59 ` Cédric Le Goater
2025-05-27 19:27 ` 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=22265d1d-207b-4e84-bd4d-7a2f56cb1348@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=c.koehne@beckhoff.com \
--cc=edmund.raile@proton.me \
--cc=edmund.raile@protonmail.com \
--cc=qemu-devel@nongnu.org \
--cc=tomitamoeko@gmail.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).