diff options
| author | Peter Zijlstra <peterz@infradead.org> | 2019-11-08 14:16:00 +0100 |
|---|---|---|
| committer | Ingo Molnar <mingo@kernel.org> | 2019-11-11 08:35:21 +0100 |
| commit | a0e813f26ebcb25c0b5e504498fbd796cca1a4ba (patch) | |
| tree | c6a926cff783866cc5ee1b20ffefb559e78d45fa /usr | |
| parent | 2eeb01a28c9233333bf229a5b4b0559f4bd22b52 (diff) | |
| download | linux-a0e813f26ebcb25c0b5e504498fbd796cca1a4ba.tar.bz2 | |
sched/core: Further clarify sched_class::set_next_task()
It turns out there really is something special to the first
set_next_task() invocation. In specific the 'change' pattern really
should not cause balance callbacks.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: bsegall@google.com
Cc: dietmar.eggemann@arm.com
Cc: juri.lelli@redhat.com
Cc: ktkhai@virtuozzo.com
Cc: mgorman@suse.de
Cc: qais.yousef@arm.com
Cc: qperret@google.com
Cc: rostedt@goodmis.org
Cc: valentin.schneider@arm.com
Cc: vincent.guittot@linaro.org
Fixes: f95d4eaee6d0 ("sched/{rt,deadline}: Fix set_next_task vs pick_next_task")
Link: https://lkml.kernel.org/r/20191108131909.775434698@infradead.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'usr')
0 files changed, 0 insertions, 0 deletions