Kconfig.profile (058179e72e0956a2dfe4927db6cbe5fbfb2406aa) | Kconfig.profile (b79029b2e859d8cef534643a1254a833459038f1) |
---|---|
1config DRM_I915_USERFAULT_AUTOSUSPEND 2 int "Runtime autosuspend delay for userspace GGTT mmaps (ms)" 3 default 250 # milliseconds 4 help 5 On runtime suspend, as we suspend the device, we have to revoke 6 userspace GGTT mmaps and force userspace to take a pagefault on 7 their next access. The revocation and subsequent recreation of 8 the GGTT mmap can be very slow and so we impose a small hysteris --- 45 unchanged lines hidden (view full) --- 54 default 100 # milliseconds 55 help 56 By stopping submission and sleeping for a short time before resetting 57 the GPU, we allow the innocent contexts also on the system to quiesce. 58 It is then less likely for a hanging context to cause collateral 59 damage as the system is reset in order to recover. The corollary is 60 that the reset itself may take longer and so be more disruptive to 61 interactive or low latency workloads. | 1config DRM_I915_USERFAULT_AUTOSUSPEND 2 int "Runtime autosuspend delay for userspace GGTT mmaps (ms)" 3 default 250 # milliseconds 4 help 5 On runtime suspend, as we suspend the device, we have to revoke 6 userspace GGTT mmaps and force userspace to take a pagefault on 7 their next access. The revocation and subsequent recreation of 8 the GGTT mmap can be very slow and so we impose a small hysteris --- 45 unchanged lines hidden (view full) --- 54 default 100 # milliseconds 55 help 56 By stopping submission and sleeping for a short time before resetting 57 the GPU, we allow the innocent contexts also on the system to quiesce. 58 It is then less likely for a hanging context to cause collateral 59 damage as the system is reset in order to recover. The corollary is 60 that the reset itself may take longer and so be more disruptive to 61 interactive or low latency workloads. |
62 63config DRM_I915_TIMESLICE_DURATION 64 int "Scheduling quantum for userspace batches (ms, jiffy granularity)" 65 default 1 # milliseconds 66 help 67 When two user batches of equal priority are executing, we will 68 alternate execution of each batch to ensure forward progress of 69 all users. This is necessary in some cases where there may be 70 an implicit dependency between those batches that requires 71 concurrent execution in order for them to proceed, e.g. they 72 interact with each other via userspace semaphores. Each context 73 is scheduled for execution for the timeslice duration, before 74 switching to the next context. 75 76 May be 0 to disable timeslicing. |
|