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/2] tracing: A couple of fixes for v6.8
Date: Tue, 13 Feb 2024 18:14:13 -0500	[thread overview]
Message-ID: <20240213231413.726507543@goodmis.org> (raw)


Two tracing fixes for v6.8:

- Fix the #ifndef that didn't have CONFIG_ on HAVE_DYNAMIC_FTRACE_WITH_REGS
  The fix to have dynamic trampolines work with x86 broke arm64 as
  the config used in the #ifdef was HAVE_DYNAMIC_FTRACE_WITH_REGS and not
  CONFIG_HAVE_DYNAMIC_FTRACE_WITH_REGS which removed the fix that the
  previous fix was to fix.

- Fix tracing_on state
  The code to test if "tracing_on" is set used ring_buffer_record_is_on()
  which returns false if the ring buffer isn't able to be written to.
  But the ring buffer disable has several bits that disable it.
  One is internal disabling which is used for resizing and other
  modifications of the ring buffer. But the "tracing_on" user space
  visibile flag should only report if tracing is actually on and not
  internally disabled, as this can cause confusion as writing "1"
  when it is disabled will not enable it.

  Instead use ring_buffer_record_is_set_on() which shows the user space
  visible settings.

  git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/urgent

Head SHA1: a6eaa24f1cc2c7aecec6047556bdfe32042094c3


Petr Pavlu (1):
      tracing: Fix HAVE_DYNAMIC_FTRACE_WITH_REGS ifdef

Sven Schnelle (1):
      tracing: Use ring_buffer_record_is_set_on() in tracer_tracing_is_on()

----
 kernel/trace/ftrace.c | 2 +-
 kernel/trace/trace.c  | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

             reply	other threads:[~2024-02-13 23:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 23:14 Steven Rostedt [this message]
2024-02-13 23:14 ` [for-linus][PATCH 1/2] tracing: Fix HAVE_DYNAMIC_FTRACE_WITH_REGS ifdef Steven Rostedt
2024-02-13 23:14 ` [for-linus][PATCH 2/2] tracing: Use ring_buffer_record_is_set_on() in tracer_tracing_is_on() 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=20240213231413.726507543@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