drivers/gpu/drm/nouveau/nouveau_sgdma.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)
From: Faith Ekstrand <faith.ekstrand@collabora.com>
On Tegra devices, uncached maps traslate to device memory, causing
unaligned accesses by userspace resulting in a SIGBUS. Instead, use
write-combined maps to ensure proper access.
This would also affect discrete cards on any Arm device. It was
determined that discrete cards regardless of cpu arch should use
write-combined maps for coherent anyways. Thus this change is made for
all gpu types.
Signed-off-by: Faith Ekstrand <faith.ekstrand@collabora.com>
Co-developed-by: Aaron Kling <webgeek1234@gmail.com>
Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
---
Without this change, nouveau can easily hit sigbus errors in the Android
UI rendering via nvk or running vulkan deqp tests on Tegra. Changing
coherent maps to use write-combined stops the crashing.
---
Changes in v2:
- Set write-combined for coherent on all gpu types
- Link to v1: https://lore.kernel.org/r/20260725-tegra-coherent-wc-v1-1-dfdcc929c21b@gmail.com
---
drivers/gpu/drm/nouveau/nouveau_sgdma.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/nouveau/nouveau_sgdma.c b/drivers/gpu/drm/nouveau/nouveau_sgdma.c
index fa3b4ebf38a83..2bd0376193aee 100644
--- a/drivers/gpu/drm/nouveau/nouveau_sgdma.c
+++ b/drivers/gpu/drm/nouveau/nouveau_sgdma.c
@@ -72,9 +72,7 @@ nouveau_sgdma_create_ttm(struct ttm_buffer_object *bo, uint32_t page_flags)
struct nouveau_sgdma_be *nvbe;
enum ttm_caching caching;
- if (nvbo->force_coherent)
- caching = ttm_uncached;
- else if (drm->agp.bridge)
+ if (nvbo->force_coherent || drm->agp.bridge)
caching = ttm_write_combined;
else
caching = ttm_cached;
---
base-commit: 903c1cf6dff9964e71eda98a39e2e5d442050472
change-id: 20260725-tegra-coherent-wc-19941d1a5a60
Best regards,
--
Aaron Kling <webgeek1234@gmail.com>
On Fri, 21 Aug 2026 23:42:59 -0500, Aaron Kling wrote:
> [PATCH v2] drm/nouveau: Use write-combined maps for coherent
Applied, thanks!
Branch: drm-misc-fixes
Tree: https://gitlab.freedesktop.org/drm/misc/kernel.git
[1/1] drm/nouveau: Use write-combined maps for coherent
commit: 774b73428e6e
The patch will appear in the next linux-next integration (typically within 24
hours on weekdays).
The patch is queued up for Linus's tree and should land in the next -rc release.
On 8/22/26 6:42 AM, Aaron Kling via B4 Relay wrote: > From: Faith Ekstrand <faith.ekstrand@collabora.com> > > On Tegra devices, uncached maps traslate to device memory, causing > unaligned accesses by userspace resulting in a SIGBUS. Instead, use > write-combined maps to ensure proper access. > > This would also affect discrete cards on any Arm device. It was > determined that discrete cards regardless of cpu arch should use > write-combined maps for coherent anyways. Thus this change is made for > all gpu types. > > Signed-off-by: Faith Ekstrand <faith.ekstrand@collabora.com> > Co-developed-by: Aaron Kling <webgeek1234@gmail.com> > Signed-off-by: Aaron Kling <webgeek1234@gmail.com> Can you please provide a Fixes: tag? Also, please remember to Cc: stable if necessary. Thanks, Danilo
On Tue, Sep 1, 2026 at 9:07 AM Danilo Krummrich <dakr@kernel.org> wrote:
>
> On 8/22/26 6:42 AM, Aaron Kling via B4 Relay wrote:
> > From: Faith Ekstrand <faith.ekstrand@collabora.com>
> >
> > On Tegra devices, uncached maps traslate to device memory, causing
> > unaligned accesses by userspace resulting in a SIGBUS. Instead, use
> > write-combined maps to ensure proper access.
> >
> > This would also affect discrete cards on any Arm device. It was
> > determined that discrete cards regardless of cpu arch should use
> > write-combined maps for coherent anyways. Thus this change is made for
> > all gpu types.
> >
> > Signed-off-by: Faith Ekstrand <faith.ekstrand@collabora.com>
> > Co-developed-by: Aaron Kling <webgeek1234@gmail.com>
> > Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
> Can you please provide a Fixes: tag? Also, please remember to Cc: stable if necessary.
Looks like the tag is:
Fixes: 1b4ea4c5980f ("drm/ttm: set the tt caching state at creation time")
Should I send another revision just to add this, or can the subsystem
maintainer add it when picking the change up? For stable, I would like
to see this picked to 6.18 at least, since I primarily work with LTS
forks.
Aaron
On Tue, 2026-09-01 at 13:03 -0500, Aaron Kling wrote:
>
> Looks like the tag is:
>
> Fixes: 1b4ea4c5980f ("drm/ttm: set the tt caching state at creation
> time")
>
> Should I send another revision just to add this, or can the subsystem
> maintainer add it when picking the change up? For stable, I would
> like
> to see this picked to 6.18 at least, since I primarily work with LTS
> forks.
>
> Aaron
I would send out a respin with the tag
© 2016 - 2026 Red Hat, Inc.