From: "Cédric Le Goater" <clg@redhat.com>
To: Pierrick Bouvier <pierrick.bouvier@linaro.org>, qemu-devel@nongnu.org
Cc: Richard Henderson <richard.henderson@linaro.org>,
eric.auger@redhat.com, Paolo Bonzini <pbonzini@redhat.com>,
philmd@linaro.org, qemu-ppc@nongnu.org
Subject: Re: [PATCH v5 4/8] hw/vfio: eradicate CONFIG_IOMMU from sources
Date: Thu, 19 Mar 2026 09:32:10 +0100 [thread overview]
Message-ID: <1a90bb09-9141-4fde-a8c4-87d82664da9e@redhat.com> (raw)
In-Reply-To: <20260318174733.1717643-5-pierrick.bouvier@linaro.org>
On 3/18/26 18:47, Pierrick Bouvier wrote:
> This commit removes usage of CONFIG_IOMMU in hw/vfio sources, exposing
> inconditionally iommufd related properties, which are declared
> statically (in const arrays). The alternative to expose them dynamically
> is more complex and requires boilerplate to set properties at runtime,
> with set_* callbacks and added logic to check if iommufd backend is
> available, with no obvious benefit.
>
> One possible difference is that user may see a different error message
> when trying to attach a vfio device with a QEMU not supporting iommufd,
> without declaring iommufd object associated.
>
> Instead of:
> ```
> $ qemu-system-* -device vfio-pci,host=0000:01:00.0,iommufd=iommufd0
> qemu-system-*: -device vfio-pci,host=0000:01:00.0,iommufd=iommufd0: Property 'vfio-pci.iommufd' not found
> ```
> User will now see:
> ```
> qemu-system-aarch64: -device vfio-pci,host=0000:01:00.0,iommufd=iommufd0: Device 'iommufd0' not found
> ```
>
> However, since declaring the iommufd object is needed, error reported
> before and after is still the same:
> ```
> $ qemu-system-* -object iommufd,id=iommufd0 -device vfio-pci,host=0000:01:00.0,iommufd=iommufd0
> qemu-system-*: invalid object type: iommufd
> ```
>
> Signed-off-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
> ---
> hw/vfio/ap.c | 9 ---------
> hw/vfio/ccw.c | 9 ---------
> hw/vfio/pci.c | 11 -----------
> 3 files changed, 29 deletions(-)
Reviewed-by: Cédric Le Goater <clg@redhat.com>
Thanks,
C.
next prev parent reply other threads:[~2026-03-19 8:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 17:47 [PATCH v5 0/8] hw/vfio: single-binary Pierrick Bouvier
2026-03-18 17:47 ` [PATCH v5 1/8] hw/vfio/listener.c: remove CONFIG_KVM Pierrick Bouvier
2026-03-18 17:47 ` [PATCH v5 2/8] hw/vfio/helpers.c: extract kvm helpers in kvm-helpers.c Pierrick Bouvier
2026-03-18 17:47 ` [PATCH v5 3/8] hw/vfio/pci-quirks.c: remove CONFIG_VFIO_IGD Pierrick Bouvier
2026-03-18 17:47 ` [PATCH v5 4/8] hw/vfio: eradicate CONFIG_IOMMU from sources Pierrick Bouvier
2026-03-19 8:32 ` Cédric Le Goater [this message]
2026-03-18 17:47 ` [PATCH v5 5/8] hw/vfio/pci.c: eradicate CONFIG_KVM Pierrick Bouvier
2026-03-19 8:33 ` Cédric Le Goater
2026-03-18 17:47 ` [PATCH v5 6/8] hw/vfio/ap.c: use full path for target specific header Pierrick Bouvier
2026-03-18 17:47 ` [PATCH v5 7/8] hw/vfio/spapr.c: extract vfio_spapr_kvm_attach_tce to hw/vfio/kvm-spapr.c Pierrick Bouvier
2026-03-19 8:32 ` Cédric Le Goater
2026-03-18 17:47 ` [PATCH v5 8/8] hw/vfio: all vfio files can now be common files Pierrick Bouvier
2026-03-19 7:45 ` [PATCH v5 0/8] hw/vfio: single-binary Philippe Mathieu-Daudé
2026-03-19 8:33 ` 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=1a90bb09-9141-4fde-a8c4-87d82664da9e@redhat.com \
--to=clg@redhat.com \
--cc=eric.auger@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=richard.henderson@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.