Messages in this thread Patch in this message | | | From | Nicholas Piggin <> | Subject | [PATCH 1/4] sched/core: allow the remote scheduler tick to be started on CPU0 | Date | Thu, 4 Apr 2019 22:07:01 +1000 |
| |
This has on effect yet because CPU0 will always be a housekeeping CPU until a later change.
Signed-off-by: Nicholas Piggin <npiggin@gmail.com> --- kernel/sched/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c index 4778c48a7fda..10e05ec049b6 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -5918,7 +5918,7 @@ void __init sched_init_smp(void) static int __init migration_init(void) { - sched_rq_cpu_starting(smp_processor_id()); + sched_cpu_starting(smp_processor_id()); return 0; } early_initcall(migration_init); -- 2.20.1
| |