diff options
author | Luca Barbieri <luca@luca-barbieri.com> | 2010-01-16 15:27:51 +0100 |
---|---|---|
committer | Ben Skeggs <bskeggs@redhat.com> | 2010-01-18 09:56:03 +1000 |
commit | d051bbb22e9d8e87e2a5b8efb176d1bfd0f7feee (patch) | |
tree | 1a03f3b39bddfad3c40184a6eb9947fece59664a /drivers/gpu/drm/nouveau/nouveau_state.c | |
parent | 0d92971dd6973d865a873c24df2d7bfe06ec4486 (diff) |
drm/nouveau: Acknowledge DMA_VTX_PROTECTION PGRAPH interrupts
Currently Nouveau is unable to dismiss DMA_VTX_PROTECTION errors,
which results in an infinite loop in the interrupt handler.
These errors are caused both by bugs in the Gallium driver and by
user-specified index buffers with out of bounds indices.
By mmio-tracing the nVidia drivers, I found out how this is done.
On DMA_VTX_PROTECTION, The nVidia driver reads the register 0x402000,
always getting the value 4, and then writes 4 back to 0x402000.
This patch adds that logic by reading 0x402000 and writing the same
value back.
It's unclear what should happen if the value read is not 4, and
the current approach might not be the correct one.
To test this, modify mesa/progs/trivial/vbo-drawrange.c, defining
ELTOBJ to 1 and replacing indices with huge out of bounds integers.
Without this patch, the GPU and/or kernel should lock up.
With this patch, it should misrender as expected but not lock up.
The errors are still logged since they are useful for development.
This has been tested on NV49 and may not work on other cards.
To find out how things work on other cards, run the aforementioned
test using the blob with mmiotrace and grep for a read of the PGRAPH
source register.
Signed-off-by: Luca Barbieri <luca@luca-barbieri.com>
Signed-off-by: Francisco Jerez <currojerez@riseup.net>
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
Diffstat (limited to 'drivers/gpu/drm/nouveau/nouveau_state.c')
0 files changed, 0 insertions, 0 deletions