From: Jason Gunthorpe <jgg@nvidia.com>
To: Josua Mayer <josua@solid-run.com>
Cc: "iommu@lists.linux.dev" <iommu@lists.linux.dev>,
Joerg Roedel <joro@8bytes.org>,
Robin Murphy <robin.murphy@arm.com>,
Will Deacon <will@kernel.org>, Kevin Tian <kevin.tian@intel.com>,
"patches@lists.linux.dev" <patches@lists.linux.dev>,
Samiullah Khawaja <skhawaja@google.com>,
Rabeeh Khoury <rabeeh@solid-run.com>,
Yazan Shhady <yazan.shhady@solid-run.com>,
Jon Nettleton <jon@solid-run.com>,
Mikhail Anikin <mikhail.anikin@solid-run.com>
Subject: Re: [PATCH v3 2/2] iommupt: Avoid rewalking during map
Date: Sat, 9 May 2026 20:39:59 -0300 [thread overview]
Message-ID: <20260509233959.GN9254@nvidia.com> (raw)
In-Reply-To: <ac1aae2d-9b5a-488b-aad7-7be542ec8102@solid-run.com>
On Sat, May 09, 2026 at 08:25:36PM +0000, Josua Mayer wrote:
> I applied this on top of the problematic commit, and my system boots fine now!
>
> When I compare the bad boot log, the good one, and the current one with above change,
> only the bad one is missing the following line from boot log:
>
> iommusmmu.0x0000000005000000: IOMMU driver was not able to establish FW requested direct mapping.
Ahhh. Now it makes sense. This is happening because SMMUv2 hasn't been
updated to create a domain that can immediately be mapped so you get
this message and the error propagation retries it after attaching the
domain. Since that got broke it never retried and the RMR was not
established.
Thanks,
Jason
next prev parent reply other threads:[~2026-05-09 23:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 19:30 [PATCH v3 0/2] Let iommupt manage changes in page size internally Jason Gunthorpe
2026-02-27 19:30 ` [PATCH v3 1/2] iommupt: Directly call iommupt's unmap_range() Jason Gunthorpe
2026-02-27 19:30 ` [PATCH v3 2/2] iommupt: Avoid rewalking during map Jason Gunthorpe
2026-05-09 17:41 ` Josua Mayer
2026-05-09 19:40 ` Jason Gunthorpe
2026-05-09 20:25 ` Josua Mayer
2026-05-09 23:39 ` Jason Gunthorpe [this message]
2026-03-03 3:55 ` [PATCH v3 0/2] Let iommupt manage changes in page size internally Baolu Lu
2026-03-17 12:58 ` Joerg Roedel
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=20260509233959.GN9254@nvidia.com \
--to=jgg@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=jon@solid-run.com \
--cc=joro@8bytes.org \
--cc=josua@solid-run.com \
--cc=kevin.tian@intel.com \
--cc=mikhail.anikin@solid-run.com \
--cc=patches@lists.linux.dev \
--cc=rabeeh@solid-run.com \
--cc=robin.murphy@arm.com \
--cc=skhawaja@google.com \
--cc=will@kernel.org \
--cc=yazan.shhady@solid-run.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