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/urgent for v5.16-rc4
Date: Sun, 5 Dec 2021 12:42:42 +0100 [thread overview]
Message-ID: <YaylsgmYwXBK6qXf@zn.tnic> (raw)
Hi Linus,
please pull a couple of urgent scheduler fixes for 5.16.
Thx.
---
The following changes since commit d58071a8a76d779eedab38033ae4c821c30295a5:
Linux 5.16-rc3 (2021-11-28 14:09:19 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/sched_urgent_for_v5.16_rc4
for you to fetch changes up to 315c4f884800c45cb6bd8c90422fad554a8b9588:
sched/uclamp: Fix rq->uclamp_max not set on first enqueue (2021-12-04 10:56:18 +0100)
----------------------------------------------------------------
- Properly init uclamp_flags of a runqueue, on first enqueuing
- Fix preempt= callback return values
- Correct utime/stime resource usage reporting on nohz_full to return
the proper times instead of shorter ones
----------------------------------------------------------------
Andrew Halaney (1):
preempt/dynamic: Fix setup_preempt_mode() return value
Frederic Weisbecker (1):
sched/cputime: Fix getrusage(RUSAGE_THREAD) with nohz_full
Qais Yousef (1):
sched/uclamp: Fix rq->uclamp_max not set on first enqueue
include/linux/sched/cputime.h | 5 +++--
kernel/sched/core.c | 6 +++---
kernel/sched/cputime.c | 12 +++++++++---
3 files changed, 15 insertions(+), 8 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Ivo Totev, HRB 36809, AG Nürnberg
next reply other threads:[~2021-12-05 11:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 11:42 Borislav Petkov [this message]
2021-12-05 17:02 ` 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=YaylsgmYwXBK6qXf@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
all inboxes | Powered by JetHome®