On Thu, Feb 06, 2025 at 10:20:43AM +, Tvrtko Ursulin wrote:
>
> On 06/02/2025 06:45, Matthew Brost wrote:
> > On Wed, Feb 05, 2025 at 01:44:48PM +0100, Christian König wrote:
> > > Am 05.02.25 um 12:14 schrieb Tvrtko Ursulin:
> > > > Christian suggests scheduler should not use the term TDR bec
On 06/02/2025 06:45, Matthew Brost wrote:
On Wed, Feb 05, 2025 at 01:44:48PM +0100, Christian König wrote:
Am 05.02.25 um 12:14 schrieb Tvrtko Ursulin:
Christian suggests scheduler should not use the term TDR because it only
can do basic timeout detection on it's own, not the full blown timeo
On Wed, Feb 05, 2025 at 01:44:48PM +0100, Christian König wrote:
> Am 05.02.25 um 12:14 schrieb Tvrtko Ursulin:
> > Christian suggests scheduler should not use the term TDR because it only
> > can do basic timeout detection on it's own, not the full blown timeout-
> > detection-and-recovery (TDR) a
Am 05.02.25 um 12:14 schrieb Tvrtko Ursulin:
Christian suggests scheduler should not use the term TDR because it only
can do basic timeout detection on it's own, not the full blown timeout-
detection-and-recovery (TDR) as the term is generally understood.
There is even more to the term TDR on W
Christian suggests scheduler should not use the term TDR because it only
can do basic timeout detection on it's own, not the full blown timeout-
detection-and-recovery (TDR) as the term is generally understood.
Attempt to rename it to a more basic drm_sched_trigger_timeout.
Signed-off-by: Tvrtko
