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.14
Date: Sun, 29 Aug 2021 13:21:22 +0200 [thread overview]
Message-ID: <YSttskpCbUeAiwTj@zn.tnic> (raw)
Hi Linus,
I believe this should be the last pull request from the tip gang for
5.14 and we should be pretty much ready so please pull two final urgent
scheduler fixes for v5.14.
Thx.
---
The following changes since commit 7c60610d476766e128cc4284bb6349732cbd6606:
Linux 5.14-rc6 (2021-08-15 13:40:53 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/sched_urgent_for_v5.14
for you to fetch changes up to e681dcbaa4b284454fecd09617f8b24231448446:
sched: Fix get_push_task() vs migrate_disable() (2021-08-26 19:02:00 +0200)
----------------------------------------------------------------
- Have get_push_task() check whether current has migration disabled and
thus avoid useless invocations of the migration thread
- Rework initialization flow so that all rq->core's are initialized,
even of CPUs which have not been onlined yet, so that iterating over
them all works as expected
----------------------------------------------------------------
Peter Zijlstra (1):
sched: Fix Core-wide rq->lock for uninitialized CPUs
Sebastian Andrzej Siewior (1):
sched: Fix get_push_task() vs migrate_disable()
kernel/sched/core.c | 143 +++++++++++++++++++++++++++++++++++++++++----------
kernel/sched/sched.h | 5 +-
2 files changed, 121 insertions(+), 27 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
next reply other threads:[~2021-08-29 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 11:21 Borislav Petkov [this message]
2021-08-29 19:47 ` [GIT PULL] sched/urgent for v5.14 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=YSttskpCbUeAiwTj@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