From: "tip-bot2 for Wang Hui" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Wang Hui <john.wanghui@huawei.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: sched/core] sched: remove redundant on_rq status change
Date: Thu, 05 Aug 2021 09:34:36 -0000 [thread overview]
Message-ID: <162815607635.395.12214105489940284165.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20210721091109.1406043-1-john.wanghui@huawei.com>
The following commit has been merged into the sched/core branch of tip:
Commit-ID: f912d051619d11411867f642d2004928eb0b41b1
Gitweb: https://git.kernel.org/tip/f912d051619d11411867f642d2004928eb0b41b1
Author: Wang Hui <john.wanghui@huawei.com>
AuthorDate: Wed, 21 Jul 2021 17:11:09 +08:00
Committer: Peter Zijlstra <peterz@infradead.org>
CommitterDate: Wed, 04 Aug 2021 15:16:43 +02:00
sched: remove redundant on_rq status change
activate_task/deactivate_task will change on_rq status,
no need to do it again.
Signed-off-by: Wang Hui <john.wanghui@huawei.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lkml.kernel.org/r/20210721091109.1406043-1-john.wanghui@huawei.com
---
kernel/sched/core.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 0c22cd0..6c562ad 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -5659,11 +5659,9 @@ static bool try_steal_cookie(int this, int that)
if (p->core_occupation > dst->idle->core_occupation)
goto next;
- p->on_rq = TASK_ON_RQ_MIGRATING;
deactivate_task(src, p, 0);
set_task_cpu(p, this);
activate_task(dst, p, 0);
- p->on_rq = TASK_ON_RQ_QUEUED;
resched_curr(dst);
prev parent reply other threads:[~2021-08-05 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 9:11 [PATCH -next] sched: remove redundant on_rq status change Wang Hui
2021-08-05 9:34 ` tip-bot2 for Wang Hui [this message]
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=162815607635.395.12214105489940284165.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=john.wanghui@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).