Lines Matching refs:to

8 	  Beware setting this value lower, or close to heartbeat interval
9 	  rounded to whole seconds times three, in order to avoid allowing
13 	  May be 0 to disable the timeout.
19 	  When listening to a foreign fence, we install a supplementary timer
20 	  to ensure that we are always signaled and our userspace is able to
24 	  May be 0 to disable the timeout, and rely on the foreign fence being
31 	  On runtime suspend, as we suspend the device, we have to revoke
32 	  userspace GGTT mmaps and force userspace to take a pagefault on
38 	  May be 0 to disable the extra delay and solely use the device level
45 	  The driver sends a periodic heartbeat down all active engines to
52 	  May be 0 to disable heartbeats and therefore disable automatic GPU
59 	  How long to wait (in milliseconds) for a preemption event to occur
61 	  does not hit an arbitration point and yield to HW before the timer
62 	  expires, the HW will be reset to allow the more important context
63 	  to execute.
68 	  May be 0 to disable the timeout.
78 	  Before sleeping waiting for a request (GPU operation) to complete,
80 	  take a non-negligible time to setup, we do a short spin first to
82 	  us to enable the interrupt.
87 	  May be 0 to disable the initial spin. In practice, we estimate
88 	  the cost of enabling the interrupt (if currently disabled) to be
92 	int "How long to wait for an engine to quiesce gracefully before reset (ms)"
96 	  the GPU, we allow the innocent contexts also on the system to quiesce.
97 	  It is then less likely for a hanging context to cause collateral
98 	  damage as the system is reset in order to recover. The corollary is
99 	  that the reset itself may take longer and so be more disruptive to
110 	  alternate execution of each batch to ensure forward progress of
113 	  concurrent execution in order for them to proceed, e.g. they
116 	  switching to the next context.
121 	  May be 0 to disable timeslicing.