All of lore.kernel.org
 help / color / mirror / Atom feed
From: Quentin Perret <qperret@google.com>
To: Dietmar Eggemann <dietmar.eggemann@arm.com>
Cc: mingo@redhat.com, peterz@infradead.org,
	vincent.guittot@linaro.org, qais.yousef@arm.com,
	rickyiu@google.com, wvw@google.com, patrick.bellasi@matbug.net,
	xuewen.yan94@gmail.com, linux-kernel@vger.kernel.org,
	kernel-team@android.com
Subject: Re: [PATCH v4 2/2] sched: Skip priority checks with SCHED_FLAG_KEEP_PARAMS
Date: Tue, 27 Jul 2021 11:16:48 +0100	[thread overview]
Message-ID: <YP/dEMeULqozIqZd@google.com> (raw)
In-Reply-To: <YP6++lClPCQvTLcK@google.com>

On Monday 26 Jul 2021 at 14:56:10 (+0100), Quentin Perret wrote:
> On Thursday 22 Jul 2021 at 10:47:33 (+0200), Dietmar Eggemann wrote:
> > (*) This changes the behaviour when setting uclamp values on a DL task.
> > 
> > Before uclamp values could be set but now, because of
> > 
> >   void __getparam_dl(struct task_struct *p, struct sched_attr *attr)
> >     ..
> >     attr->sched_flags = dl_se->flags
> > 
> > SCHED_FLAG_UTIL_CLAMP gets overwritten and  __sched_setscheduler() bails in:
> > 
> >     if (unlikely(policy == p->policy)) {
> >       ...
> >       retval = 0;
> >       goto unlock;
> >     }
> >   change:
> > 
> > I.e. the:
> > 
> >       if (attr->sched_flags & SCHED_FLAG_UTIL_CLAMP)
> >         goto change;
> > 
> > can't trigger anymore.
> 
> Bah, as you said it doesn't seem to be a big deal, but clearly that was
> unintentional. Let me try and fix this.

While looking at this I found existing bugs in the area. Fixes are here:

https://lore.kernel.org/lkml/20210727101103.2729607-1-qperret@google.com/

And with the above series applied this patch should behave correctly
now.

Thanks,
Quentin

  reply	other threads:[~2021-07-27 10:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 16:16 [PATCH v4 0/2] A couple of uclamp fixes Quentin Perret
2021-07-19 16:16 ` [PATCH v4 1/2] sched: Fix UCLAMP_FLAG_IDLE setting Quentin Perret
2021-07-21 10:07   ` Dietmar Eggemann
2021-07-21 13:09     ` Quentin Perret
2021-07-22  8:47       ` Dietmar Eggemann
2021-07-27 14:32   ` Qais Yousef
2021-07-19 16:16 ` [PATCH v4 2/2] sched: Skip priority checks with SCHED_FLAG_KEEP_PARAMS Quentin Perret
2021-07-22  8:47   ` Dietmar Eggemann
2021-07-26 13:56     ` Quentin Perret
2021-07-27 10:16       ` Quentin Perret [this message]
2021-07-29 17:34         ` Dietmar Eggemann
2021-07-29 17:31       ` 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=YP/dEMeULqozIqZd@google.com \
    --to=qperret@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=patrick.bellasi@matbug.net \
    --cc=peterz@infradead.org \
    --cc=qais.yousef@arm.com \
    --cc=rickyiu@google.com \
    --cc=vincent.guittot@linaro.org \
    --cc=wvw@google.com \
    --cc=xuewen.yan94@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.