mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* [GIT PULL] Performance events updates for v7.3
@ 2026-08-17  9:30 Ingo Molnar
  2026-08-18 19:42 ` Linus Torvalds
  2026-08-18 22:00 ` pr-tracker-bot
  0 siblings, 2 replies; 4+ messages in thread
From: Ingo Molnar @ 2026-08-17  9:30 UTC (permalink / raw)
  To: Linus Torvalds
  Cc: linux-kernel, Peter Zijlstra, Arnaldo Carvalho de Melo,
	Jiri Olsa, Alexander Shishkin, Mark Rutland, Namhyung Kim,
	linux-perf-users, Sean Christopherson

Linus,

Please pull the latest perf/core Git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-core-2026-08-17

for you to fetch changes up to 917d558b151cad5b05991e5eaee22efab33525ca:

Performance events updates for v7.3:

uprobes updates:

 - Patch series to fix a category of bugs with optimized uprobes that
   can clobber the redzone area with call instruction storing return
   address on stack where user code may keep temporary data without
   adjusting RSP. Fix this by moving the optimized uprobes on top of
   10-bytes NOP instruction, so we can squeeze another instruction to
   escape the redzone area before doing the call.
   (Jiri Olsa, Andrii Nakryiko)

 - Switch uretprobes_srcu to SRCU-fast-updown, to improve performance
   (Puranjay Mohan)

Intel CPU PMU driver updates:

 - Optimize ACR handling in match_prev_assignment() (Dapeng Mi)
 - Patch series to fix various PMU driver bugs and data leaks (Dapeng Mi)
 - Fix Intel PT stop/start with no update (Adrian Hunter)

Intel uncore PMU driver updates:

 - Series to fix various uncore PMU setup robustness bugs (Zide Chen)

AMD uncore PMU driver updates:

 - Add group validation (Sandipan Das)

Misc fixes and updates by Dapeng Mi, Randy Dunlap and Zide Chen.

 Thanks,

	Ingo

------------------>
Adrian Hunter (3):
      perf/x86/intel/pt: Factor out pt_config_enable()
      perf/x86/intel/pt: Use bitwise access for PERF_HES_STOPPED
      perf/x86/intel/pt: Fix stop/start with no update

Andrii Nakryiko (1):
      selftests/bpf: Add tests for uprobe nop10 red zone clobbering

Dapeng Mi (15):
      perf/x86/intel: Remove anythread_deprecated bit from perf_capabilities
      perf/x86/intel: Keep cap_user_rdpmc in sync with RDPMC user-disable state
      perf/x86/intel: Fallback to sw branch type decoding if no hw decoding
      perf/x86/intel: Fix kernel address leakages in LBR stack
      perf/x86/intel: Validate the return value of intel_pmu_init_hybrid()
      perf/x86/intel: Drop fixed-counter PEBS constraints for baseline PEBS
      perf/core: Fix kernel register info leak via hardware skid
      perf/core: Check kernel access when kernel callchains are requested
      perf/x86: Unregister PMI handler on PMU init failure
      perf/x86: Free hybrid state on PMU init failure
      perf/x86: Guard intel_pmu_cpu_dead() against invalid hybrid PMU casts
      perf/x86/intel: Unwind cpuc state if PEBS buffer setup fails
      perf/x86: Remove stale fixed counter helper and fix hybrid PMU access
      perf/x86/intel: Fix intel_cap handling on hybrid PMUs
      perf/x86: Optimize ACR handling in match_prev_assignment()

Jiri Olsa (11):
      uprobes/x86: Remove struct uprobe_trampoline object
      uprobes/x86: Do not leak trampoline vma mapping on optimization failure
      uprobes/x86: Allow to copy uprobe trampolines on fork
      uprobes/x86: Move optimized uprobe from nop5 to nop10
      libbpf: Change has_nop_combo to work on top of nop10
      libbpf: Detect uprobe syscall with new error
      selftests/bpf: Emit nop,nop10 instructions combo for x86_64 arch
      selftests/bpf: Change uprobe syscall tests to use nop10
      selftests/bpf: Change uprobe/usdt trigger bench code to use nop10
      selftests/bpf: Add reattach tests for uprobe syscall
      selftests/bpf: Add tests for forked/cloned optimized uprobes

