From: Valentin Schneider <vschneid@redhat.com>
To: Schspa Shi <schspa@gmail.com>,
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, dgonyier@redhat.com
Cc: linux-kernel@vger.kernel.org, zhaohui.shi@horizon.ai,
Schspa Shi <schspa@gmail.com>
Subject: Re: [PATCH v8 1/2] sched/rt: fix bad task migration for rt tasks
Date: Tue, 11 Apr 2023 13:23:05 +0100 [thread overview]
Message-ID: <xhsmh4jpma9qu.mognet@vschneid.remote.csb> (raw)
In-Reply-To: <xhsmhile99qdo.mognet@vschneid.remote.csb>
On 06/04/23 12:55, Valentin Schneider wrote:
>
> Sorry, I lost track of that one, and ironically it looks like we've hit
> this bug internally. I'm going to test whether this is the cure we need,
> but even if this isn't the same issue, that patch looks good:
>
> Reviewed-by: Valentin Schneider <vschneid@redhat.com>
>
> I have some more comments on 2/2, but IMO this can go in on its own.
Seems like we were indeed hitting that bug, as we used to have a MTTF of
about 2 hours, and we haven't had any with that patch in 3 days.
Tested-By: Dwaine Gonyier <dgonyier@redhat.com>
prev parent reply other threads:[~2023-04-11 12:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-28 17:03 Schspa Shi
2022-08-28 17:03 ` [PATCH v8 2/2] sched/rt: Trying to push current task when target disable migrating Schspa Shi
2023-04-06 11:55 ` Valentin Schneider
2023-04-12 3:44 ` Schspa Shi
2023-04-06 11:55 ` [PATCH v8 1/2] sched/rt: fix bad task migration for rt tasks Valentin Schneider
2023-04-11 12:23 ` Valentin Schneider [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=xhsmh4jpma9qu.mognet@vschneid.remote.csb \
--to=vschneid@redhat.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dgonyier@redhat.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=schspa@gmail.com \
--cc=vincent.guittot@linaro.org \
--cc=zhaohui.shi@horizon.ai \
/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®