1config DRM_I915_REQUEST_TIMEOUT
  2	int "Default timeout for requests (ms)"
  3	default 20000 # milliseconds
  4	help
  5	  Configures the default timeout after which any user submissions will
  6	  be forcefully terminated.
  7
  8	  Beware setting this value lower, or close to heartbeat interval
  9	  rounded to whole seconds times three, in order to avoid allowing
 10	  misbehaving applications causing total rendering failure in unrelated
 11	  clients.
 12
 13	  May be 0 to disable the timeout.
 14
 15config DRM_I915_FENCE_TIMEOUT
 16	int "Timeout for unsignaled foreign fences (ms, jiffy granularity)"
 17	default 10000 # milliseconds
 18	help
 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
 21	  make forward progress. This value specifies the timeout used for an
 22	  unsignaled foreign fence.
 23
 24	  May be 0 to disable the timeout, and rely on the foreign fence being
 25	  eventually signaled.
 26
 27config DRM_I915_USERFAULT_AUTOSUSPEND
 28	int "Runtime autosuspend delay for userspace GGTT mmaps (ms)"
 29	default 250 # milliseconds
 30	help
 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
 33	  their next access. The revocation and subsequent recreation of
 34	  the GGTT mmap can be very slow and so we impose a small hysteris
 35	  that complements the runtime-pm autosuspend and provides a lower
 36	  floor on the autosuspend delay.
 37
 38	  May be 0 to disable the extra delay and solely use the device level
 39	  runtime pm autosuspend delay tunable.
 40
 41config DRM_I915_HEARTBEAT_INTERVAL
 42	int "Interval between heartbeat pulses (ms)"
 43	default 2500 # milliseconds
 44	help
 45	  The driver sends a periodic heartbeat down all active engines to
 46	  check the health of the GPU and undertake regular house-keeping of
 47	  internal driver state.
 48
 49	  This is adjustable via
 50	  /sys/class/drm/card?/engine/*/heartbeat_interval_ms
 51
 52	  May be 0 to disable heartbeats and therefore disable automatic GPU
 53	  hang detection.
 54
 55config DRM_I915_PREEMPT_TIMEOUT
 56	int "Preempt timeout (ms, jiffy granularity)"
 57	default 640 # milliseconds
 58	help
 59	  How long to wait (in milliseconds) for a preemption event to occur
 60	  when submitting a new context via execlists. If the current context
 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.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 64
 65	  This is adjustable via
 66	  /sys/class/drm/card?/engine/*/preempt_timeout_ms
 67
 68	  May be 0 to disable the timeout.
 69
 70	  The compiled in default may get overridden at driver probe time on
 71	  certain platforms and certain engines which will be reflected in the
 72	  sysfs control.
 73
 74config DRM_I915_MAX_REQUEST_BUSYWAIT
 75	int "Busywait for request completion limit (ns)"
 76	default 8000 # nanoseconds
 77	help
 78	  Before sleeping waiting for a request (GPU operation) to complete,
 79	  we may spend some time polling for its completion. As the IRQ may
 80	  take a non-negligible time to setup, we do a short spin first to
 81	  check if the request will complete in the time it would have taken
 82	  us to enable the interrupt.
 83
 84	  This is adjustable via
 85	  /sys/class/drm/card?/engine/*/max_busywait_duration_ns
 86
 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
 89	  a few microseconds.
 90
 91config DRM_I915_STOP_TIMEOUT
 92	int "How long to wait for an engine to quiesce gracefully before reset (ms)"
 93	default 100 # milliseconds
 94	help
 95	  By stopping submission and sleeping for a short time before resetting
 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
100	  interactive or low latency workloads.
101
102	  This is adjustable via
103	  /sys/class/drm/card?/engine/*/stop_timeout_ms
104
105config DRM_I915_TIMESLICE_DURATION
106	int "Scheduling quantum for userspace batches (ms, jiffy granularity)"
107	default 1 # milliseconds
108	help
109	  When two user batches of equal priority are executing, we will
110	  alternate execution of each batch to ensure forward progress of
111	  all users. This is necessary in some cases where there may be
112	  an implicit dependency between those batches that requires
113	  concurrent execution in order for them to proceed, e.g. they
114	  interact with each other via userspace semaphores. Each context
115	  is scheduled for execution for the timeslice duration, before
116	  switching to the next context.
117
118	  This is adjustable via
119	  /sys/class/drm/card?/engine/*/timeslice_duration_ms
120
121	  May be 0 to disable timeslicing.

  1config DRM_I915_REQUEST_TIMEOUT
  2	int "Default timeout for requests (ms)"
  3	default 20000 # milliseconds
  4	help
  5	  Configures the default timeout after which any user submissions will
  6	  be forcefully terminated.
  7
  8	  Beware setting this value lower, or close to heartbeat interval
  9	  rounded to whole seconds times three, in order to avoid allowing
 10	  misbehaving applications causing total rendering failure in unrelated
 11	  clients.
 12
 13	  May be 0 to disable the timeout.
 14
 15config DRM_I915_FENCE_TIMEOUT
 16	int "Timeout for unsignaled foreign fences (ms, jiffy granularity)"
 17	default 10000 # milliseconds
 18	help
 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
 21	  make forward progress. This value specifies the timeout used for an
 22	  unsignaled foreign fence.
 23
 24	  May be 0 to disable the timeout, and rely on the foreign fence being
 25	  eventually signaled.
 26
 27config DRM_I915_USERFAULT_AUTOSUSPEND
 28	int "Runtime autosuspend delay for userspace GGTT mmaps (ms)"
 29	default 250 # milliseconds
 30	help
 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
 33	  their next access. The revocation and subsequent recreation of
 34	  the GGTT mmap can be very slow and so we impose a small hysteris
 35	  that complements the runtime-pm autosuspend and provides a lower
 36	  floor on the autosuspend delay.
 37
 38	  May be 0 to disable the extra delay and solely use the device level
 39	  runtime pm autosuspend delay tunable.
 40
 41config DRM_I915_HEARTBEAT_INTERVAL
 42	int "Interval between heartbeat pulses (ms)"
 43	default 2500 # milliseconds
 44	help
 45	  The driver sends a periodic heartbeat down all active engines to
 46	  check the health of the GPU and undertake regular house-keeping of
 47	  internal driver state.
 48
 49	  This is adjustable via
 50	  /sys/class/drm/card?/engine/*/heartbeat_interval_ms
 51
 52	  May be 0 to disable heartbeats and therefore disable automatic GPU
 53	  hang detection.
 54
 55config DRM_I915_PREEMPT_TIMEOUT
 56	int "Preempt timeout (ms, jiffy granularity)"
 57	default 640 # milliseconds
 58	help
 59	  How long to wait (in milliseconds) for a preemption event to occur
 60	  when submitting a new context. If the current context does not hit
 61	  an arbitration point and yield to HW before the timer expires, the
 62	  HW will be reset to allow the more important context to execute.
 63
 64	  This is adjustable via
 65	  /sys/class/drm/card?/engine/*/preempt_timeout_ms
 66
 67	  May be 0 to disable the timeout.
 68
 69	  The compiled in default may get overridden at driver probe time on
 70	  certain platforms and certain engines which will be reflected in the
 71	  sysfs control.
 72
 73config DRM_I915_PREEMPT_TIMEOUT_COMPUTE
 74	int "Preempt timeout for compute engines (ms, jiffy granularity)"
 75	default 7500 # milliseconds
 76	help
 77	  How long to wait (in milliseconds) for a preemption event to occur
 78	  when submitting a new context to a compute capable engine. If the
 79	  current context does not hit an arbitration point and yield to HW
 80	  before the timer expires, the HW will be reset to allow the more
 81	  important context to execute.
 82
 83	  This is adjustable via
 84	  /sys/class/drm/card?/engine/*/preempt_timeout_ms
 85
 86	  May be 0 to disable the timeout.
 87
 88	  The compiled in default may get overridden at driver probe time on
 89	  certain platforms and certain engines which will be reflected in the
 90	  sysfs control.
 91
 92config DRM_I915_MAX_REQUEST_BUSYWAIT
 93	int "Busywait for request completion limit (ns)"
 94	default 8000 # nanoseconds
 95	help
 96	  Before sleeping waiting for a request (GPU operation) to complete,
 97	  we may spend some time polling for its completion. As the IRQ may
 98	  take a non-negligible time to setup, we do a short spin first to
 99	  check if the request will complete in the time it would have taken
