From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 5.6-rc3: WARNING: CPU: 48 PID: 17435 at kernel/sched/fair.c:380 enqueue_task_fair+0x328/0x440
Date: Thu, 5 Mar 2020 13:48:50 +0100 [thread overview]
Message-ID: <a2d6cf51-6d8a-6db3-bdc9-8614e9746349@de.ibm.com> (raw)
In-Reply-To: <20200305123351.GB32088@vingu-book>
On 05.03.20 13:33, Vincent Guittot wrote:
> Le jeudi 05 mars 2020 à 13:12:39 (+0100), Dietmar Eggemann a écrit :
>> On 05/03/2020 12:28, Christian Borntraeger wrote:
>>>
>>> On 05.03.20 10:30, Vincent Guittot wrote:
>>>> Le mercredi 04 mars 2020 à 20:59:33 (+0100), Christian Borntraeger a écrit :
>>>>>
>>>>> On 04.03.20 20:38, Christian Borntraeger wrote:
>>>>>>
>>>>>>
>>>>>> On 04.03.20 20:19, Dietmar Eggemann wrote:
>>
>> [...]
>>
>>> It seems to speed up the issue when I do a compile job in parallel on the host:
>>>
>>> Do you also need the sysfs tree?
>>
>> [ 87.932552] CPU23 path=/machine.slice/machine-test.slice/machine-qemu\x2d18\x2dtest10. on_list=1 nr_running=1 throttled=0 p=[CPU 2/KVM 2662]
>> [ 87.932559] CPU23 path=/machine.slice/machine-test.slice/machine-qemu\x2d18\x2dtest10. on_list=0 nr_running=3 throttled=0 p=[CPU 2/KVM 2662]
>> [ 87.932562] CPU23 path=/machine.slice/machine-test.slice on_list=1 nr_running=1 throttled=1 p=[CPU 2/KVM 2662]
>> [ 87.932564] CPU23 path=/machine.slice on_list=1 nr_running=0 throttled=0 p=[CPU 2/KVM 2662]
>> [ 87.932566] CPU23 path=/ on_list=1 nr_running=1 throttled=0 p=[CPU 2/KVM 2662]
>> [ 87.951872] CPU23 path=/ on_list=1 nr_running=2 throttled=0 p=[ksoftirqd/23 126]
>> [ 87.987528] CPU23 path=/user.slice on_list=1 nr_running=2 throttled=0 p=[as 6737]
>> [ 87.987533] CPU23 path=/ on_list=1 nr_running=1 throttled=0 p=[as 6737]
>>
>> Arrh, looks like 'char path[64]' is too small to hold 'machine.slice/machine-test.slice/machine-qemu\x2d18\x2dtest10.scope/vcpuX' !
>> ^
>> But I guess that the 'on_list=0' for 'machine-qemu\x2d18\x2dtest10.scope' could be the missing hint?
>
> yes the if (cfs_bandwidth_used()) at the end of enqueue_task_fair is not enough
> to ensure that all cfs will be added back. It will "work" for the 1st enqueue
> because the throttled cfs will be added and will reset tmp_alone_branch but not
> for the next one
>
> Compare to the previous proposed fix, we can optimize it a bit with:
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 9ccde775e02e..3b19e508641d 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -4035,10 +4035,16 @@ enqueue_entity(struct cfs_rq *cfs_rq, struct sched_entity *se, int flags)
> __enqueue_entity(cfs_rq, se);
> se->on_rq = 1;
>
> - if (cfs_rq->nr_running == 1) {
> + /*
> + * When bandwidth control is enabled, cfs might have been removed because of
> + * a parent been throttled but cfs->nr_running > 1. Try to add it
> + * unconditionnally.
> + */
> + if (cfs_rq->nr_running == 1 || cfs_bandwidth_used())
This needs a forward declaration for cfs_bandwidth_used, but with that it compiles fine
and its seems to work fine so far. Will keep it running for while.
> list_add_leaf_cfs_rq(cfs_rq);
> +
> + if (cfs_rq->nr_running == 1)
> check_enqueue_throttle(cfs_rq);
> - }
> }
>
> static void __clear_buddies_last(struct sched_entity *se)
next prev parent reply other threads:[~2020-03-05 12:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 7:54 Christian Borntraeger
2020-02-28 12:04 ` Christian Borntraeger
2020-02-28 13:32 ` Vincent Guittot
2020-02-28 13:43 ` Christian Borntraeger
2020-02-28 15:08 ` Christian Borntraeger
2020-02-28 15:37 ` Vincent Guittot
2020-02-28 15:42 ` Christian Borntraeger
2020-02-28 16:32 ` Qais Yousef
2020-02-28 16:35 ` Vincent Guittot
2020-03-02 11:16 ` Christian Borntraeger
2020-03-02 18:17 ` Christian Borntraeger
2020-03-03 7:37 ` Christian Borntraeger
2020-03-03 7:55 ` Vincent Guittot
2020-03-04 15:26 ` Vincent Guittot
2020-03-04 17:42 ` Christian Borntraeger
2020-03-04 17:51 ` Vincent Guittot
2020-03-04 19:19 ` Dietmar Eggemann
2020-03-04 19:38 ` Christian Borntraeger
2020-03-04 19:59 ` Christian Borntraeger
2020-03-05 9:30 ` Vincent Guittot
2020-03-05 11:28 ` Christian Borntraeger
2020-03-05 12:12 ` Dietmar Eggemann
2020-03-05 12:33 ` Vincent Guittot
2020-03-05 12:48 ` Christian Borntraeger [this message]
2020-03-05 13:02 ` Vincent Guittot
2020-03-05 13:18 ` Christian Borntraeger
2020-03-05 12:14 ` Vincent Guittot
2020-03-05 11:54 ` Dietmar Eggemann
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=a2d6cf51-6d8a-6db3-bdc9-8614e9746349@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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®