#
334cc26d |
| 08-May-2018 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/fifo/gp100-: force individual channels into a channel group
RM does this for some reason, and is enforced in HW on Volta.
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
#
79bb4b61 |
| 08-May-2018 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/fifo/gk208-: write pbdma timeout regs during initialisation
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
#
8c4e9f9d |
| 08-May-2018 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/fifo/gk110-: support writing channel group runlist entries
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
#
4f2fc25c |
| 08-May-2018 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/fifo/gk104-: poll for runlist update completion
Newer HW doesn't appear to send this event, which will cause long delays in runlist updates if they don't complete immediately.
RM doesn'
drm/nouveau/fifo/gk104-: poll for runlist update completion
Newer HW doesn't appear to send this event, which will cause long delays in runlist updates if they don't complete immediately.
RM doesn't use these events anywhere, and an NVGPU commit message notes that polling is the preferred method even on HW that supports the event.
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
show more ...
|
#
66587083 |
| 08-May-2018 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/fifo/gk104-: add interfaces to support different runlist layouts
This will be required to support features on newer hardware.
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
#
f9360c3a |
| 08-May-2018 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/fifo/gk104-: simplify definition of channel classes
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
#
cc362050 |
| 08-May-2018 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/fifo/gk104-: support querying engines available on each runlist
Will be used to improve channel runlist selection.
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
#
ddc669e2 |
| 08-May-2018 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/fifo/gk104-: allow fault recovery code to be called by other subdevs
This will be required to support Volta.
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
Revision tags: v4.16, v4.15, v4.13.16, v4.14 |
|
#
01f349fc |
| 31-Oct-2017 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/fifo/gf100-: use new interfaces for vmm operations
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
#
997a8900 |
| 31-Oct-2017 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/core/memory: add reference counting
We need to be able to prevent memory from being freed while it's still mapped in a GPU's address-space.
Will be used by upcoming MMU changes.
Signed
drm/nouveau/core/memory: add reference counting
We need to be able to prevent memory from being freed while it's still mapped in a GPU's address-space.
Will be used by upcoming MMU changes.
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
show more ...
|
#
19a82e49 |
| 31-Oct-2017 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/core/memory: change map interface to support upcoming mmu changes
Map flags (access, kind, etc) are currently defined in either the VMA, or the memory object, which turns out to not be i
drm/nouveau/core/memory: change map interface to support upcoming mmu changes
Map flags (access, kind, etc) are currently defined in either the VMA, or the memory object, which turns out to not be ideal for things like suballocated buffers, etc.
These will become per-map flags instead, so we need to support passing these arguments in nvkm_memory_map().
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
show more ...
|
#
570889dc |
| 31-Oct-2017 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/bar: modify interface to bar1 vmm mapping
Upcoming changes will remove the nvkm_vmm pointer from nvkm_vma, instead requiring it to be explicitly specified on each operation.
It's not cu
drm/nouveau/bar: modify interface to bar1 vmm mapping
Upcoming changes will remove the nvkm_vmm pointer from nvkm_vma, instead requiring it to be explicitly specified on each operation.
It's not currently possible to get this information for BAR1 mappings, so let's fix that ahead of time.
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
show more ...
|
Revision tags: v4.13.5, v4.13, v4.12, v4.10.17, v4.10.16, v4.10.15, v4.10.14 |
|
#
2579b8b0 |
| 27-Apr-2017 |
Dan Carpenter <dan.carpenter@oracle.com> |
drm/nouveau/fifo/gk104-: Silence a locking warning
Presumably we can never actually hit this return, but static checkers complain that we should unlock before we return.
Signed-off-by: Dan Carpente
drm/nouveau/fifo/gk104-: Silence a locking warning
Presumably we can never actually hit this return, but static checkers complain that we should unlock before we return.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
show more ...
|
Revision tags: v4.10.13, v4.10.12, v4.10.11, v4.10.10, v4.10.9, v4.10.8, v4.10.7, v4.10.6, v4.10.5, v4.10.4, v4.10.3, v4.10.2, v4.10.1, v4.10 |
|
#
3ebef76a |
| 17-Jan-2017 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/fifo/gk104-: trigger mmu fault before attempting engine recovery
Greatly improves the chances of recovering the GPU from a CTXSW_TIMEOUT.
Tested with piglit's arb_shader_image_load_stor
drm/nouveau/fifo/gk104-: trigger mmu fault before attempting engine recovery
Greatly improves the chances of recovering the GPU from a CTXSW_TIMEOUT.
Tested with piglit's arb_shader_image_load_store-atomicity, which causes GR to hang in such a way that recovery failed (CTXSW_TIMEOUT continually re-triggers).
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
show more ...
|
#
03f16f5f |
| 18-Jan-2017 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/fifo/gk104-: ACK SCHED_ERROR before attempting CTXSW_TIMEOUT recovery
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
#
91b9d659 |
| 18-Jan-2017 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/fifo/gk104-: directly use new recovery code for ctxsw timeout
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
#
3534821d |
| 18-Jan-2017 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/fifo/gk104-: directly use new recovery code for mmu faults
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
#
eaa5ed65 |
| 17-Jan-2017 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/fifo/gk104-: reset all engines a killed channel is still active on
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
#
0faaa47d |
| 17-Jan-2017 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/fifo/gk104-: refactor recovery code
This will serve as a basis for implementing some improvements to how we recover the GPU from channel errors.
Signed-off-by: Ben Skeggs <bskeggs@redha
drm/nouveau/fifo/gk104-: refactor recovery code
This will serve as a basis for implementing some improvements to how we recover the GPU from channel errors.
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
show more ...
|
#
ec5c6bda |
| 15-Jan-2017 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/fifo/gk104-: better detection of chid when parsing engine status
The previous commit simply changes the interface, but should result in the same behaviour as previously. This commit has
drm/nouveau/fifo/gk104-: better detection of chid when parsing engine status
The previous commit simply changes the interface, but should result in the same behaviour as previously. This commit has been split out from it as it can result in a different channel being selected.
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
show more ...
|
#
b88917fe |
| 15-Jan-2017 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/fifo/gk104-: separate out engine status parsing
We'll be wanting to reuse this logic in more places.
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
Revision tags: v4.9, openbmc-4.4-20161121-1, v4.4.33, v4.4.32, v4.4.31 |
|
#
ff9f29ab |
| 04-Nov-2016 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/fifo/gf100-: provide notification to user if channel is killed
There are instances (such as non-recoverable GPU page faults) where NVKM decides that a channel's context is no longer viab
drm/nouveau/fifo/gf100-: provide notification to user if channel is killed
There are instances (such as non-recoverable GPU page faults) where NVKM decides that a channel's context is no longer viable, and will be removed from the runlist.
This commit notifies the owner of the channel when this happens, so it has the opportunity to take some kind of recovery action instead of hanging.
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
show more ...
|
Revision tags: v4.4.30, v4.4.29, v4.4.28, v4.4.27, v4.7.10, openbmc-4.4-20161021-1, v4.7.9, v4.4.26, v4.7.8, v4.4.25, v4.4.24, v4.7.7, v4.8, v4.4.23, v4.7.6, v4.7.5, v4.4.22, v4.4.21, v4.7.4, v4.7.3, v4.4.20, v4.7.2, v4.4.19, openbmc-4.4-20160819-1, v4.7.1, v4.4.18, v4.4.17, openbmc-4.4-20160804-1, v4.4.16, v4.7, openbmc-4.4-20160722-1, openbmc-20160722-1, openbmc-20160713-1, v4.4.15, v4.6.4, v4.6.3, v4.4.14, v4.6.2, v4.4.13, openbmc-20160606-1, v4.6.1, v4.4.12, openbmc-20160521-1, v4.4.11, openbmc-20160518-1, v4.6, v4.4.10, openbmc-20160511-1 |
|
#
d2ee3605 |
| 09-May-2016 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/core/memory: distinguish between coherent/non-coherent targets
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
#
ec884f74 |
| 09-Dec-2016 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/fifo/gf100-: recover from host mmu faults
This has been on the TODO list for a while now, recovering from things such as attempting to execute a push buffer or touch a semaphore in an un
drm/nouveau/fifo/gf100-: recover from host mmu faults
This has been on the TODO list for a while now, recovering from things such as attempting to execute a push buffer or touch a semaphore in an unmapped memory area.
The only thing required on the HW side here is that the offending channel is removed from the runlist, and *not* a full reset of PFIFO.
This used to be a bit messier to handle before the rework to make use of engine topology info, but is apparently now trivial.
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
show more ...
|
#
1fe8c02f |
| 21-Jun-2016 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/fifo/gk104-: translate engidx into human-readable name in debug output
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|