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] perf/urgent for v5.17-rc2
Date: Sun, 30 Jan 2022 12:15:52 +0100 [thread overview]
Message-ID: <YfZzaI5/7OCaFBoh@zn.tnic> (raw)
Hi Linus,
please pull two urgent perf fixes for v5.17.
Thx.
---
The following changes since commit 8c16dc047b5dd8f7b3bf4584fa75733ea0dde7dc:
x86/perf: Avoid warning for Arch LBR without XSAVE (2022-01-18 12:09:49 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/perf_urgent_for_v5.17_rc2_p2
for you to fetch changes up to c5de60cd622a2607c043ba65e25a6e9998a369f9:
perf/core: Fix cgroup event list management (2022-01-26 15:06:06 +0100)
----------------------------------------------------------------
- Prevent accesses to the per-CPU cgroup context list from another CPU
except the one it belongs to, to avoid list corruption
- Make sure parent events are always woken up to avoid indefinite hangs
in the traced workload
----------------------------------------------------------------
James Clark (1):
perf: Always wake the parent event
Namhyung Kim (1):
perf/core: Fix cgroup event list management
kernel/events/core.c | 23 +++++++++++++++++++----
1 file changed, 19 insertions(+), 4 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Ivo Totev, HRB 36809, AG Nürnberg
next reply other threads:[~2022-01-30 11:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 11:15 Borislav Petkov [this message]
2022-01-30 13:30 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2022-01-23 10:44 Borislav Petkov
2022-01-23 15:47 ` 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=YfZzaI5/7OCaFBoh@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®