All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Qais Yousef <qais.yousef@arm.com>
Cc: Ingo Molnar <mingo@kernel.org>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Patrick Bellasi <patrick.bellasi@matbug.net>,
	Tejun Heo <tj@kernel.org>, Quentin Perret <qperret@google.com>,
	Wei Wang <wvw@google.com>, Yun Hsiang <hsiang023167@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 0/2] Uclamp cgroup fixes
Date: Thu, 13 May 2021 16:13:36 +0200	[thread overview]
Message-ID: <YJ00EB3MeUo3Inoy@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20210510145032.1934078-1-qais.yousef@arm.com>

On Mon, May 10, 2021 at 03:50:30PM +0100, Qais Yousef wrote:
> A couple of fixes for uclamp cgroup. The first one is addressing wrong
> implementation details that is restricting usability of uclamp in cgroup. The
> 2nd is fixing locking issues.
> 
> This is a resend since I forgot to CC LKML...
> 
> Qais Yousef (2):
>   sched/uclamp: Fix wrong implementation of cpu.uclamp.min
>   sched/uclamp: Fix locking around cpu_util_update_eff()
> 
>  kernel/sched/core.c | 28 ++++++++++++++++++++++++----
>  1 file changed, 24 insertions(+), 4 deletions(-)

Thanks!

      parent reply	other threads:[~2021-05-13 14:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10 14:50 [PATCH RESEND 0/2] Uclamp cgroup fixes Qais Yousef
2021-05-10 14:50 ` [PATCH RESEND 1/2] sched/uclamp: Fix wrong implementation of cpu.uclamp.min Qais Yousef
2021-05-19  8:09   ` [tip: sched/core] " tip-bot2 for Qais Yousef
2021-05-19  9:02   ` tip-bot2 for Qais Yousef
2021-05-10 14:50 ` [PATCH RESEND 2/2] sched/uclamp: Fix locking around cpu_util_update_eff() Qais Yousef
2021-05-19  8:09   ` [tip: sched/core] " tip-bot2 for Qais Yousef
2021-05-19  9:02   ` tip-bot2 for Qais Yousef
2021-05-13 14:13 ` Peter Zijlstra [this message]

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=YJ00EB3MeUo3Inoy@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=dietmar.eggemann@arm.com \
    --cc=hsiang023167@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=patrick.bellasi@matbug.net \
    --cc=qais.yousef@arm.com \
    --cc=qperret@google.com \
    --cc=tj@kernel.org \
    --cc=vincent.guittot@linaro.org \
    --cc=wvw@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 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.