From: Cheng Chao <cs.os.kernel@gmail.com>
To: mingo@redhat.com, peterz@infradead.org
Cc: linux-kernel@vger.kernel.org, Cheng Chao <cs.os.kernel@gmail.com>,
stable@vger.kernel.org
Subject: [PATCH v2] sched/core: remove unnecessary initialization in sched_init()
Date: Wed, 14 Sep 2016 10:23:02 +0800 [thread overview]
Message-ID: <1473819782-7650-1-git-send-email-cs.os.kernel@gmail.com> (raw)
In-Reply-To: <1473819536-7398-1-git-send-email-cs.os.kernel@gmail.com>
init_idle() is called immediately after current->sched_class
= &fair_sched_class, init_idle() sets current->sched_class
= &idle_sched_class.
Signed-off-by: Cheng Chao <cs.os.kernel@gmail.com>
Cc: stable@vger.kernel.org
---
kernel/sched/core.c | 5 -----
1 file changed, 5 deletions(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index a0086a5..ed4f4fe 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -7557,11 +7557,6 @@ void __init sched_init(void)
enter_lazy_tlb(&init_mm, current);
/*
- * During early bootup we pretend to be a normal task:
- */
- current->sched_class = &fair_sched_class;
-
- /*
* Make us the idle thread. Technically, schedule() should not be
* called from this thread, however somewhere below it might be,
* but because we are the idle thread, we just pick up running again
--
2.4.11
next prev parent reply other threads:[~2016-09-14 2:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 2:18 [PATCH] sched/core: emove unnecessary initialization in sched_init() Cheng Chao
2016-09-14 2:23 ` Cheng Chao [this message]
2016-09-18 1:59 ` [PATCH v2] sched/core: remove " Cheng Chao
2016-09-22 13:58 ` [tip:sched/core] sched/core: Remove " tip-bot for Cheng Chao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1473819782-7650-1-git-send-email-cs.os.kernel@gmail.com \
--to=cs.os.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.