From: Schspa Shi <schspa@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
bsegall@google.com, mgorman@suse.de, bristot@redhat.com,
vschneid@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/2] sched/rt: Trying to push current task when target disable migrating
Date: Tue, 12 Jul 2022 22:34:40 +0800 [thread overview]
Message-ID: <m2fsj6flfk.fsf@gmail.com> (raw)
In-Reply-To: <20220712102953.02d4a3bd@gandalf.local.home>
Steven Rostedt <rostedt@goodmis.org> writes:
> On Tue, 12 Jul 2022 09:31:25 +0800
> Schspa Shi <schspa@gmail.com> wrote:
>
>> When the task to push disable migration, retry to push the current
>> running task on this CPU away, instead doing nothing for this migrate
>> disabled task.
>>
>> Signed-off-by: Schspa Shi <schspa@gmail.com>
>> ---
>> kernel/sched/core.c | 6 +++++-
>> kernel/sched/rt.c | 6 ++++++
>> 2 files changed, 11 insertions(+), 1 deletion(-)
>>
>> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
>> index da0bf6fe9ecdc..0b1fefd97d874 100644
>> --- a/kernel/sched/core.c
>> +++ b/kernel/sched/core.c
>> @@ -2509,8 +2509,12 @@ int push_cpu_stop(void *arg)
>> if (p->sched_class->find_lock_rq)
>> lowest_rq = p->sched_class->find_lock_rq(p, rq);
>>
>> - if (!lowest_rq)
>> + if (!lowest_rq) {
>
> Probably should add a comment reminding us that the find_lock() function
> above could have released the rq lock and allow p to schedule and be
> preempted again, and that lowest_rq could be NULL because p now has the
> migrate_disable flag set and not because it could not find the lowest rq.
>
OK, it will be better.
Let me upload a v6 patch for that.
> -- Steve
>
>
>> + if (unlikely(is_migration_disabled(p)))
>> + p->migration_flags |= MDF_PUSH;
>> +
>> goto out_unlock;
>> + }
>>
>> // XXX validate p is still the highest prio task
>> if (task_rq(p) == rq) {
>> diff --git a/kernel/sched/rt.c b/kernel/sched/rt.c
>> index 7c32ba51b6d85..877380e465b7a 100644
>> --- a/kernel/sched/rt.c
>> +++ b/kernel/sched/rt.c
>> @@ -2136,6 +2136,12 @@ static int push_rt_task(struct rq *rq, bool pull)
>> */
>> task = pick_next_pushable_task(rq);
>> if (task == next_task) {
>> + /*
>> + * If next task has now disabled migrating, see if we
>> + * can push the current task.
>> + */
>> + if (unlikely(is_migration_disabled(task)))
>> + goto retry;
>> /*
>> * The task hasn't migrated, and is still the next
>> * eligible task, but we failed to find a run-queue
--
BRs
Schspa Shi
next prev parent reply other threads:[~2022-07-12 14:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 1:31 [PATCH v5 1/2] sched/rt: fix bad task migration for rt tasks Schspa Shi
2022-07-12 1:31 ` [PATCH v5 2/2] sched/rt: Trying to push current task when target disable migrating Schspa Shi
2022-07-12 14:29 ` Steven Rostedt
2022-07-12 14:34 ` Schspa Shi [this message]
2022-07-12 13:53 ` [PATCH v5 1/2] sched/rt: fix bad task migration for rt tasks Steven Rostedt
2022-07-12 14:37 ` Schspa Shi
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=m2fsj6flfk.fsf@gmail.com \
--to=schspa@gmail.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
/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.