100	  us to enable the interrupt.
101
102	  This is adjustable via
103	  /sys/class/drm/card?/engine/*/max_busywait_duration_ns
104
105	  May be 0 to disable the initial spin. In practice, we estimate
106	  the cost of enabling the interrupt (if currently disabled) to be
107	  a few microseconds.
108
109config DRM_I915_STOP_TIMEOUT
110	int "How long to wait for an engine to quiesce gracefully before reset (ms)"
111	default 100 # milliseconds
112	help
113	  By stopping submission and sleeping for a short time before resetting
114	  the GPU, we allow the innocent contexts also on the system to quiesce.
115	  It is then less likely for a hanging context to cause collateral
116	  damage as the system is reset in order to recover. The corollary is
117	  that the reset itself may take longer and so be more disruptive to
118	  interactive or low latency workloads.
119
120	  This is adjustable via
121	  /sys/class/drm/card?/engine/*/stop_timeout_ms
122
123config DRM_I915_TIMESLICE_DURATION
124	int "Scheduling quantum for userspace batches (ms, jiffy granularity)"
125	default 1 # milliseconds
126	help
127	  When two user batches of equal priority are executing, we will
128	  alternate execution of each batch to ensure forward progress of
129	  all users. This is necessary in some cases where there may be
130	  an implicit dependency between those batches that requires
131	  concurrent execution in order for them to proceed, e.g. they
132	  interact with each other via userspace semaphores. Each context
133	  is scheduled for execution for the timeslice duration, before
134	  switching to the next context.
135
136	  This is adjustable via
137	  /sys/class/drm/card?/engine/*/timeslice_duration_ms
138
139	  May be 0 to disable timeslicing.