From: luca abeni <luca.abeni@santannapisa.it>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Juri Lelli <juri.lelli@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Juri Lelli <juri.lelli@gmail.com>,
syzbot <syzbot+385468161961cee80c31@syzkaller.appspotmail.com>,
Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
LKML <linux-kernel@vger.kernel.org>,
mingo@redhat.com, nstange@suse.de,
syzkaller-bugs@googlegroups.com, henrik@austad.us,
Tommaso Cucinotta <tommaso.cucinotta@santannapisa.it>,
Claudio Scordino <claudio@evidence.eu.com>,
Daniel Bristot de Oliveira <bristot@redhat.com>
Subject: Re: INFO: rcu detected stall in do_idle
Date: Fri, 19 Oct 2018 22:50:05 +0200 [thread overview]
Message-ID: <20181019225005.61707c64@nowhere> (raw)
In-Reply-To: <20181019113942.GH3121@hirez.programming.kicks-ass.net>
On Fri, 19 Oct 2018 13:39:42 +0200
Peter Zijlstra <peterz@infradead.org> wrote:
> On Thu, Oct 18, 2018 at 01:08:11PM +0200, luca abeni wrote:
> > Ok, I see the issue now: the problem is that the "while
> > (dl_se->runtime <= 0)" loop is executed at replenishment time, but
> > the deadline should be postponed at enforcement time.
> >
> > I mean: in update_curr_dl() we do:
> > dl_se->runtime -= scaled_delta_exec;
> > if (dl_runtime_exceeded(dl_se) || dl_se->dl_yielded) {
> > ...
> > enqueue replenishment timer at dl_next_period(dl_se)
> > But dl_next_period() is based on a "wrong" deadline!
> >
> >
> > I think that inserting a
> > while (dl_se->runtime <= -pi_se->dl_runtime) {
> > dl_se->deadline += pi_se->dl_period;
> > dl_se->runtime += pi_se->dl_runtime;
> > }
> > immediately after "dl_se->runtime -= scaled_delta_exec;" would fix
> > the problem, no?
>
> That certainly makes sense to me.
Good; I'll try to work on this idea in the weekend.
Thanks,
Luca
> The only remaining issue would then
> be placing a limit on the amount of times we can take that loop;
> which, as you propose in a later email; can be done separately as a
> limit on runtime.
next prev parent reply other threads:[~2018-10-19 20:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-13 7:31 INFO: rcu detected stall in do_idle syzbot
2018-10-16 13:24 ` Thomas Gleixner
2018-10-16 14:03 ` Peter Zijlstra
2018-10-16 14:41 ` Juri Lelli
2018-10-16 14:45 ` Thomas Gleixner
2018-10-16 15:36 ` Juri Lelli
2018-10-18 8:28 ` Juri Lelli
2018-10-18 9:48 ` Peter Zijlstra
2018-10-18 10:10 ` Juri Lelli
2018-10-18 10:38 ` luca abeni
2018-10-18 10:33 ` luca abeni
2018-10-19 13:14 ` Peter Zijlstra
2018-10-18 10:23 ` luca abeni
2018-10-18 10:47 ` Juri Lelli
2018-10-18 11:08 ` luca abeni
2018-10-18 12:21 ` Juri Lelli
2018-10-18 12:36 ` luca abeni
2018-10-19 11:39 ` Peter Zijlstra
2018-10-19 20:50 ` luca abeni [this message]
2018-10-24 12:03 ` Juri Lelli
2018-10-27 11:16 ` Dmitry Vyukov
2018-10-28 8:33 ` Juri Lelli
2018-10-30 10:45 ` Peter Zijlstra
2018-10-30 11:08 ` luca abeni
2018-10-31 16:18 ` Daniel Bristot de Oliveira
2018-10-31 16:40 ` Juri Lelli
2018-10-31 17:39 ` Peter Zijlstra
2018-10-31 17:58 ` Daniel Bristot de Oliveira
2018-11-01 5:55 ` Juri Lelli
2018-11-02 10:00 ` Daniel Bristot de Oliveira
2018-11-05 10:55 ` Juri Lelli
2018-11-07 10:12 ` Daniel Bristot de Oliveira
2018-10-31 17:38 ` Peter Zijlstra
2018-10-30 11:12 ` Juri Lelli
2018-11-06 11:44 ` Juri Lelli
-- strict thread matches above, loose matches on Subject: below --
2021-10-27 0:59 Hao Sun
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=20181019225005.61707c64@nowhere \
--to=luca.abeni@santannapisa.it \
--cc=bp@alien8.de \
--cc=bristot@redhat.com \
--cc=claudio@evidence.eu.com \
--cc=henrik@austad.us \
--cc=hpa@zytor.com \
--cc=juri.lelli@gmail.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nstange@suse.de \
--cc=peterz@infradead.org \
--cc=syzbot+385468161961cee80c31@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=tommaso.cucinotta@santannapisa.it \
/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