From: Eric Auger <eric.auger@redhat.com>
To: Zhenzhong Duan <zhenzhong.duan@intel.com>,
qemu-devel@nongnu.org, qemu-arm@nongnu.org
Cc: jean-philippe@linaro.org, alex.williamson@redhat.com,
clg@redhat.com, peterx@redhat.com, jasowang@redhat.com,
mst@redhat.com, yi.l.liu@intel.com, chao.p.peng@intel.com
Subject: Re: [PATCH 3/3] virtio-iommu: Support PCI device aliases
Date: Wed, 24 Jan 2024 21:55:47 +0100 [thread overview]
Message-ID: <afbb95d3-f18e-47d1-bb4f-ebcc89514c21@redhat.com> (raw)
In-Reply-To: <20240122064015.94630-4-zhenzhong.duan@intel.com>
Hi Zhenzhong,
On 1/22/24 07:40, Zhenzhong Duan wrote:
> Currently virtio-iommu doesn't work well if there are multiple devices
> in same iommu group. In below example config, guest virtio-iommu driver
> can successfully probe first device but fail on others. Only one device
> under the bridge can work normally.
>
> -device virtio-iommu \
> -device pcie-pci-bridge,id=root0 \
> -device vfio-pci,host=81:11.0,bus=root0 \
> -device vfio-pci,host=6f:01.0,bus=root0 \
>
> The reason is virtio-iommu stores AS(address space) in hash table with
> aliased BDF and corelates endpoint which is indexed by device's real
> BDF, i.e., virtio_iommu_mr() is passed a real BDF to lookup AS hash
> table, we either get wrong AS or NULL.
>
> Fix it by storing AS indexed by real BDF. This way also make iova_ranges
> from vfio device stored in IOMMUDevice of real BDF successfully.
>
> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
> ---
> hw/virtio/virtio-iommu.c | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/hw/virtio/virtio-iommu.c b/hw/virtio/virtio-iommu.c
> index d99c1f0d64..6880d92a44 100644
> --- a/hw/virtio/virtio-iommu.c
> +++ b/hw/virtio/virtio-iommu.c
> @@ -399,27 +399,27 @@ static AddressSpace *virtio_iommu_find_add_as(PCIBus *bus, void *opaque,
> int real_devfn)
> {
> VirtIOIOMMU *s = opaque;
> - IOMMUPciBus *sbus = g_hash_table_lookup(s->as_by_busptr, bus);
> + IOMMUPciBus *sbus = g_hash_table_lookup(s->as_by_busptr, real_bus);
> static uint32_t mr_index;
> IOMMUDevice *sdev;
>
> if (!sbus) {
> sbus = g_malloc0(sizeof(IOMMUPciBus) +
> sizeof(IOMMUDevice *) * PCI_DEVFN_MAX);
> - sbus->bus = bus;
> - g_hash_table_insert(s->as_by_busptr, bus, sbus);
> + sbus->bus = real_bus;
> + g_hash_table_insert(s->as_by_busptr, real_bus, sbus);
> }
>
> - sdev = sbus->pbdev[devfn];
> + sdev = sbus->pbdev[real_devfn];
> if (!sdev) {
> char *name = g_strdup_printf("%s-%d-%d",
> TYPE_VIRTIO_IOMMU_MEMORY_REGION,
> - mr_index++, devfn);
> - sdev = sbus->pbdev[devfn] = g_new0(IOMMUDevice, 1);
> + mr_index++, real_devfn);
> + sdev = sbus->pbdev[real_devfn] = g_new0(IOMMUDevice, 1);
>
> sdev->viommu = s;
> - sdev->bus = bus;
> - sdev->devfn = devfn;
> + sdev->bus = real_bus;
> + sdev->devfn = real_devfn;
but then this means the 2 devices would be abstracted by two different
IOMMU MRs whereas in practice they cannot be distinguished from an IOMMU
pov. Shouldn't the virtio-iommu driver use the same ep_id for both
devices within the same group?
Note there are some known issues about virtio-iommu and pcie-to-pci
bridges which were reported early last year and confirmed by Robin
Murphy. See:
[RFC] virtio-iommu: Take into account possible aliasing in virtio_iommu_mr() <https://lore.kernel.org/all/20230116124709.793084-1-eric.auger@redhat.com/#r>
https://lore.kernel.org/all/20230116124709.793084-1-eric.auger@redhat.com/
Thanks
Eric
>
> trace_virtio_iommu_init_iommu_mr(name);
>
next prev parent reply other threads:[~2024-01-24 20:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 6:40 [PATCH 0/3] Two minor fixes on virtio-iommu Zhenzhong Duan
2024-01-22 6:40 ` [PATCH 1/3] virtio_iommu: Clear IOMMUPciBus pointer cache when system reset Zhenzhong Duan
2024-01-23 9:41 ` Cédric Le Goater
2024-01-23 10:03 ` Duan, Zhenzhong
2024-01-24 21:04 ` Eric Auger
2024-01-25 2:46 ` Duan, Zhenzhong
2024-01-22 6:40 ` [PATCH 2/3] hw/pci: Add two parameters to get_address_space Zhenzhong Duan
2024-01-22 6:40 ` [PATCH 3/3] virtio-iommu: Support PCI device aliases Zhenzhong Duan
2024-01-24 20:55 ` Eric Auger [this message]
2024-01-25 5:58 ` Duan, Zhenzhong
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=afbb95d3-f18e-47d1-bb4f-ebcc89514c21@redhat.com \
--to=eric.auger@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=chao.p.peng@intel.com \
--cc=clg@redhat.com \
--cc=jasowang@redhat.com \
--cc=jean-philippe@linaro.org \
--cc=mst@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=yi.l.liu@intel.com \
--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).