diff options
Diffstat (limited to 'litmus/Kconfig')
-rw-r--r-- | litmus/Kconfig | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/litmus/Kconfig b/litmus/Kconfig index c05405094ea4..594c54342bdc 100644 --- a/litmus/Kconfig +++ b/litmus/Kconfig | |||
@@ -210,6 +210,14 @@ choice | |||
210 | Break ties between two jobs, A and B, with equal deadlines by using a | 210 | Break ties between two jobs, A and B, with equal deadlines by using a |
211 | uniform hash; i.e.: hash(A.pid, A.job_num) < hash(B.pid, B.job_num). Job | 211 | uniform hash; i.e.: hash(A.pid, A.job_num) < hash(B.pid, B.job_num). Job |
212 | A has ~50% of winning a given tie-break. | 212 | A has ~50% of winning a given tie-break. |
213 | |||
214 | NOTES: | ||
215 | * This method doesn't work very well if a tied job has a low-valued | ||
216 | hash while the jobs it ties with do not make progress (that is, | ||
217 | they don't increment to new job numbers). The job with a low-valued | ||
218 | hash job will lose most tie-breaks. This is usually not a problem | ||
219 | unless you are doing something funky in Litmus (ex. worker threads | ||
220 | that do not increment job numbers). | ||
213 | 221 | ||
214 | config EDF_PID_TIE_BREAK | 222 | config EDF_PID_TIE_BREAK |
215 | bool "PID-based Tie Breaks" | 223 | bool "PID-based Tie Breaks" |
@@ -363,7 +371,7 @@ config SCHED_DEBUG_TRACE_CALLER | |||
363 | 371 | ||
364 | config PREEMPT_STATE_TRACE | 372 | config PREEMPT_STATE_TRACE |
365 | bool "Trace preemption state machine transitions" | 373 | bool "Trace preemption state machine transitions" |
366 | depends on SCHED_DEBUG_TRACE | 374 | depends on SCHED_DEBUG_TRACE && DEBUG_KERNEL |
367 | default n | 375 | default n |
368 | help | 376 | help |
369 | With this option enabled, each CPU will log when it transitions | 377 | With this option enabled, each CPU will log when it transitions |