From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Mark Rutland <mark.rutland@arm.com>,
Namhyung Kim <namhyung@kernel.org>
Subject: [GIT PULL] perf events fixes
Date: Sun, 8 Nov 2026 10:09:15 +0100 [thread overview]
Message-ID: <avA8O8tiG0pLpMKn@gmail.com> (raw)
Linus,
Please pull the latest perf/urgent Git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-urgent-2026-11-08
for you to fetch changes up to 6f083fbccd5f06889bc08e1182bd02c0383b9121:
Perf events fixes:
- Fix sideband event output when only requesting attr.defer_output
(Ian Rogers)
- Clamp deferred callchain entry count to fit u16 header.size
(Ian Rogers)
- Various AMD IBS fixes (Ravi Bangoria):
- Reset CPU0 IBS state on syscore resume
- Fix kernel address leak via REGS_USER and REGS_INTR
- Simplify/fix event state handling with IBS_CAPS_DIS
- Revert AUX page allocation order default to be continuous (Leo Yan)
- Don't send SIGTRAP after exec removed the event (Danish Khateeb)
Thanks,
Ingo
------------------>
Danish Khateeb (1):
perf/core: Don't send SIGTRAP after exec removed the event
Ian Rogers (2):
perf/core: Include perf_event_attr::defer_output in is_sb_event() check
perf/core: Clamp deferred callchain entry count to fit u16 header.size
Leo Yan (1):
Revert "perf/aux: Allocate non-contiguous AUX pages by default"
Ravi Bangoria (3):
perf/amd/ibs: Reset CPU0 IBS state on syscore resume
perf/amd/ibs: Fix kernel address leak via REGS_USER and REGS_INTR
perf/amd/ibs: Simplify event state handling with IBS_CAPS_DIS
arch/x86/events/amd/ibs.c | 197 ++++++++++++++++++++++++++++++++++++++------
arch/x86/events/intel/pt.c | 2 -
include/linux/perf_event.h | 11 ++-
kernel/events/core.c | 37 ++++++---
kernel/events/ring_buffer.c | 29 ++-----
5 files changed, 216 insertions(+), 60 deletions(-)
next reply other threads:[~2026-11-08 9:09 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 9:09 Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-10-25 11:11 Ingo Molnar
2026-10-26 3:59 ` pr-tracker-bot
2026-10-18 9:20 Ingo Molnar
2026-10-18 18:15 ` pr-tracker-bot
2026-10-04 7:38 Ingo Molnar
2026-10-04 16:04 ` pr-tracker-bot
2026-09-27 7:59 Ingo Molnar
2026-09-27 19:48 ` pr-tracker-bot
2026-09-20 9:42 Ingo Molnar
2026-09-20 17:21 ` pr-tracker-bot
2026-09-13 8:12 Ingo Molnar
2026-09-13 17:37 ` pr-tracker-bot
2026-09-06 11:13 Ingo Molnar
2026-09-06 18:11 ` pr-tracker-bot
2026-07-11 11:38 Ingo Molnar
2026-07-11 17:14 ` pr-tracker-bot
2026-07-05 7:37 Ingo Molnar
2026-07-05 15:46 ` pr-tracker-bot
2026-05-09 1:40 Ingo Molnar
2026-05-09 3:32 ` pr-tracker-bot
2026-04-12 7:17 Ingo Molnar
2026-04-12 17:45 ` pr-tracker-bot
2026-03-22 8:24 Ingo Molnar
2026-03-22 18:04 ` pr-tracker-bot
2026-03-01 9:00 Ingo Molnar
2026-03-01 21:37 ` pr-tracker-bot
2026-01-24 9:28 Ingo Molnar
2026-01-24 18:00 ` pr-tracker-bot
2025-12-12 9:36 Ingo Molnar
2025-12-13 18:12 ` pr-tracker-bot
2025-11-23 7:45 Ingo Molnar
2025-11-23 16:26 ` pr-tracker-bot
2025-11-01 7:13 Ingo Molnar
2025-11-01 17:41 ` pr-tracker-bot
2025-05-04 7:17 Ingo Molnar
2025-05-04 15:23 ` pr-tracker-bot
2025-04-26 8:35 Ingo Molnar
2025-04-26 17:06 ` pr-tracker-bot
2025-04-18 20:32 Ingo Molnar
2025-04-18 21:15 ` pr-tracker-bot
2025-04-10 21:10 Ingo Molnar
2025-04-10 22:52 ` pr-tracker-bot
2025-03-21 10:39 Ingo Molnar
2025-03-21 17:39 ` pr-tracker-bot
2025-03-07 12:22 Ingo Molnar
2025-03-07 21:04 ` pr-tracker-bot
2025-02-28 19:17 Ingo Molnar
2025-03-01 1:41 ` pr-tracker-bot
2024-06-02 7:08 Ingo Molnar
2024-06-02 16:41 ` pr-tracker-bot
2024-03-17 8:57 Ingo Molnar
2024-03-17 19:34 ` pr-tracker-bot
2023-10-01 8:35 Ingo Molnar
2023-10-01 17:08 ` pr-tracker-bot
2010-09-08 13:00 Ingo Molnar
2010-01-16 16:59 Ingo Molnar
2009-11-10 17:45 Ingo Molnar
2009-11-01 15:36 Ingo Molnar
2009-10-23 14:49 Ingo Molnar
2009-10-13 18:25 Ingo Molnar
2009-10-08 18:37 Ingo Molnar
2009-10-02 12:42 Ingo Molnar
2009-09-26 12:29 Ingo Molnar
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=avA8O8tiG0pLpMKn@gmail.com \
--to=mingo@kernel.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.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®