From: Shameerali Kolothum Thodi via <qemu-devel@nongnu.org>
To: Zhangfei Gao <zhangfei.gao@linaro.org>, Jason Gunthorpe <jgg@nvidia.com>
Cc: Nicolin Chen <nicolinc@nvidia.com>,
Eric Auger <eric.auger@redhat.com>,
Mostafa Saleh <smostafa@google.com>,
"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
Moritz Fischer <mdf@kernel.org>,
Michael Shavit <mshavit@google.com>,
Andrea Bolognani <abologna@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Peter Xu <peterx@redhat.com>,
"nathanc@nvidia.com" <nathanc@nvidia.com>,
"arighi@nvidia.com" <arighi@nvidia.com>,
"ianm@nvidia.com" <ianm@nvidia.com>,
"jan@nvidia.com" <jan@nvidia.com>,
"mochs@nvidia.com" <mochs@nvidia.com>
Subject: RE: nested-smmuv3 topic for QEMU/libvirt, Nov 2024
Date: Mon, 2 Dec 2024 08:07:14 +0000 [thread overview]
Message-ID: <8f9d105371be44f1a1f6ba0f268d8c68@huawei.com> (raw)
In-Reply-To: <CABQgh9E3ba1F_4bTxkzRmt0sDmyVR+hbxocnqSvrvwerFZwiug@mail.gmail.com>
> -----Original Message-----
> From: Zhangfei Gao <zhangfei.gao@linaro.org>
> Sent: Monday, December 2, 2024 6:05 AM
> To: Jason Gunthorpe <jgg@nvidia.com>
> Cc: Nicolin Chen <nicolinc@nvidia.com>; Shameerali Kolothum Thodi
> <shameerali.kolothum.thodi@huawei.com>; Eric Auger
> <eric.auger@redhat.com>; Mostafa Saleh <smostafa@google.com>; qemu-
> arm@nongnu.org; qemu-devel@nongnu.org; Peter Maydell
> <peter.maydell@linaro.org>; Jean-Philippe Brucker <jean-
> philippe@linaro.org>; Moritz Fischer <mdf@kernel.org>; Michael Shavit
> <mshavit@google.com>; Andrea Bolognani <abologna@redhat.com>;
> Michael S. Tsirkin <mst@redhat.com>; Peter Xu <peterx@redhat.com>;
> nathanc@nvidia.com; arighi@nvidia.com; ianm@nvidia.com;
> jan@nvidia.com; mochs@nvidia.com
> Subject: Re: nested-smmuv3 topic for QEMU/libvirt, Nov 2024
>
> Hi, Nico
>
> On Fri, 1 Nov 2024 at 19:55, Jason Gunthorpe <jgg@nvidia.com> wrote:
> >
> > On Thu, Oct 31, 2024 at 09:09:20PM -0700, Nicolin Chen wrote:
> >
> > > FWIW, Robin requested a different solution for MSI mapping [1], v.s.
> > > the RMR one that we have been using since Eric's work. I drafted a
> > > few VFIO/IOMMUFD patches for that,
> >
> > I also talked to MarcZ about this at LPC and he seems willing to
> > consider it. It took a bit to explain everything though. So I think we
> > should try in Nov/Dec
>
> When boot qemu, reports this
>
> qemu-system-aarch64: warning: IOMMU_IOAS_MAP failed: Bad address, PCI
> BAR?
> qemu-system-aarch64: vfio_container_dma_map(0xaaaadd30f110,
> 0x8000200000, 0x10000, 0xffffb8031000) = -14 (Bad address)
> qemu-system-aarch64: warning: IOMMU_IOAS_MAP failed: Bad address, PCI
> BAR?
> qemu-system-aarch64: vfio_container_dma_map(0xaaaadd2bc310,
> 0x8000200000, 0x10000, 0xffffb8031000) = -14 (Bad address)
> qemu-system-aarch64: warning: IOMMU_IOAS_MAP failed: Bad address, PCI
> BAR?
> qemu-system-aarch64: vfio_container_dma_map(0xaaaadcf90000,
> 0x8000200000, 0x10000, 0xffffb8031000) = -14 (Bad address)
>
> Will this also be solved in the new MSI mapping patchset?
Nope. These are not related to MSIs. These mappings are required for
P2P DMA between devices and is not supported by IOMMUFD at the moment.
See the discussion here,
https://lore.kernel.org/all/20220426103507.5693a0ca.alex.williamson@redhat.com/
Thanks,
Shameer
next prev parent reply other threads:[~2024-12-02 8:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 4:09 nested-smmuv3 topic for QEMU/libvirt, Nov 2024 Nicolin Chen
2024-11-01 11:55 ` Jason Gunthorpe
2024-12-02 6:04 ` Zhangfei Gao
2024-12-02 8:07 ` Shameerali Kolothum Thodi via [this message]
2024-12-02 15:00 ` Zhangfei Gao
2024-11-01 18:35 ` Shameerali Kolothum Thodi via
2024-11-01 19:29 ` Nicolin Chen
2024-11-08 13:05 ` Shameerali Kolothum Thodi via
2024-11-20 21:13 ` Andrea Bolognani
2024-11-21 9:47 ` Shameerali Kolothum Thodi via
2024-11-07 11:11 ` Eric Auger
2024-11-07 20:31 ` Nicolin Chen
2024-11-07 22:10 ` Donald Dutile
2024-11-18 17:59 ` Eric Auger
2024-11-19 7:07 ` Duan, Zhenzhong
2024-11-19 8:17 ` Eric Auger
2024-11-20 20:44 ` Nicolin Chen
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=8f9d105371be44f1a1f6ba0f268d8c68@huawei.com \
--to=qemu-devel@nongnu.org \
--cc=abologna@redhat.com \
--cc=arighi@nvidia.com \
--cc=eric.auger@redhat.com \
--cc=ianm@nvidia.com \
--cc=jan@nvidia.com \
--cc=jean-philippe@linaro.org \
--cc=jgg@nvidia.com \
--cc=mdf@kernel.org \
--cc=mochs@nvidia.com \
--cc=mshavit@google.com \
--cc=mst@redhat.com \
--cc=nathanc@nvidia.com \
--cc=nicolinc@nvidia.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=smostafa@google.com \
--cc=zhangfei.gao@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 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).