Puranjay Mohan (2):
      srcu: Add lock guard for srcu_fast_updown flavor
      uprobes: Switch uretprobes_srcu to SRCU-fast-updown

Randy Dunlap (1):
      perf/x86/intel/pt: Drop kernel-doc for deleted struct members

Sandipan Das (1):
      perf/x86/amd/uncore: Add group validation

Zide Chen (8):
      perf/x86/intel/uncore: Fix PCI PMU cleanup on setup failure
      perf/x86/intel/uncore: Fix refcnt and other cleanups
      perf/x86/intel/uncore: Let init_box() callback report failures
      perf/x86/intel/uncore: Keep PCI PMUs working when MMIO/MSR setup fails
      perf/x86/intel/uncore: Factor out box setup code
      perf/x86/intel/uncore: Introduce PMU flags and broken state
      perf/x86/intel/uncore: Fix uncore_box ref/unref ordering
      perf/x86/intel/uncore: Implement lazy setup for MSR/MMIO PMUs


 arch/x86/events/amd/uncore.c                       |  31 ++
 arch/x86/events/core.c                             |  48 ++-
 arch/x86/events/intel/core.c                       | 120 +++---
 arch/x86/events/intel/ds.c                         |  13 -
 arch/x86/events/intel/lbr.c                        |  14 +-
 arch/x86/events/intel/pt.c                         |  96 +++--
 arch/x86/events/intel/pt.h                         |   2 -
 arch/x86/events/intel/uncore.c                     | 225 ++++++------
 arch/x86/events/intel/uncore.h                     |  39 +-
 arch/x86/events/intel/uncore_discovery.c           |  21 +-
 arch/x86/events/intel/uncore_discovery.h           |   6 +-
 arch/x86/events/intel/uncore_nhmex.c               |   3 +-
 arch/x86/events/intel/uncore_snb.c                 |  82 +++--
 arch/x86/events/intel/uncore_snbep.c               |  77 ++--
 arch/x86/events/perf_event.h                       |  16 +-
 arch/x86/kernel/uprobes.c                          | 404 +++++++++++++--------
 include/linux/srcu.h                               |   7 +
 include/linux/uprobes.h                            |  10 +-
 kernel/events/core.c                               |  41 ++-
 kernel/events/uprobes.c                            |  39 +-
 kernel/fork.c                                      |   1 -
 tools/lib/bpf/features.c                           |   4 +-
 tools/lib/bpf/usdt.c                               |  16 +-
 tools/testing/selftests/bpf/bench.c                |  20 +-
 tools/testing/selftests/bpf/benchs/bench_trigger.c |  38 +-
 .../selftests/bpf/benchs/run_bench_uprobes.sh      |   2 +-
 .../selftests/bpf/prog_tests/uprobe_syscall.c      | 325 +++++++++++++++--
 tools/testing/selftests/bpf/prog_tests/usdt.c      |  74 +++-
 tools/testing/selftests/bpf/progs/test_usdt.c      |  25 ++
 tools/testing/selftests/bpf/usdt.h                 |   2 +-
 tools/testing/selftests/bpf/usdt_2.c               |  15 +-
 31 files changed, 1232 insertions(+), 584 deletions(-)


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [GIT PULL] Performance events updates for v7.3
  2026-08-17  9:30 [GIT PULL] Performance events updates for v7.3 Ingo Molnar
