From: Quentin Perret <qperret@google.com>
To: mingo@redhat.com, peterz@infradead.org,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
qais.yousef@arm.com, rickyiu@google.com, wvw@google.com,
patrick.bellasi@matbug.net, xuewen.yan94@gmail.com
Cc: linux-kernel@vger.kernel.org, kernel-team@android.com,
Quentin Perret <qperret@google.com>
Subject: [PATCH v2 0/3] A few uclamp fixes
Date: Thu, 10 Jun 2021 15:13:03 +0000 [thread overview]
Message-ID: <20210610151306.1789549-1-qperret@google.com> (raw)
Hi all,
This series groups together the v2 of a few patches I orignally sent
independently from each others:
https://lore.kernel.org/r/20210609143339.1194238-1-qperret@google.com
https://lore.kernel.org/r/20210609170132.1386495-1-qperret@google.com
https://lore.kernel.org/r/20210609175901.1423553-1-qperret@google.com
But since they're all touching uclamp-related things, I figured I might
as well group them in a series.
The first one is a pure fix, and the two others change a bit the
sched_setattr behaviour for uclamp to make it more convenient to use,
and allow to put restrictions on the per-task API.
Changes since v1:
- fixed the CAP_SYS_NICE check to handle the uclamp_{min,max} = -1
cases correctly;
- fixed commit message of UCLAMP_FLAG_IDLE patch.
Thanks,
Quentin
Quentin Perret (3):
sched: Fix UCLAMP_FLAG_IDLE setting
sched: Skip priority checks with SCHED_FLAG_KEEP_PARAMS
sched: Make uclamp changes depend on CAP_SYS_NICE
kernel/sched/core.c | 64 +++++++++++++++++++++++++++++++++++++--------
1 file changed, 53 insertions(+), 11 deletions(-)
--
2.32.0.272.g935e593368-goog
next reply other threads:[~2021-06-10 15:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 15:13 Quentin Perret [this message]
2021-06-10 15:13 ` [PATCH v2 1/3] sched: Fix UCLAMP_FLAG_IDLE setting Quentin Perret
2021-06-10 19:05 ` Peter Zijlstra
2021-06-11 7:25 ` Quentin Perret
2021-06-17 15:27 ` Dietmar Eggemann
2021-06-21 10:57 ` Quentin Perret
2021-06-10 15:13 ` [PATCH v2 2/3] sched: Skip priority checks with SCHED_FLAG_KEEP_PARAMS Quentin Perret
2021-06-10 19:15 ` Peter Zijlstra
2021-06-11 8:59 ` Quentin Perret
2021-06-11 9:07 ` Quentin Perret
2021-06-11 9:20 ` Peter Zijlstra
2021-06-10 15:13 ` [PATCH v2 3/3] sched: Make uclamp changes depend on CAP_SYS_NICE Quentin Perret
2021-06-11 12:48 ` Qais Yousef
2021-06-11 13:08 ` Quentin Perret
2021-06-11 13:26 ` Qais Yousef
2021-06-11 13:49 ` Quentin Perret
2021-06-11 14:17 ` Qais Yousef
2021-06-11 14:43 ` Quentin Perret
2021-06-14 15:03 ` Qais Yousef
2021-06-21 10:52 ` Quentin Perret
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=20210610151306.1789549-1-qperret@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox