Searched hist:"6 d7a20c0776036115c6e22bc673d645d524c4b8a" (Results 1 – 5 of 5) sorted by relevance
| /linux/drivers/gpu/drm/etnaviv/ |
| H A D | etnaviv_dump.c | diff 6d7a20c0776036115c6e22bc673d645d524c4b8a Wed Dec 06 10:53:27 CET 2017 Lucas Stach <l.stach@pengutronix.de> drm/etnaviv: replace hangcheck with scheduler timeout
This replaces the etnaviv internal hangcheck logic with the job timeout
handling provided by the DRM scheduler. This simplifies the driver further
and allows to replay jobs after a GPU reset, so only minimal state is lost.
This introduces a user-visible change in that we don't allow jobs to run
indefinitely as long as they make progress anymore, as this introduces
quality of service issues when multiple processes are using the GPU.
Userspace is now responsible to flush jobs in a way that the finish in a
reasonable time, where reasonable is currently defined as less than 500ms.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
|
| H A D | etnaviv_sched.c | diff 6d7a20c0776036115c6e22bc673d645d524c4b8a Wed Dec 06 10:53:27 CET 2017 Lucas Stach <l.stach@pengutronix.de> drm/etnaviv: replace hangcheck with scheduler timeout
This replaces the etnaviv internal hangcheck logic with the job timeout
handling provided by the DRM scheduler. This simplifies the driver further
and allows to replay jobs after a GPU reset, so only minimal state is lost.
This introduces a user-visible change in that we don't allow jobs to run
indefinitely as long as they make progress anymore, as this introduces
quality of service issues when multiple processes are using the GPU.
Userspace is now responsible to flush jobs in a way that the finish in a
reasonable time, where reasonable is currently defined as less than 500ms.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
|
| H A D | etnaviv_gpu.h | diff 6d7a20c0776036115c6e22bc673d645d524c4b8a Wed Dec 06 10:53:27 CET 2017 Lucas Stach <l.stach@pengutronix.de> drm/etnaviv: replace hangcheck with scheduler timeout
This replaces the etnaviv internal hangcheck logic with the job timeout
handling provided by the DRM scheduler. This simplifies the driver further
and allows to replay jobs after a GPU reset, so only minimal state is lost.
This introduces a user-visible change in that we don't allow jobs to run
indefinitely as long as they make progress anymore, as this introduces
quality of service issues when multiple processes are using the GPU.
Userspace is now responsible to flush jobs in a way that the finish in a
reasonable time, where reasonable is currently defined as less than 500ms.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
|
| H A D | etnaviv_gem_submit.c | diff 6d7a20c0776036115c6e22bc673d645d524c4b8a Wed Dec 06 10:53:27 CET 2017 Lucas Stach <l.stach@pengutronix.de> drm/etnaviv: replace hangcheck with scheduler timeout
This replaces the etnaviv internal hangcheck logic with the job timeout
handling provided by the DRM scheduler. This simplifies the driver further
and allows to replay jobs after a GPU reset, so only minimal state is lost.
This introduces a user-visible change in that we don't allow jobs to run
indefinitely as long as they make progress anymore, as this introduces
quality of service issues when multiple processes are using the GPU.
Userspace is now responsible to flush jobs in a way that the finish in a
reasonable time, where reasonable is currently defined as less than 500ms.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
|
| H A D | etnaviv_gpu.c | diff 6d7a20c0776036115c6e22bc673d645d524c4b8a Wed Dec 06 10:53:27 CET 2017 Lucas Stach <l.stach@pengutronix.de> drm/etnaviv: replace hangcheck with scheduler timeout
This replaces the etnaviv internal hangcheck logic with the job timeout
handling provided by the DRM scheduler. This simplifies the driver further
and allows to replay jobs after a GPU reset, so only minimal state is lost.
This introduces a user-visible change in that we don't allow jobs to run
indefinitely as long as they make progress anymore, as this introduces
quality of service issues when multiple processes are using the GPU.
Userspace is now responsible to flush jobs in a way that the finish in a
reasonable time, where reasonable is currently defined as less than 500ms.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
|