From: Ilya Maximets <i.maximets@ovn.org>
To: Vineeth Remanan Pillai <vineeth@bitbyteword.org>
Cc: i.maximets@ovn.org, Peter Zijlstra <peterz@infradead.org>,
Joel Fernandes <joel@joelfernandes.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
vineethrp@google.com, shraash@google.com,
marcel.ziswiler@codethink.co.uk
Subject: Re: [v6.12] WARNING: at kernel/sched/deadline.c:1995 enqueue_dl_entity (task blocked for more than 28262 seconds)
Date: Wed, 11 Dec 2024 10:48:28 +0100 [thread overview]
Message-ID: <01e7f4a1-9fbd-44fa-a590-3fa0a7a5ab46@ovn.org> (raw)
In-Reply-To: <CAO7JXPh40hhge6dSHj1=jERj63HSmXnNPd16_VXDbxapiTCzHA@mail.gmail.com>
On 12/11/24 03:30, Vineeth Remanan Pillai wrote:
>>> /*
>>> - * Any fair task that runs outside of fair_server should
>>> - * account against fair_server such that it can account for
>>> - * this time and possibly avoid running this period.
>>> + * If the fair_server is active, we need to account for the
>>> + * fair_server time whether or not the task is running on
>>> + * behalf of fair_server or not:
>>> + * - If the task is running on behalf of fair_server, we need
>>> + * to limit its time based on the assigned runtime.
>>> + * - Fair task that runs outside of fair_server should account
>>> + * against fair_server such that it can account for this time
>>> + * and possibly avoid running this period.
>>> */
>>> - if (p->dl_server != &rq->fair_server)
>>> + if (dl_server_active(&rq->fair_server))
>>> dl_server_update(&rq->fair_server, delta_exec);
>>> }
>>
>> That indeed also fixes it for me.
>>
> Thanks for the confirmation Marcel
>
>>>>
>>>> "static inline bool dl_server_active(struct sched_dl_entity *dl_se)"
>>>
>>> Sure. I can try that.
>>
>> Running with this for about 8 hours and so far so good.
>> Will leave the test running for the night, just in case.
>>
> Thanks for the update Ilya
>
> I also have been running the test for more than 24 hours now and did
> not encounter warnings or crashes.
Nice! On my side, another 11 hours and no issues observed.
>
> Juri, Peter, Shall I go ahead and send out a single patch folding the
> 2 fixes in this thread(dl_server_active and fix for the
> dl_server_update call)?
>
> Thanks,
> Vineeth
next prev parent reply other threads:[~2024-12-11 9:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 12:47 Ilya Maximets
2024-12-06 15:18 ` Joel Fernandes
2024-12-06 16:57 ` Vineeth Remanan Pillai
2024-12-06 17:24 ` Joel Fernandes
2024-12-09 10:48 ` Juri Lelli
2024-12-09 10:55 ` Peter Zijlstra
2024-12-09 12:29 ` Vineeth Remanan Pillai
2024-12-09 12:34 ` Ilya Maximets
2024-12-10 0:31 ` Ilya Maximets
2024-12-09 12:56 ` Peter Zijlstra
2024-12-09 13:56 ` Vineeth Remanan Pillai
2024-12-09 14:01 ` Peter Zijlstra
2024-12-09 14:12 ` Vineeth Remanan Pillai
2024-12-10 0:34 ` Ilya Maximets
2024-12-10 2:52 ` Vineeth Remanan Pillai
2024-12-10 2:58 ` Vineeth Remanan Pillai
2024-12-10 9:28 ` Ilya Maximets
2024-12-10 23:16 ` Ilya Maximets
2024-12-11 2:30 ` Vineeth Remanan Pillai
2024-12-11 9:48 ` Ilya Maximets [this message]
2024-12-10 16:11 ` Marcel Ziswiler
2024-12-10 16:08 ` Marcel Ziswiler
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=01e7f4a1-9fbd-44fa-a590-3fa0a7a5ab46@ovn.org \
--to=i.maximets@ovn.org \
--cc=joel@joelfernandes.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel.ziswiler@codethink.co.uk \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=shraash@google.com \
--cc=vincent.guittot@linaro.org \
--cc=vineeth@bitbyteword.org \
--cc=vineethrp@google.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®