public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [for-linus][PATCH 0/4] tracing: Fixes for v6.9
Date: Fri, 12 Apr 2024 09:31:52 -0400	[thread overview]
Message-ID: <20240412133152.723632549@goodmis.org> (raw)

Tracing fixes for 6.9:

- Fix the buffer_percent accounting as it is dependent on three variables:
  1) pages_read - number of subbuffers read
  2) pages_lost - number of subbuffers lost due to overwrite
  3) pages_touched - number of pages that a writer entered
  These three counters only increment, and to know how many active pages
  there are on the buffer at any given time, the pages_read and
  pages_lost are subtracted from pages_touched. But the pages touched
  was incremented whenever any writer went to the next subbuffer even
  if it wasn't the only one, so it was incremented more than it should
  be causing the counter for how many subbuffers currently have content
  incorrect, which caused the buffer_percent that holds waiters until
  the ring buffer is filled to a given percentage to wake up early.

- Fix warning of unused functions when PERF_EVENTS is not configured in

- Replace bad tab with space in Kconfig for FTRACE_RECORD_RECURSION_SIZE

- Fix to some kerneldoc function comments in eventfs code.

Arnd Bergmann (1):
      tracing: hide unused ftrace_event_id_fops

Prasad Pandit (1):
      tracing: Fix FTRACE_RECORD_RECURSION_SIZE Kconfig entry

Steven Rostedt (Google) (1):
      ring-buffer: Only update pages_touched when a new page is touched

Yang Li (1):
      eventfs: Fix kernel-doc comments to functions

----
 fs/tracefs/event_inode.c    | 14 ++++++++++----
 kernel/trace/Kconfig        |  2 +-
 kernel/trace/ring_buffer.c  |  6 +++---
 kernel/trace/trace_events.c |  4 ++++
 4 files changed, 18 insertions(+), 8 deletions(-)

             reply	other threads:[~2024-04-12 13:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12 13:31 Steven Rostedt [this message]
2024-04-12 13:31 ` [for-linus][PATCH 1/4] eventfs: Fix kernel-doc comments to functions Steven Rostedt
2024-04-12 13:31 ` [for-linus][PATCH 2/4] tracing: Fix FTRACE_RECORD_RECURSION_SIZE Kconfig entry Steven Rostedt
2024-04-12 13:31 ` [for-linus][PATCH 3/4] tracing: hide unused ftrace_event_id_fops Steven Rostedt
2024-04-12 13:31 ` [for-linus][PATCH 4/4] ring-buffer: Only update pages_touched when a new page is touched Steven Rostedt

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=20240412133152.723632549@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@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