Linux Trace Kernel
 help / color / mirror / Atom feed
From: Vincent Donnefort <vdonnefort@google.com>
To: rostedt@goodmis.org, mhiramat@kernel.org,
	 linux-trace-kernel@vger.kernel.org
Cc: mathieu.desnoyers@efficios.com, kernel-team@android.com,
	 linux-kernel@vger.kernel.org,
	Vincent Donnefort <vdonnefort@google.com>
Subject: [PATCH v3 11/18] ring-buffer: Add ring_buffer_read_remote_meta_page()
Date: Tue, 21 Jul 2026 11:35:56 +0100	[thread overview]
Message-ID: <20260721103603.342266-12-vdonnefort@google.com> (raw)
In-Reply-To: <20260721103603.342266-1-vdonnefort@google.com>

In preparation for the introduction of a panic handler for trace
remotes, add a ring_buffer_read_remote_meta_page(). This is basically
similar to ring_buffer_poll_remote, but it doesn't try to wake-up
readers and, in the !RING_BUFFER_ALL_CPUS case, uses panic-friendly
locks.

While at it, update trace_remote_has_cpu() to use this new function
instead of ring_buffer_poll_remote(), avoiding unnecessary wakeups when
verifying if a CPU buffer is active.

Signed-off-by: Vincent Donnefort <vdonnefort@google.com>

diff --git a/include/linux/ring_buffer.h b/include/linux/ring_buffer.h
index 0670742b2d60..3c0de6593c81 100644
--- a/include/linux/ring_buffer.h
+++ b/include/linux/ring_buffer.h
@@ -299,6 +299,7 @@ struct ring_buffer_remote {
 	void				*priv;
 };
 
+int ring_buffer_read_remote_meta_page(struct trace_buffer *buffer, int cpu);
 int ring_buffer_poll_remote(struct trace_buffer *buffer, int cpu);
 
 struct trace_buffer *
diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
index 517bdb061083..c35e36c553aa 100644
--- a/kernel/trace/ring_buffer.c
+++ b/kernel/trace/ring_buffer.c
@@ -6805,6 +6805,47 @@ bool ring_buffer_empty_cpu(struct trace_buffer *buffer, int cpu)
 }
 EXPORT_SYMBOL_GPL(ring_buffer_empty_cpu);
 
+/**
+ * ring_buffer_read_remote_meta_page - read the meta page of a remote ring buffer
+ * @buffer: The ring buffer
+ * @cpu: The CPU buffer to read (or RING_BUFFER_ALL_CPUS)
+ *
+ * Returns:
+ *  0 on success, or -EINVAL if the CPU is not in the buffer's cpumask.
+ */
+int ring_buffer_read_remote_meta_page(struct trace_buffer *buffer, int cpu)
+{
+	struct ring_buffer_per_cpu *cpu_buffer;
+
+	if (cpu != RING_BUFFER_ALL_CPUS) {
+		unsigned long flags;
+		bool dolock;
+
+		if (!cpumask_test_cpu(cpu, buffer->cpumask))
+			return -EINVAL;
+
+		cpu_buffer = buffer->buffers[cpu];
+
+		local_irq_save(flags);
+		dolock = rb_reader_lock(cpu_buffer);
+		rb_read_remote_meta_page(cpu_buffer);
+		rb_reader_unlock(cpu_buffer, dolock);
+		local_irq_restore(flags);
+		return 0;
+	}
+
+	guard(cpus_read_lock)();
+
+	for_each_buffer_cpu(buffer, cpu) {
+		cpu_buffer = buffer->buffers[cpu];
+
+		guard(raw_spinlock_irqsave)(&cpu_buffer->reader_lock);
+		rb_read_remote_meta_page(cpu_buffer);
+	}
+
+	return 0;
+}
+
 int ring_buffer_poll_remote(struct trace_buffer *buffer, int cpu)
 {
 	struct ring_buffer_per_cpu *cpu_buffer;
diff --git a/kernel/trace/trace_remote.c b/kernel/trace/trace_remote.c
index c54e1c65d163..fcd2dd754f6e 100644
--- a/kernel/trace/trace_remote.c
+++ b/kernel/trace/trace_remote.c
@@ -350,7 +350,7 @@ static bool trace_remote_has_cpu(struct trace_remote *remote, int cpu)
 	if (cpu == RING_BUFFER_ALL_CPUS)
 		return true;
 
-	return ring_buffer_poll_remote(remote->trace_buffer, cpu) == 0;
+	return ring_buffer_read_remote_meta_page(remote->trace_buffer, cpu) == 0;
 }
 
 static void __free_ring_buffer_iter(struct trace_remote_iterator *iter, int cpu)
-- 
2.55.0.229.g6434b31f56-goog


  parent reply	other threads:[~2026-07-21 10:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 10:35 [PATCH v3 00/18] tracing/remotes: Add printk, dump_on_panic and boot parameters Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 01/18] tracing/remotes: Gate tracefs files opening on trace remote registration Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 02/18] tracing/remotes: Release tracefs,eventfs on registration failure Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 03/18] tracing/remotes: Use kstrtobool for boolean tracefs files Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 04/18] tracing/remotes: Use a single per-remote polling work Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 05/18] tracing/simple_ring_buffer: Add support for compressed length Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 06/18] tracing/remotes: Add dmesg tracefs file Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 07/18] tracing/remotes: selftests: Add a test for the " Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 08/18] tracing/remotes: selftests: Prefix hypervisor folder Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 09/18] ring-buffer: Use irqsave for the reader lock in ring_buffer_poll_remote Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 10/18] ring-buffer: Use panic-friendly locking in ring_buffer_iter interface Vincent Donnefort
2026-07-21 10:35 ` Vincent Donnefort [this message]
2026-07-21 10:35 ` [PATCH v3 12/18] ring-buffer: Add kerneldoc for ring_buffer_poll_remote Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 13/18] tracing/remotes: Add dump_on_panic tracefs file Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 14/18] tracing/remotes: selftests: Add a test for the " Vincent Donnefort
2026-07-21 10:36 ` [PATCH v3 15/18] tracing/remotes: Add poll_ms " Vincent Donnefort
2026-07-21 10:36 ` [PATCH v3 16/18] tracing/remotes: Add trace_remote cmdline options Vincent Donnefort
2026-07-21 10:36 ` [PATCH v3 17/18] Documentation: tracing/remotes: Add detailed tracefs layout Vincent Donnefort
2026-07-21 10:36 ` [PATCH v3 18/18] Documentation/kernel-parameters: Add trace_remote Vincent Donnefort

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=20260721103603.342266-12-vdonnefort@google.com \
    --to=vdonnefort@google.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.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