From: Jason Gunthorpe <jgg@ziepe.ca>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Hector Martin <marcan@marcan.st>, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Jerry Snitselaar <jsnitsel@redhat.com>,
Joerg Roedel <jroedel@suse.de>, Neal Gompa <neal@gompa.dev>,
"Justin M. Forbes" <jforbes@fedoraproject.org>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
asahi@lists.linux.dev, stable@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: [PATCH REGRESSION] iommu: Only allocate FQ domains for IOMMUs that support them
Date: Fri, 22 Sep 2023 11:42:22 -0300 [thread overview]
Message-ID: <20230922144222.GF13795@ziepe.ca> (raw)
In-Reply-To: <2ea199a1-d20d-2fde-d1bd-76ecad14a68d@arm.com>
On Fri, Sep 22, 2023 at 03:21:17PM +0100, Robin Murphy wrote:
> On 22/09/2023 2:40 pm, Hector Martin wrote:
> > Commit a4fdd9762272 ("iommu: Use flush queue capability") hid the
> > IOMMU_DOMAIN_DMA_FQ domain type from domain allocation. A check was
> > introduced in iommu_dma_init_domain() to fall back if not supported, but
> > this check runs too late: by that point, devices have been attached to
> > the IOMMU, and the IOMMU driver might not expect FQ domains at
> > ops->attach_dev() time.
> >
> > Ensure that we immediately clamp FQ domains to plain DMA if not
> > supported by the driver at device attach time, not later.
> >
> > This regressed apple-dart in v6.5.
>
> Apologies, I missed that apple-dart was doing something unusual here.
> However, could we just fix that directly instead?
>
> diff --git a/drivers/iommu/apple-dart.c b/drivers/iommu/apple-dart.c
> index 2082081402d3..0b8927508427 100644
> --- a/drivers/iommu/apple-dart.c
> +++ b/drivers/iommu/apple-dart.c
> @@ -671,8 +671,7 @@ static int apple_dart_attach_dev(struct iommu_domain
> *domain,
> return ret;
>
> switch (domain->type) {
> - case IOMMU_DOMAIN_DMA:
> - case IOMMU_DOMAIN_UNMANAGED:
> + default:
> ret = apple_dart_domain_add_streams(dart_domain, cfg);
> if (ret)
> return ret;
Yes, I much prefer this to the original patch please. Drivers should
not be testing DMA_FQ at all.
I already wrote a series to convert DART to domain_alloc_paging() that
fixes this inadvertantly.
Robin's suggestion is good for a temporary -rc fix.
Removing the switch is slightly more robust:
if (domain->type & domain->type & __IOMMU_DOMAIN_PAGING) {
[..]
return 0
}
if (domain->type == IOMMU_DOMAIN_BLOCKED) {
..
}
return -EOPNOTSUPP;
But not so worthwhile since I deleted all this anyhow...
I'll send out the dart series, it can't go to -rc, so a patch is still needed.
Thanks,
Jason
next prev parent reply other threads:[~2023-09-22 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 13:40 [PATCH REGRESSION] iommu: Only allocate FQ domains for IOMMUs that support them Hector Martin
2023-09-22 14:21 ` Robin Murphy
2023-09-22 14:41 ` Hector Martin
2023-09-22 14:42 ` Jason Gunthorpe [this message]
2023-09-24 7:49 ` Linux regression tracking #adding (Thorsten Leemhuis)
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=20230922144222.GF13795@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=asahi@lists.linux.dev \
--cc=iommu@lists.linux.dev \
--cc=jforbes@fedoraproject.org \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=jsnitsel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=neal@gompa.dev \
--cc=regressions@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=stable@vger.kernel.org \
--cc=will@kernel.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