From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] sched/core for v5.17
Date: Tue, 11 Jan 2022 18:23:01 +0100 [thread overview]
Message-ID: <Yd289b35jcsSdJfl@zn.tnic> (raw)
Hi Linus,
please pull the sched/core pile for 5.17.
Thx.
---
The following changes since commit fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf:
Linux 5.16-rc1 (2021-11-14 13:56:52 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/sched_core_for_v5.17_rc1
for you to fetch changes up to 82762d2af31a60081162890983a83499c9c7dd74:
sched/fair: Replace CFS internal cpu_util() with cpu_util_cfs() (2021-12-11 09:10:00 +0100)
----------------------------------------------------------------
Peter Zijlstra says:
"Mostly minor things this time; some highlights:
- core-sched: Add 'Forced Idle' accounting; this allows to track how
much CPU time is 'lost' due to core scheduling constraints.
- psi: Fix for MEM_FULL; a task running reclaim would be counted as a
runnable task and prevent MEM_FULL from being reported.
- cpuacct: Long standing fixes for some cgroup accounting issues.
- rt: Bandwidth timer could, under unusual circumstances, be failed to
armed, leading to indefinite throttling."
----------------------------------------------------------------
Andrey Ryabinin (4):
cputime, cpuacct: Include guest time in user time in cpuacct.stat
cpuacct: Convert BUG_ON() to WARN_ON_ONCE()
sched/cpuacct: Fix user/system in shown cpuacct.usage*
sched/cpuacct: Make user/system times in cpuacct.stat more precise
Barry Song (1):
sched/fair: Document the slow path and fast path in select_task_rq_fair
Brian Chen (1):
psi: Fix PSI_MEM_FULL state when tasks are in memstall and doing reclaim
Dietmar Eggemann (1):
sched/fair: Replace CFS internal cpu_util() with cpu_util_cfs()
Josh Don (1):
sched/core: Forced idle accounting
Li Hua (1):
sched/rt: Try to restart rt period timer when rt runtime exceeded
Liu Xinpeng (2):
psi: Remove repeated verbose comment
psi: Add a missing SPDX license header
Vincent Donnefort (3):
sched/fair: Fix detection of per-CPU kthreads waking a task
sched/fair: Fix per-CPU kthread and wakee stacking for asym CPU capacity
sched/fair: Cleanup task_util and capacity type
include/linux/psi.h | 1 +
include/linux/psi_types.h | 14 ++++-
include/linux/sched.h | 4 ++
kernel/sched/core.c | 84 ++++++++++++++++++++++--------
kernel/sched/core_sched.c | 66 +++++++++++++++++++++++-
kernel/sched/cpuacct.c | 107 ++++++++++++++++++---------------------
kernel/sched/cpufreq_schedutil.c | 2 +-
kernel/sched/cputime.c | 4 +-
kernel/sched/debug.c | 4 ++
kernel/sched/fair.c | 87 ++++++++-----------------------
kernel/sched/psi.c | 47 ++++++++++-------
kernel/sched/rt.c | 23 +++++++--
kernel/sched/sched.h | 76 ++++++++++++++++++++++++---
kernel/sched/stats.h | 5 +-
14 files changed, 343 insertions(+), 181 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Ivo Totev, HRB 36809, AG Nürnberg
next reply other threads:[~2022-01-11 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 17:23 Borislav Petkov [this message]
2022-01-12 1:35 ` [GIT PULL] sched/core for v5.17 pr-tracker-bot
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=Yd289b35jcsSdJfl@zn.tnic \
--to=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/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