Re: [PATCH] drm/nouveau/fifo: map Kepler video engine contexts non-privileged

From: Dave Airlie

Date: Thu Nov 05 2026 - 03:42:18 EST


On Wed, 4 Nov 2026 at 08:15, Rosen Penev <rosenp@xxxxxxxxx> wrote:
>
> Since the engine context rework, gk104_ectx_ctor() maps every engine
> context into the channel's VMM as a privileged page. The MSVLD,
> MSPDEC and MSPPP falcons on Kepler fetch their context with
> non-privileged requests, so the first method sent to any of them
> faults and the channel is killed:
>
> fifo: fault 00 [READ] at 0000000001050000 engine 10 [MSVLD] client 0d [HUB/MSVLD] reason 05 [PRIV_VIOLATION] on channel 9
> fifo: fault 00 [READ] at 0000000001051000 engine 14 [MSPDEC] client 0b [HUB/MSPDEC] reason 05 [PRIV_VIOLATION] on channel 10
> fifo: fault 00 [READ] at 0000000001052000 engine 11 [MSPPP] client 0c [HUB/MSPPP] reason 05 [PRIV_VIOLATION] on channel 11
>
> Before the rework, gk104_fifo_gpfifo_engine_ctor() mapped engine
> contexts without the privileged bit. Restore that for the three video
> engines, and keep the privileged mapping for everything else.
>
> Fixes: 8ab849d6dd4c ("drm/nouveau/fifo: add new engine context handling")
> Signed-off-by: Rosen Penev <rosenp@xxxxxxxxx>

Appled to drm-misc-fixes

Thanks,
Dave.