From: Christoph Hellwig <hch@infradead.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Mario Limonciello <mario.limonciello@amd.com>,
Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
"open list:IOMMU DRIVERS" <iommu@lists.linux-foundation.org>,
Suthikulpanit Suravee <Suravee.Suthikulpanit@amd.com>,
Hegde Vasant <Vasant.Hegde@amd.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] iommu/amd: Enable swiotlb in all cases
Date: Thu, 7 Apr 2022 06:41:09 -0700 [thread overview]
Message-ID: <Yk7p9fhIhvaHw9dF@infradead.org> (raw)
In-Reply-To: <f7039f1f-81ef-2fab-4ade-728316b54942@arm.com>
On Thu, Apr 07, 2022 at 02:31:44PM +0100, Robin Murphy wrote:
> FWIW it's also broken for another niche case where
> iommu_default_passthrough() == false at init, but the user later changes a
> 32-bit device's default domain type to passthrough via sysfs, such that it
> starts needing regular dma-direct bouncing.
Yeah.
We also have yet another issue: swiotlb is not allocate if there is
no memory outside the 4GB physical address space. I think I can fix
that easily after my swiotlb init series goes in, before that it
would be a bit of a mess spread over all the architectures.
next prev parent reply other threads:[~2022-04-07 13:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 20:47 [PATCH v2 0/2] Fix issues with untrusted devices and AMD IOMMU Mario Limonciello
2022-04-04 20:47 ` [PATCH v2 1/2] iommu/amd: Enable swiotlb in all cases Mario Limonciello
2022-04-05 4:34 ` Christoph Hellwig
2022-04-06 17:04 ` Limonciello, Mario
2022-04-07 7:58 ` Christoph Hellwig
2022-04-21 14:44 ` Limonciello, Mario
2022-04-07 13:31 ` Robin Murphy
2022-04-07 13:41 ` Christoph Hellwig [this message]
2022-04-04 20:47 ` [PATCH v2 2/2] dma-iommu: Check that swiotlb is active before trying to use it Mario Limonciello
2022-04-05 4:34 ` Christoph Hellwig
2022-04-07 13:07 ` Robin Murphy
2022-04-28 8:27 ` [PATCH v2 0/2] Fix issues with untrusted devices and AMD IOMMU 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=Yk7p9fhIhvaHw9dF@infradead.org \
--to=hch@infradead.org \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=Vasant.Hegde@amd.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mario.limonciello@amd.com \
--cc=robin.murphy@arm.com \
--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