@ 2026-08-18 19:42 ` Linus Torvalds
  2026-08-23 10:22   ` Ingo Molnar
  2026-08-18 22:00 ` pr-tracker-bot
  1 sibling, 1 reply; 4+ messages in thread
From: Linus Torvalds @ 2026-08-18 19:42 UTC (permalink / raw)
  To: Ingo Molnar
  Cc: linux-kernel, Peter Zijlstra, Arnaldo Carvalho de Melo,
	Jiri Olsa, Alexander Shishkin, Mark Rutland, Namhyung Kim,
	linux-perf-users, Sean Christopherson

On Mon, 17 Aug 2026 at 02:30, Ingo Molnar <mingo@kernel.org> wrote:
>
>  - Patch series to fix a category of bugs [..]
...
>  - Series to fix various uncore [..]

In today's small pet peeve, you seem to have caught the same pointless
verbiage bug that I've been editing out of other peoples'
explanations: I really don't think it adds any value to talk about how
one issue was fixed by X patches, and another was fixed by a single
patch.

Just say "Fix a category of bugs ..." and "Fix various uncore ..". The
important thing is what got fixed, not that it was a "Five-patch
series fixing XYZ" like some people seem to think.

No, this isn't a big deal. I edit other peoples messages a lot more.
Some people seem to not understand imperative mood, and keep doing
that "Series fixing XYZ" thing.

The only reason I mention it is that I don't think I _used_ to do it
for your messages.

Or maybe it's just that I've been looking at too many of these, and I
went "Not Ingo too!"

Feel free to ignore my little impotent outburst.

              Linus

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [GIT PULL] Performance events updates for v7.3
  2026-08-17  9:30 [GIT PULL] Performance events updates for v7.3 Ingo Molnar
  2026-08-18 19:42 ` Linus Torvalds
@ 2026-08-18 22:00 ` pr-tracker-bot
  1 sibling, 0 replies; 4+ messages in thread
From: pr-tracker-bot @ 2026-08-18 22:00 UTC (permalink / raw)
  To: Ingo Molnar
  Cc: Linus Torvalds, linux-kernel, Peter Zijlstra,
	Arnaldo Carvalho de Melo, Jiri Olsa, Alexander Shishkin,
	Mark Rutland, Namhyung Kim, linux-perf-users,
	Sean Christopherson

The pull request you sent on Mon, 17 Aug 2026 11:30:49 +0200:

> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-core-2026-08-17

has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/8915457146a11d20a6c0786396376afda65eec40

Thank you!

-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [GIT PULL] Performance events updates for v7.3
  2026-08-18 19:42 ` Linus Torvalds
@ 2026-08-23 10:22   ` Ingo Molnar
  0 siblings, 0 replies; 4+ messages in thread
From: Ingo Molnar @ 2026-08-23 10:22 UTC (permalink / raw)
  To: Linus Torvalds
  Cc: linux-kernel, Peter Zijlstra, Arnaldo Carvalho de Melo,
	Jiri Olsa, Alexander Shishkin, Mark Rutland, Namhyung Kim,
	linux-perf-users, Sean Christopherson


* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Mon, 17 Aug 2026 at 02:30, Ingo Molnar <mingo@kernel.org> wrote:
> >
> >  - Patch series to fix a category of bugs [..]
> ...
> >  - Series to fix various uncore [..]
>
> In today's small pet peeve, you seem to have caught the same pointless
> verbiage bug that I've been editing out of other peoples'
> explanations: I really don't think it adds any value to talk about how
> one issue was fixed by X patches, and another was fixed by a single
> patch.
>
> Just say "Fix a category of bugs ..." and "Fix various uncore ..". The
> important thing is what got fixed, not that it was a "Five-patch
> series fixing XYZ" like some people seem to think.
>
> No, this isn't a big deal. I edit other peoples messages a lot more.
> Some people seem to not understand imperative mood, and keep doing
> that "Series fixing XYZ" thing.
>
> The only reason I mention it is that I don't think I _used_ to do it
> for your messages.

Yeah, so this was indeed a recent change of mine, I got the brilliant
idea to improve the pull request verbiage from the somewhat ambiguous
and perhaps a bit dismissive 'various' wording of larger changes to the
'series' phrasing, which intended to give the (significantly) higher
underlying effort a bit more credit while keeping the description
more compressed (and I tried to only apply it where it was justified,
so a simple cleanup series does not necessarily earn the same weight),
but looks like it's a regression and annoyance, so I reverted the
brain patch ;-)

I'll simply bring back more verbose summaries in those cases, or
use the 'various' verbiage.

Thanks,

	Ingo

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2026-08-23 10:23 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-08-17  9:30 [GIT PULL] Performance events updates for v7.3 Ingo Molnar
2026-08-18 19:42 ` Linus Torvalds
2026-08-23 10:22   ` Ingo Molnar
2026-08-18 22:00 ` pr-tracker-bot

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®