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 6.1
Date: Sun, 23 Oct 2022 12:15:37 +0200 [thread overview]
Message-ID: <Y1UUSef0KUKy2RUE@zn.tnic> (raw)
Hi Linus,
by popular demand, here are a couple of urgent perf fixes for 6.1.
Please pull,
thx.
---
The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:
Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/perf_urgent_for_v6.1_rc2
for you to fetch changes up to 21da7472a040420f2dc624ffec70291a72c5d6a6:
bpf: Fix sample_flags for bpf_perf_event_output (2022-10-17 16:32:06 +0200)
----------------------------------------------------------------
- Fix raw data handling when perf events are used in bpf
- Rework how SIGTRAPs get delivered to events to address a bunch of
problems with it. Add a selftest for that too
----------------------------------------------------------------
Marco Elver (1):
selftests/perf_events: Add a SIGTRAP stress test with disables
Peter Zijlstra (1):
perf: Fix missing SIGTRAPs
Sumanth Korikkar (1):
bpf: Fix sample_flags for bpf_perf_event_output
include/linux/perf_event.h | 19 ++-
kernel/events/core.c | 151 +++++++++++++++------
kernel/events/ring_buffer.c | 2 +-
kernel/trace/bpf_trace.c | 2 +
.../selftests/perf_events/sigtrap_threads.c | 35 ++++-
5 files changed, 163 insertions(+), 46 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman
(HRB 36809, AG Nürnberg)
next reply other threads:[~2022-10-23 10:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 10:15 Borislav Petkov [this message]
2022-10-23 17:18 ` [GIT PULL] perf/urgent for 6.1 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=Y1UUSef0KUKy2RUE@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