From: Hao Jia <jiahao.os@bytedance.com>
To: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
bristot@redhat.com
Cc: linux-kernel@vger.kernel.org, Hao Jia <jiahao.os@bytedance.com>
Subject: [PATCH v2 0/2] Avoid obvious double update_rq_clock warning
Date: Fri, 22 Apr 2022 17:09:42 +0800 [thread overview]
Message-ID: <20220422090944.52618-1-jiahao.os@bytedance.com> (raw)
These two patches are about the kernel scheduler:
patch 1: fixed the issue that kernel may trigger WARN_DOUBLE_CLOCK warning.
patch 2: removed some no longer needed comments in the deadline scheduler
and cleaned up the code.
v2:
- Added double_rq_clock_clear_update inline helper to clear RQCF_UPDATED
of rq->clock_update_flags.
- split into two separate patches.
[1] https://lore.kernel.org/lkml/20220418090929.54005-1-jiahao.os@bytedance.com/
Hao Jia (2):
sched/core: Avoid obvious double update_rq_clock warning
sched/dl: Remove some comments and adjust code in push_dl_task
kernel/sched/core.c | 6 +++---
kernel/sched/deadline.c | 8 +-------
kernel/sched/rt.c | 5 +++--
kernel/sched/sched.h | 31 +++++++++++++++++++++++++++----
4 files changed, 34 insertions(+), 16 deletions(-)
--
2.32.0
next reply other threads:[~2022-04-22 9:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 9:09 Hao Jia [this message]
2022-04-22 9:09 ` [PATCH v2 1/2] sched/core: Avoid obvious double update_rq_clock warning Hao Jia
2022-04-25 15:37 ` Dietmar Eggemann
2022-04-26 7:57 ` [External] " Hao Jia
2022-04-22 9:09 ` [PATCH v2 2/2] sched/dl: Remove some comments and adjust code in push_dl_task Hao Jia
2022-04-25 16:21 ` Dietmar Eggemann
2022-04-26 8:01 ` [External] " Hao Jia
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=20220422090944.52618-1-jiahao.os@bytedance.com \
--to=jiahao.os@bytedance.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 \
/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).