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
Subject: Re: [PATCH v4 0/2] sched/core: Avoid obvious double update_rq_clock warning
Date: Mon, 9 May 2022 11:16:39 +0800 [thread overview]
Message-ID: <20b9822d-4a87-c868-1683-30b0a7e97777@bytedance.com> (raw)
In-Reply-To: <20220430085843.62939-1-jiahao.os@bytedance.com>
Friendly ping...
Hi Dietmar Eggemann & Peter Zijlstra,
If you have time, please review these two patches.
On 2022/4/30 Hao Jia wrote:
> 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.
>
> Thanks for suggestion from Dietmar Eggemann & Peter Zijlstra.
>
> v3->v4:
> - Modify some code formats and commit messages.
> - Add Reviewed-by: Dietmar Eggemann <dietmar.eggemann@arm.com> for
> patch 1.
> - Add Reviewed-by: Daniel Bristot de Oliveira <bristot@redhat.com>
> for patch 2.
>
> v2->v3:
> - Modify some descriptions and errors in the commit information.
> - Fixed a bug that might trigger the WARN_DOUBLE_CLOCK warning in
> migrate_task_rq_dl().
> - Add Reviewed-by: Dietmar Eggemann <dietmar.eggemann@arm.com> for
> patch 2.
>
> v1->v2:
> - Added double_rq_clock_clear_update inline helper to clear RQCF_UPDATED
> of rq->clock_update_flags.
> - split into two separate patches.
>
> [v1] https://lore.kernel.org/lkml/20220418090929.54005-1-jiahao.os@bytedance.com/
> [v2] https://lore.kernel.org/lkml/20220422090944.52618-1-jiahao.os@bytedance.com/
> [v3] https://lore.kernel.org/all/20220427080014.18483-1-jiahao.os@bytedance.com/
>
> Hao Jia (2):
> sched/core: Avoid obvious double update_rq_clock warning
> sched/deadline: Remove superfluous rq clock update in push_dl_task()
>
> kernel/sched/core.c | 6 +++---
> kernel/sched/deadline.c | 13 ++++---------
> kernel/sched/rt.c | 5 +++--
> kernel/sched/sched.h | 28 ++++++++++++++++++++++++----
> 4 files changed, 34 insertions(+), 18 deletions(-)
>
next prev parent reply other threads:[~2022-05-09 3:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-30 8:58 Hao Jia
2022-04-30 8:58 ` [PATCH v4 1/2] " Hao Jia
2022-05-11 19:47 ` [tip: sched/core] " tip-bot2 for Hao Jia
2022-04-30 8:58 ` [PATCH v4 2/2] sched/deadline: Remove superfluous rq clock update in push_dl_task() Hao Jia
2022-05-11 19:47 ` [tip: sched/core] " tip-bot2 for Hao Jia
2022-05-09 3:16 ` Hao Jia [this message]
2022-05-09 8:08 ` [PATCH v4 0/2] sched/core: Avoid obvious double update_rq_clock warning Peter Zijlstra
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=20b9822d-4a87-c868-1683-30b0a7e97777@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
all inboxes | Powered by JetHome®