mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrii Nakryiko <andrii@kernel.org>,
	Gaosheng Cui <cuigaosheng1@huawei.com>,
	Masami Hiramatsu (Google) <mhiramat@kernel.org>,
	linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>
Subject: [GIT PULL] probes: Updates for v6.12
Date: Wed, 25 Sep 2024 23:31:56 +0900	[thread overview]
Message-ID: <20240925233156.20824ba2b21ff5d9a22c2baa@kernel.org> (raw)

Hi Linus,

Probes updates for v6.12:

- uprobes: make trace_uprobe->nhit counter a per-CPU one
   This makes uprobe event's hit counter per-CPU for improving
   scalability on multi-core environment.

- kprobes: Remove obsoleted declaration for init_test_probes
   Remove unused init_test_probes() from header.

- Raw tracepoint probe supports raw tracepoint events on modules.
   The tracepoint events using fprobe were introduced in v6.5, but
   tracepoints can be compiled in modules. This supports such a case.
   This includes the following improvements.
  . tracepoint: add a function for iterating over all tracepoints in
    all modules.
  . tracepoint: Add a function for iterating over tracepoints in a
    module.
  . tracing/fprobe: Support raw tracepoint events on modules.
  . tracing/fprobe: Support raw tracepoints on future loaded modules.
     This allows user to add tracepoint events on modules which is
     not loaded yet.
  . selftests/tracing: Add a test for tracepoint events on modules.


Please pull the latest probes-v6.12 tree, which can be found at:


  git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
probes-v6.12

Tag SHA1: 66af4af443ef76c214c5751c162ea058ae05bd1f
Head SHA1: 4e78dd6b4c27c5a6d057f179ff6c1ddd75a7a2ab


Andrii Nakryiko (1):
      uprobes: turn trace_uprobe's nhit counter to be per-CPU one

Gaosheng Cui (1):
      kprobes: Remove obsoleted declaration for init_test_probes

Masami Hiramatsu (Google) (5):
      tracepoint: Support iterating over tracepoints on modules
      tracepoint: Support iterating tracepoints in a loading module
      tracing/fprobe: Support raw tracepoint events on modules
      tracing/fprobe: Support raw tracepoints on future loaded modules
      sefltests/tracing: Add a test for tracepoint events on modules

----
 include/linux/kprobes.h                            |   9 --
 include/linux/tracepoint.h                         |  20 +++
 kernel/trace/trace_fprobe.c                        | 179 +++++++++++++++------
 kernel/trace/trace_uprobe.c                        |  24 ++-
 kernel/tracepoint.c                                |  42 +++++
 tools/testing/selftests/ftrace/config              |   1 +
 .../test.d/dynevent/add_remove_tprobe_module.tc    |  61 +++++++
 .../ftrace/test.d/dynevent/tprobe_syntax_errors.tc |   1 -
 8 files changed, 275 insertions(+), 62 deletions(-)
 create mode 100644 tools/testing/selftests/ftrace/test.d/dynevent/add_remove_tprobe_module.tc


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

             reply	other threads:[~2024-09-25 14:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-25 14:31 Masami Hiramatsu [this message]
2024-09-26 16:38 ` 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=20240925233156.20824ba2b21ff5d9a22c2baa@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=andrii@kernel.org \
    --cc=cuigaosheng1@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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®