mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Ajay Kaher <akaher@vmware.com>,
	Eric Vaughn <ervaughn@linux.microsoft.com>,
	Sishuai Gong <sishuai.system@gmail.com>,
	Uros Bizjak <ubizjak@gmail.com>,
	Valentin Schneider <vschneid@redhat.com>,
	Yue Haibing <yuehaibing@huawei.com>,
	Zhang Zekun <zhangzekun11@huawei.com>,
	Zheng Yejian <zhengyejian1@huawei.com>
Subject: [GIT PULL] tracing: Updates for 6.6
Date: Thu, 31 Aug 2023 11:56:35 -0400	[thread overview]
Message-ID: <20230831115635.1bdea0d7@rorschach.local.home> (raw)


Linus,

[ Note, there's a minor conflict which should be fixed by:
        mutex_lock(&trace_types_lock);
-       if (unlikely(tr->current_trace && iter->trace->name != tr->current_trace->name)) {
+       if (unlikely(tr->current_trace != iter->trace))
 +              /* Close iter->trace before switching to the new current tracer */
 +              if (iter->trace->close)
 +                      iter->trace->close(iter);
-               *iter->trace = *tr->current_trace;
+               iter->trace = tr->current_trace;
 +              /* Reopen the new current tracer */
 +              if (iter->trace->open)
 +                      iter->trace->open(iter);
 +      }
        mutex_unlock(&trace_types_lock);
]

Tracing updates for 6.6:

 User visible changes:

  - Added a way to easier filter with cpumasks:
     # echo 'cpumask & CPUS{17-42}' > /sys/kernel/tracing/events/ipi_send_cpumask/filter

  - Show actual size of ring buffer after modifying the ring buffer size via
    buffer_size_kb. Currently it just returns what was written, but the actual
    size rounds up to the sub buffer size. Show that real size instead.

 Major changes:

  - Added "eventfs". This is the code that handles the inodes and dentries of
    tracefs/events directory. As there are thousands of events, and each event
    has several inodes and dentries that currently exist even when tracing is
    never used, they take up precious memory. Instead, eventfs will allocate
    the inodes and dentries in a JIT way (similar to what procfs does). There
    is now metadata that handles the events and subdirectories, and will create
    the inodes and dentries when they are used.

    Note, I also have patches that remove the subdirectory meta data, but will
    wait till the next merge window before applying them. It's a little more
    complex, and I want to make sure the dynamic code works properly before
    adding more complexity, making it easier to revert if need be.

 Minor changes:

  - Optimization to user event list traversal.

  - Remove intermediate permission of tracefs files (note the intermediate
    permission removes all access to the files so it is not a security concern,
    but just a clean up.)

  - Add the complex fix to FORTIFY_SOURCE to the kernel stack event logic.

  - Other minor clean ups.


Please pull the latest trace-v6.6 tree, which can be found at:


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

Tag SHA1: 1065c0c85cfdb141b5cc2064b6e379fd564f0779
Head SHA1: 8c96b70171584f38940eb2ba65b84eee38b549ba


Ajay Kaher (9):
      eventfs: Implement tracefs_inode_cache
      tracefs: Rename and export some tracefs functions
      eventfs: Implement eventfs dir creation functions
      eventfs: Implement eventfs file add functions
      eventfs: Implement eventfs lookup, read, open functions
      eventfs: Implement functions to create files and dirs when accessed
      eventfs: Implement removal of meta data from eventfs
      eventfs: Move tracing/events to eventfs
      test: ftrace: Fix kprobe test for eventfs

Eric Vaughn (1):
      tracing/user_events: Optimize safe list traversals

Sishuai Gong (1):
      tracefs: Avoid changing i_mode to a temp value

Steven Rostedt (Google) (5):
      tracing: Add back FORTIFY_SOURCE logic to kernel_stack event structure
      tracing: Remove unnecessary copying of tr->current_trace
      tracing: Add free_trace_iter_content() helper function
      tracing: Require all trace events to have a TRACE_SYSTEM
      tracefs: Remove kerneldoc from struct eventfs_file

Uros Bizjak (1):
      ring_buffer: Use try_cmpxchg instead of cmpxchg

Valentin Schneider (9):
      tracing/filters: Dynamically allocate filter_pred.regex
      tracing/filters: Enable filtering a cpumask field by another cpumask
      tracing/filters: Enable filtering a scalar field by a cpumask
      tracing/filters: Enable filtering the CPU common field by a cpumask
      tracing/filters: Optimise cpumask vs cpumask filtering when user mask is a single CPU
      tracing/filters: Optimise scalar vs cpumask filtering when the user mask is a single CPU
      tracing/filters: Optimise CPU vs cpumask filtering when the user mask is a single CPU
      tracing/filters: Further optimise scalar vs cpumask comparison
      tracing/filters: Document cpumask filtering

Yue Haibing (1):
      tracing: Remove unused function declarations

Zhang Zekun (1):
      ftrace: Remove empty declaration ftrace_enable_daemon() and ftrace_disable_daemon()

Zheng Yejian (1):
      tracing: Set actual size after ring buffer resize

----
 Documentation/trace/events.rst                     |  14 +
 fs/tracefs/Makefile                                |   1 +
 fs/tracefs/event_inode.c                           | 807 +++++++++++++++++++++
 fs/tracefs/inode.c                                 | 157 +++-
 fs/tracefs/internal.h                              |  29 +
 include/linux/ftrace.h                             |   5 -
 include/linux/trace_events.h                       |   2 +
 include/linux/tracefs.h                            |  23 +
 kernel/trace/ring_buffer.c                         |  20 +-
 kernel/trace/trace.c                               |  99 +--
 kernel/trace/trace.h                               |  14 +-
 kernel/trace/trace_entries.h                       |   2 +-
 kernel/trace/trace_events.c                        |  76 +-
 kernel/trace/trace_events_filter.c                 | 302 +++++++-
 kernel/trace/trace_events_user.c                   |  15 +-
 kernel/trace/trace_export.c                        |   9 +
 .../ftrace/test.d/kprobe/kprobe_args_char.tc       |   9 +-
 .../ftrace/test.d/kprobe/kprobe_args_string.tc     |   9 +-
 18 files changed, 1424 insertions(+), 169 deletions(-)
 create mode 100644 fs/tracefs/event_inode.c
 create mode 100644 fs/tracefs/internal.h
---------------------------

             reply	other threads:[~2023-08-31 15:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31 15:56 Steven Rostedt [this message]
2023-09-01  9:20 ` Valentin Schneider
2023-09-01 11:44   ` Steven Rostedt
2023-09-01 12:19     ` Valentin Schneider
2023-09-01 23:41 ` 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=20230831115635.1bdea0d7@rorschach.local.home \
    --to=rostedt@goodmis.org \
    --cc=akaher@vmware.com \
    --cc=ervaughn@linux.microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mhiramat@kernel.org \
    --cc=sishuai.system@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=ubizjak@gmail.com \
    --cc=vschneid@redhat.com \
    --cc=yuehaibing@huawei.com \
    --cc=zhangzekun11@huawei.com \
    --cc=zhengyejian1@huawei.com \
    /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®