[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171219193232.gxkwvtz7f4gj7ffz@hirez.programming.kicks-ass.net>
Date: Tue, 19 Dec 2017 20:32:32 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: Claudio Scordino <claudio@...dence.eu.com>,
Juri Lelli <juri.lelli@...il.com>,
Luca Abeni <luca.abeni@...tannapisa.it>,
Tommaso Cucinotta <tommaso.cucinotta@...up.it>,
Ingo Molnar <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
linux-rt-users <linux-rt-users@...r.kernel.org>
Subject: Re: [PATCH v3] sched/deadline: runtime overrun signal
On Tue, Dec 12, 2017 at 12:50:40PM +0100, Ingo Molnar wrote:
>
> * Claudio Scordino <claudio@...dence.eu.com> wrote:
>
> > From: Juri Lelli <juri.lelli@...il.com>
>
> > - ~(SCHED_FLAG_RESET_ON_FORK | SCHED_FLAG_RECLAIM))
> > + ~(SCHED_FLAG_RESET_ON_FORK | SCHED_FLAG_RECLAIM |
> > + SCHED_FLAG_DL_OVERRUN))
Introduced SCHED_FLAG_ALL for this
>
> > + if (dl_runtime_exceeded(dl_se) &&
> > + (dl_se->flags & SCHED_FLAG_DL_OVERRUN))
realigned this one
>
> > + pr_info("runtime overrun: %s[%d]\n",
> > + tsk->comm, task_pid_nr(tsk));
And simply took this out, you asked for it, no reason to tell world
about getting one.
Powered by blists - more mailing lists