From: Robin Murphy <robin.murphy@arm.com>
To: Nicolas Chauvet <kwizart@gmail.com>
Cc: joro@8bytes.org, iommu@lists.linux.dev, will@kernel.org,
jgg@nvidia.com, digetx@gmail.com, thierry.reding@gmail.com,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH 0/4] iommu: tegra-gart cleanups
Date: Tue, 16 May 2023 12:45:35 +0100 [thread overview]
Message-ID: <11d8adf1-75f5-5728-2139-e32aae6e6c49@arm.com> (raw)
In-Reply-To: <CABr+WTnzNPfOGbAmy-E3pH9U5XR0y2PdVmDd2gtnv67ByEb_0w@mail.gmail.com>
On 2023-05-16 10:53, Nicolas Chauvet wrote:
> Le lun. 15 mai 2023 à 14:57, Robin Murphy <robin.murphy@arm.com> a écrit :
>>
>> Hi all,
>>
>> For the sake of discussion, here's my irrational pet project to bring
>> the tegra-gart driver right up to date as an example of a
>> properly-implemented IOMMU driver for a non-isolated address space. Part
>> of that irrationality is that I don't even own any hardware which uses
>> this driver, so it's only build-tested :)
>>
>> Thanks,
>> Robin.
>>
>>
>> Robin Murphy (4):
>> iommu/tegra-gart: Add default identity domain support
>> iommu/tegra-gart: Improve domain support
>> iommu/tegra-gart: Generalise domain support
>> iommu: Clean up force_aperture confusion
>>
>> drivers/iommu/dma-iommu.c | 19 ++--
>> drivers/iommu/mtk_iommu_v1.c | 4 +
>> drivers/iommu/sprd-iommu.c | 1 +
>> drivers/iommu/tegra-gart.c | 162 +++++++++++++++++++----------------
>> 4 files changed, 99 insertions(+), 87 deletions(-)
>
>
> For what it worth, I've tried to test this serie with "grate patches"
> (1) rebased on top on 6.4-rc2, that would make use of the tegra-gart.
> That was on PAZ00 (with only 512M of RAM and 96M CMA still allocated).
> Unfortunately, this lead to the following errors with display problems
> (no character displayed in lxt-terminal and etc)
Thanks for testing - it's quite possible I've made a silly mistake
somewhere, but just to double-check, does the same happen with the
existing driver if you boot with "tegra-gart.gart_debug=1" (or at least
enable the parameter via sysfs before the DRM driver gets going)?
Thanks,
Robin.
> [ 888.691348] tegra-mc 7000f000.memory-controller: gart: Page entry is in-use
> [ 888.698400] [drm:tegra_bo_gart_map_locked [tegra_drm]] *ERROR*
> mapping failed 4294967274 262144
> [ 888.707365] [drm:tegra_bo_gart_map_locked [tegra_drm]] *ERROR*
> failed size 262144: -12
> [ 888.716735] tegra-mc 7000f000.memory-controller: gart: Page entry is in-use
> [ 888.723800] [drm:tegra_bo_gart_map_locked [tegra_drm]] *ERROR*
> mapping failed 4294967274 262144
> [ 888.733156] [drm:tegra_bo_gart_map_locked [tegra_drm]] *ERROR*
> failed size 262144: -12
> [ 889.055247] tegra-mc 7000f000.memory-controller: gart: Page entry is in-use
> [ 889.062296] [drm:tegra_bo_gart_map_locked [tegra_drm]] *ERROR*
> mapping failed 4294967274 262144
> [ 889.071266] [drm:tegra_bo_gart_map_locked [tegra_drm]] *ERROR*
> failed size 262144: -12
>
> (1) https://github.com/grate-driver/linux
next prev parent reply other threads:[~2023-05-16 11:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 12:49 [PATCH 0/4] iommu: tegra-gart cleanups Robin Murphy
2023-05-15 12:49 ` [PATCH 1/4] iommu/tegra-gart: Add default identity domain support Robin Murphy
2023-05-15 12:49 ` [PATCH 2/4] iommu/tegra-gart: Improve " Robin Murphy
2023-05-15 12:49 ` [PATCH 3/4] iommu/tegra-gart: Generalise " Robin Murphy
2023-05-15 12:49 ` [PATCH 4/4] iommu: Clean up force_aperture confusion Robin Murphy
2023-05-15 13:15 ` Jason Gunthorpe
2023-05-16 9:53 ` [PATCH 0/4] iommu: tegra-gart cleanups Nicolas Chauvet
2023-05-16 11:45 ` Robin Murphy [this message]
2023-05-16 12:16 ` Nicolas Chauvet
2023-05-16 12:31 ` Robin Murphy
2023-05-16 15:15 ` Nicolas Chauvet
2023-05-17 10:54 ` Robin Murphy
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=11d8adf1-75f5-5728-2139-e32aae6e6c49@arm.com \
--to=robin.murphy@arm.com \
--cc=digetx@gmail.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=kwizart@gmail.com \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.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