From: Hao Jia <jiahao.os@bytedance.com>
To: mingo@redhat.com, peterz@infradead.org, mingo@kernel.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,
vschneid@redhat.com, mgorman@techsingularity.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Fix two warnings about rq clock
Date: Thu, 20 Apr 2023 19:08:24 +0800 [thread overview]
Message-ID: <658fe430-320f-5f4f-2011-9e1bd11d772c@bytedance.com> (raw)
In-Reply-To: <20230410081206.23441-1-jiahao.os@bytedance.com>
kindly ping...
On 2023/4/10 Hao Jia wrote:
> These two patches fix two warnings about rq clock
>
> Patch1 fixes the warning of using the old rq clock caused by
> missing update rq clock.
>
> Patch2 fixes the warning that the rq clock was updated multiple
> times while holding the rq lock.
>
> Hao Jia (2):
> sched/core: Fixed missing rq clock update before calling
> set_rq_offline()
> sched/core: Avoid double calling update_rq_clock()
>
> kernel/sched/core.c | 11 +++++++----
> kernel/sched/fair.c | 9 ++++++---
> kernel/sched/topology.c | 10 ++++++----
> 3 files changed, 19 insertions(+), 11 deletions(-)
>
prev parent reply other threads:[~2023-04-20 11:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 8:12 Hao Jia
2023-04-10 8:12 ` [PATCH 1/2] sched/core: Fixed missing rq clock update before calling set_rq_offline() Hao Jia
2023-04-10 8:12 ` [PATCH 2/2] sched/core: Avoid double calling update_rq_clock() Hao Jia
2023-04-21 13:44 ` Vincent Guittot
2023-05-02 10:22 ` [External] " Hao Jia
2023-05-04 16:03 ` Vincent Guittot
2023-05-05 12:13 ` Hao Jia
2023-05-09 16:26 ` Vincent Guittot
2023-04-20 11:08 ` Hao Jia [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=658fe430-320f-5f4f-2011-9e1bd11d772c@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=mgorman@techsingularity.net \
--cc=mingo@kernel.org \
--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 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®