[linux-2.6-block.git] / drivers / gpu / drm / i915 / Kconfig.profile

config DRM_I915_REQUEST_TIMEOUT
	int "Default timeout for requests (ms)"
	default 20000 # milliseconds
	help
	  Configures the default timeout after which any user submissions will
	  be forcefully terminated.

	  Beware setting this value lower, or close to heartbeat interval
	  rounded to whole seconds times three, in order to avoid allowing
	  misbehaving applications causing total rendering failure in unrelated
	  clients.

	  May be 0 to disable the timeout.

config DRM_I915_FENCE_TIMEOUT
	int "Timeout for unsignaled foreign fences (ms, jiffy granularity)"
	default 10000 # milliseconds
	help
	  When listening to a foreign fence, we install a supplementary timer
	  to ensure that we are always signaled and our userspace is able to
	  make forward progress. This value specifies the timeout used for an
	  unsignaled foreign fence.

	  May be 0 to disable the timeout, and rely on the foreign fence being
	  eventually signaled.

config DRM_I915_USERFAULT_AUTOSUSPEND
	int "Runtime autosuspend delay for userspace GGTT mmaps (ms)"
	default 250 # milliseconds
	help
	  On runtime suspend, as we suspend the device, we have to revoke
	  userspace GGTT mmaps and force userspace to take a pagefault on
	  their next access. The revocation and subsequent recreation of
	  the GGTT mmap can be very slow and so we impose a small hysteris
	  that complements the runtime-pm autosuspend and provides a lower
	  floor on the autosuspend delay.

	  May be 0 to disable the extra delay and solely use the device level
	  runtime pm autosuspend delay tunable.

config DRM_I915_HEARTBEAT_INTERVAL
	int "Interval between heartbeat pulses (ms)"
	default 2500 # milliseconds
	help
	  The driver sends a periodic heartbeat down all active engines to
	  check the health of the GPU and undertake regular house-keeping of
	  internal driver state.

	  This is adjustable via
	  /sys/class/drm/card?/engine/*/heartbeat_interval_ms

	  May be 0 to disable heartbeats and therefore disable automatic GPU
	  hang detection.

config DRM_I915_PREEMPT_TIMEOUT
	int "Preempt timeout (ms, jiffy granularity)"
	default 640 # milliseconds
	help
	  How long to wait (in milliseconds) for a preemption event to occur
	  when submitting a new context via execlists. If the current context
	  does not hit an arbitration point and yield to HW before the timer
	  expires, the HW will be reset to allow the more important context
	  to execute.

	  This is adjustable via
	  /sys/class/drm/card?/engine/*/preempt_timeout_ms

	  May be 0 to disable the timeout.

	  The compiled in default may get overridden at driver probe time on
	  certain platforms and certain engines which will be reflected in the
	  sysfs control.

config DRM_I915_MAX_REQUEST_BUSYWAIT
	int "Busywait for request completion limit (ns)"
	default 8000 # nanoseconds
	help
	  Before sleeping waiting for a request (GPU operation) to complete,
	  we may spend some time polling for its completion. As the IRQ may
	  take a non-negligible time to setup, we do a short spin first to
	  check if the request will complete in the time it would have taken
	  us to enable the interrupt.

	  This is adjustable via
	  /sys/class/drm/card?/engine/*/max_busywait_duration_ns

	  May be 0 to disable the initial spin. In practice, we estimate
	  the cost of enabling the interrupt (if currently disabled) to be
	  a few microseconds.

config DRM_I915_STOP_TIMEOUT
	int "How long to wait for an engine to quiesce gracefully before reset (ms)"
	default 100 # milliseconds
	help
	  By stopping submission and sleeping for a short time before resetting
	  the GPU, we allow the innocent contexts also on the system to quiesce.
	  It is then less likely for a hanging context to cause collateral
	  damage as the system is reset in order to recover. The corollary is
	  that the reset itself may take longer and so be more disruptive to
	  interactive or low latency workloads.

	  This is adjustable via
	  /sys/class/drm/card?/engine/*/stop_timeout_ms

config DRM_I915_TIMESLICE_DURATION
	int "Scheduling quantum for userspace batches (ms, jiffy granularity)"
	default 1 # milliseconds
	help
	  When two user batches of equal priority are executing, we will
	  alternate execution of each batch to ensure forward progress of
	  all users. This is necessary in some cases where there may be
	  an implicit dependency between those batches that requires
	  concurrent execution in order for them to proceed, e.g. they
	  interact with each other via userspace semaphores. Each context
	  is scheduled for execution for the timeslice duration, before
	  switching to the next context.

	  This is adjustable via
	  /sys/class/drm/card?/engine/*/timeslice_duration_ms

	  May be 0 to disable timeslicing.
Commit	Line	Data
e8dbb566 TU	1	config 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
16dc224f CW	15	config 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
b27e35ae CW	27	config 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
058179e7 CW	41	config 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
9a40bddd CW	49	This is adjustable via
	50	/sys/class/drm/card?/engine/*/heartbeat_interval_ms
	51
058179e7 CW	52	May be 0 to disable heartbeats and therefore disable automatic GPU
	53	hang detection.
	54
3a7a92ab CW	55	config DRM_I915_PREEMPT_TIMEOUT
3a7a92ab CW	56	int "Preempt timeout (ms, jiffy granularity)"
5766a5ff	57	default 640 # milliseconds
3a7a92ab CW	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
db3d8338 CW	65	This is adjustable via
	66	/sys/class/drm/card?/engine/*/preempt_timeout_ms
	67
3a7a92ab CW	68	May be 0 to disable the timeout.
3a7a92ab CW	69
07bcfd12 TU	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
062444bb CW	74	config DRM_I915_MAX_REQUEST_BUSYWAIT
	75	int "Busywait for request completion limit (ns)"
	76	default 8000 # nanoseconds
7ce99d24 CW	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
062444bb CW	84	This is adjustable via
	85	/sys/class/drm/card?/engine/*/max_busywait_duration_ns
	86
7ce99d24 CW	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.
a8c51ed2 CW	90
	91	config 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.
b79029b2	101
72338a1f CW	102	This is adjustable via
	103	/sys/class/drm/card?/engine/*/stop_timeout_ms
	104
b79029b2 CW	105	config 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
1a2695a7 CW	118	This is adjustable via
	119	/sys/class/drm/card?/engine/*/timeslice_duration_ms
	120
b79029b2	121	May be 0 to disable timeslicing.