From: Sidney Cammeresi <sac@mariadb.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/1] fix incorrect comment in kernel/sched/rt.c
Date: Tue, 10 Nov 2020 11:12:18 -0800 [thread overview]
Message-ID: <cover.1605034896.git.sac@cheesecake.org> (raw)
I was reading rt.c and was looking at the code pertaining to allowing a
non-migratable task to preempt a migratable task of the same priority.
It appears to me that one of the comments describing when this will
happen is wrong.
It appears that preemption will only happen when the task is *not* about
to be otherwise preempted. The comment appears to describe an older
version of the code, in which preemption would happen when the task *was*
about to be preempted, the opposite condition.
Sidney Cammeresi (1):
sched/rt: fix incorrect comment about non-migratable tasks' priority
kernel/sched/rt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.7.4
--
Sidney Cammeresi
Staff Software Engineer, MariaDB Corporation Ab
next reply other threads:[~2020-11-10 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 19:12 Sidney Cammeresi [this message]
2020-11-10 19:12 ` [PATCH] sched/rt: fix incorrect comment about non-migratable tasks' priority Sidney Cammeresi
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=cover.1605034896.git.sac@cheesecake.org \
--to=sac@mariadb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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).