From: Vincent Donnefort <vdonnefort@google.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
linux-trace-kernel@vger.kernel.org, maz@kernel.org,
oliver.upton@linux.dev, joey.gouly@arm.com,
suzuki.poulose@arm.com, yuzenghui@huawei.com,
kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
jstultz@google.com, qperret@google.com, will@kernel.org,
aneesh.kumar@kernel.org, kernel-team@android.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v10 14/30] tracing: Add a trace remote module for testing
Date: Sat, 31 Jan 2026 12:54:17 +0000 [thread overview]
Message-ID: <aX37eRjYBP4WmyS6@google.com> (raw)
In-Reply-To: <20260129113452.190d4d79@gandalf.local.home>
On Thu, Jan 29, 2026 at 11:34:52AM -0500, Steven Rostedt wrote:
> On Mon, 26 Jan 2026 10:44:03 +0000
> Vincent Donnefort <vdonnefort@google.com> wrote:
>
> > diff --git a/kernel/trace/remote_test.c b/kernel/trace/remote_test.c
> > new file mode 100644
> > index 000000000000..059127489c99
> > --- /dev/null
> > +++ b/kernel/trace/remote_test.c
> > @@ -0,0 +1,259 @@
> > +// SPDX-License-Identifier: GPL-2.0
> > +/*
> > + * Copyright (C) 2025 - Google LLC
> > + * Author: Vincent Donnefort <vdonnefort@google.com>
> > + */
> > +
> > +#include <linux/module.h>
> > +#include <linux/simple_ring_buffer.h>
> > +#include <linux/trace_remote.h>
> > +#include <linux/tracefs.h>
> > +#include <linux/types.h>
> > +
> > +#define REMOTE_EVENT_INCLUDE_FILE kernel/trace/remote_test_events.h
> > +#include <trace/define_remote_events.h>
> > +
> > +static DEFINE_PER_CPU(struct simple_rb_per_cpu *, simple_rbs);
> > +static struct trace_buffer_desc *remote_test_buffer_desc;
> > +
> > +/*
> > + * The trace_remote lock already serializes accesses from the trace_remote_callbacks.
> > + * However write_event can still race with load/unload.
> > + */
> > +static DEFINE_MUTEX(simple_rbs_lock);
> > +
> > +static int remote_test_load_simple_rb(int cpu, struct ring_buffer_desc *rb_desc)
> > +{
> > + struct simple_rb_per_cpu *cpu_buffer;
> > + struct simple_buffer_page *bpages;
> > + int ret = -ENOMEM;
> > +
> > + cpu_buffer = kmalloc(sizeof(*cpu_buffer), GFP_KERNEL);
> > + if (!cpu_buffer)
> > + return ret;
> > +
> > + bpages = kmalloc_array(rb_desc->nr_page_va, sizeof(*bpages), GFP_KERNEL);
> > + if (!bpages)
> > + goto err_free_cpu_buffer;
> > +
> > + ret = simple_ring_buffer_init(cpu_buffer, bpages, rb_desc);
> > + if (ret)
> > + goto err_free_bpages;
> > +
> > + scoped_guard(mutex, &simple_rbs_lock)
> > + *per_cpu_ptr(&simple_rbs, cpu) = cpu_buffer;
>
> Should there be some kind of check before blindly assigning the cpu_buffer?
> If not, what is the mutex protecting from?
This intends to order accesses with write_event_write(). trace_remote ensures
that load/unload are always balanced, so I don't believe there's anything to
test.
I could add a WARN_ON though. and probably guard(mutex)(&simple_rbs_lock) is
enough.
>
>
> > +
> > + return 0;
> > +
> > +err_free_bpages:
> > + kfree(bpages);
> > +
> > +err_free_cpu_buffer:
> > + kfree(cpu_buffer);
> > +
> > + return ret;
> > +}
> > +
> > +static void remote_test_unload_simple_rb(int cpu)
> > +{
> > + struct simple_rb_per_cpu *cpu_buffer = *per_cpu_ptr(&simple_rbs, cpu);
> > + struct simple_buffer_page *bpages;
> > +
> > + if (!cpu_buffer)
> > + return;
> > +
> > + guard(mutex)(&simple_rbs_lock);
> > +
> > + bpages = cpu_buffer->bpages;
> > + simple_ring_buffer_unload(cpu_buffer);
> > + kfree(bpages);
> > + kfree(cpu_buffer);
> > + *per_cpu_ptr(&simple_rbs, cpu) = NULL;
> > +}
> > +
> > +static struct trace_buffer_desc *remote_test_load(unsigned long size, void *unused)
> > +{
> > + struct ring_buffer_desc *rb_desc;
> > + struct trace_buffer_desc *desc;
> > + size_t desc_size;
> > + int cpu, ret;
> > +
> > + if (WARN_ON(remote_test_buffer_desc))
> > + return ERR_PTR(-EINVAL);
> > +
> > + desc_size = trace_buffer_desc_size(size, num_possible_cpus());
> > + if (desc_size == SIZE_MAX) {
> > + ret = -E2BIG;
> > + goto err_unlock_cpus;
> > + }
> > +
> > + desc = kmalloc(desc_size, GFP_KERNEL);
> > + if (!desc) {
> > + ret = -ENOMEM;
> > + goto err_unlock_cpus;
> > + }
> > +
> > + ret = trace_remote_alloc_buffer(desc, desc_size, size, cpu_possible_mask);
> > + if (ret)
> > + goto err_free_desc;
> > +
> > + for_each_ring_buffer_desc(rb_desc, cpu, desc) {
> > + ret = remote_test_load_simple_rb(rb_desc->cpu, rb_desc);
> > + if (ret)
> > + goto err;
> > + }
> > +
> > + remote_test_buffer_desc = desc;
> > +
> > + return remote_test_buffer_desc;
> > +
> > +err:
> > + for_each_ring_buffer_desc(rb_desc, cpu, remote_test_buffer_desc)
> > + remote_test_unload_simple_rb(rb_desc->cpu);
> > + trace_remote_free_buffer(remote_test_buffer_desc);
> > +
> > +err_free_desc:
> > + kfree(desc);
> > +
> > +err_unlock_cpus:
>
> Where was the cpus_read lock taken?
>
> > + cpus_read_unlock();
> > +
> > + return ERR_PTR(ret);
> > +}
> > +
> > +static void remote_test_unload(struct trace_buffer_desc *desc, void *unused)
> > +{
> > + struct ring_buffer_desc *rb_desc;
> > + int cpu;
> > +
> > + if (WARN_ON(desc != remote_test_buffer_desc))
> > + return;
> > +
> > + for_each_ring_buffer_desc(rb_desc, cpu, desc)
> > + remote_test_unload_simple_rb(rb_desc->cpu);
> > +
> > + remote_test_buffer_desc = NULL;
> > + trace_remote_free_buffer(desc);
> > + kfree(desc);
> > +}
> > +
> > +static int remote_test_enable_tracing(bool enable, void *unused)
> > +{
> > + struct ring_buffer_desc *rb_desc;
> > + int cpu;
> > +
> > + if (!remote_test_buffer_desc)
> > + return -ENODEV;
> > +
> > + for_each_ring_buffer_desc(rb_desc, cpu, remote_test_buffer_desc)
> > + WARN_ON(simple_ring_buffer_enable_tracing(*per_cpu_ptr(&simple_rbs, rb_desc->cpu),
> > + enable));
> > + return 0;
> > +}
> > +
> > +static int remote_test_swap_reader_page(unsigned int cpu, void *unused)
> > +{
> > + struct simple_rb_per_cpu *cpu_buffer;
> > +
> > + if (cpu >= NR_CPUS)
> > + return -EINVAL;
> > +
> > + cpu_buffer = *per_cpu_ptr(&simple_rbs, cpu);
> > + if (!cpu_buffer)
> > + return -EINVAL;
> > +
> > + return simple_ring_buffer_swap_reader_page(cpu_buffer);
> > +}
> > +
> > +static int remote_test_reset(unsigned int cpu, void *unused)
> > +{
> > + struct simple_rb_per_cpu *cpu_buffer;
> > +
> > + if (cpu >= NR_CPUS)
> > + return -EINVAL;
> > +
> > + cpu_buffer = *per_cpu_ptr(&simple_rbs, cpu);
> > + if (!cpu_buffer)
> > + return -EINVAL;
> > +
> > + return simple_ring_buffer_reset(cpu_buffer);
> > +}
> > +
> > +static int remote_test_enable_event(unsigned short id, bool enable, void *unused)
> > +{
> > + if (id != REMOTE_TEST_EVENT_ID)
> > + return -EINVAL;
> > +
> > + /*
> > + * Let's just use the struct remote_event enabled field that is turned on and off by
> > + * trace_remote. This is a bit racy but good enough for a simple test module.
> > + */
> > + return 0;
> > +}
> > +
> > +static ssize_t
> > +write_event_write(struct file *filp, const char __user *ubuf, size_t cnt, loff_t *pos)
> > +{
> > + struct remote_event_format_selftest *evt_test;
> > + struct simple_rb_per_cpu *cpu_buffer;
> > + unsigned long val;
> > + int ret;
> > +
> > + ret = kstrtoul_from_user(ubuf, cnt, 10, &val);
> > + if (ret)
> > + return ret;
> > +
> > + guard(mutex)(&simple_rbs_lock);
> > +
> > + if (!remote_event_selftest.enabled)
> > + return -ENODEV;
> > +
>
> You want a guard(preempt)(); here...
>
> > + cpu_buffer = *this_cpu_ptr(&simple_rbs);
>
> Otherwise this triggers:
>
> BUG: using smp_processor_id() in preemptible [00000000] code: bash/1096
> caller is write_event_write+0xe0/0x230 [remote_test]
>
> -- Steve
>
> > + if (!cpu_buffer)
> > + return -ENODEV;
> > +
> > + evt_test = simple_ring_buffer_reserve(cpu_buffer,
> > + sizeof(struct remote_event_format_selftest),
> > + trace_clock_global());
> > + if (!evt_test)
> > + return -ENODEV;
> > +
> > + evt_test->hdr.id = REMOTE_TEST_EVENT_ID;
> > + evt_test->id = val;
> > +
> > + simple_ring_buffer_commit(cpu_buffer);
> > +
> > + return cnt;
> > +}
> > +
next prev parent reply other threads:[~2026-01-31 12:54 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 10:43 [PATCH v10 00/30] Tracefs support for pKVM Vincent Donnefort
2026-01-26 10:43 ` [PATCH v10 01/30] ring-buffer: Add page statistics to the meta-page Vincent Donnefort
2026-01-29 0:25 ` Steven Rostedt
2026-01-26 10:43 ` [PATCH v10 02/30] ring-buffer: Store bpage pointers into subbuf_ids Vincent Donnefort
2026-01-29 0:26 ` Steven Rostedt
2026-01-26 10:43 ` [PATCH v10 03/30] ring-buffer: Introduce ring-buffer remotes Vincent Donnefort
2026-01-29 0:26 ` Steven Rostedt
2026-01-26 10:43 ` [PATCH v10 04/30] ring-buffer: Add non-consuming read for " Vincent Donnefort
2026-01-29 0:26 ` Steven Rostedt
2026-01-26 10:43 ` [PATCH v10 05/30] tracing: Introduce trace remotes Vincent Donnefort
2026-01-28 20:37 ` Steven Rostedt
2026-01-29 21:39 ` Vincent Donnefort
2026-01-28 20:52 ` Steven Rostedt
2026-01-26 10:43 ` [PATCH v10 06/30] tracing: Add reset to " Vincent Donnefort
2026-01-29 0:27 ` Steven Rostedt
2026-01-26 10:43 ` [PATCH v10 07/30] tracing: Add non-consuming read " Vincent Donnefort
2026-01-28 22:52 ` Steven Rostedt
2026-01-26 10:43 ` [PATCH v10 08/30] tracing: Add init callback " Vincent Donnefort
2026-01-29 0:27 ` Steven Rostedt
2026-01-26 10:43 ` [PATCH v10 09/30] tracing: Add events " Vincent Donnefort
2026-01-28 23:06 ` Steven Rostedt
2026-01-26 10:43 ` [PATCH v10 10/30] tracing: Add events/ root files " Vincent Donnefort
2026-01-29 0:28 ` Steven Rostedt
2026-01-26 10:44 ` [PATCH v10 11/30] tracing: Add helpers to create trace remote events Vincent Donnefort
2026-01-29 0:28 ` Steven Rostedt
2026-01-26 10:44 ` [PATCH v10 12/30] ring-buffer: Export buffer_data_page and macros Vincent Donnefort
2026-01-29 0:28 ` Steven Rostedt
2026-01-26 10:44 ` [PATCH v10 13/30] tracing: Introduce simple_ring_buffer Vincent Donnefort
2026-01-28 23:18 ` Steven Rostedt
2026-01-26 10:44 ` [PATCH v10 14/30] tracing: Add a trace remote module for testing Vincent Donnefort
2026-01-29 16:34 ` Steven Rostedt
2026-01-29 21:50 ` Vincent Donnefort
2026-01-31 12:54 ` Vincent Donnefort [this message]
2026-01-26 10:44 ` [PATCH v10 15/30] tracing: selftests: Add trace remote tests Vincent Donnefort
2026-01-29 17:05 ` Steven Rostedt
2026-01-26 10:44 ` [PATCH v10 16/30] Documentation: tracing: Add tracing remotes Vincent Donnefort
2026-01-29 17:16 ` Steven Rostedt
2026-01-26 10:44 ` [PATCH v10 17/30] tracing: load/unload page callbacks for simple_ring_buffer Vincent Donnefort
2026-01-29 17:21 ` Steven Rostedt
2026-01-26 10:44 ` [PATCH v10 18/30] tracing: Check for undefined symbols in simple_ring_buffer Vincent Donnefort
2026-01-29 17:33 ` Steven Rostedt
2026-01-26 10:44 ` [PATCH v10 19/30] KVM: arm64: Add PKVM_DISABLE_STAGE2_ON_PANIC Vincent Donnefort
2026-01-26 21:31 ` Kalesh Singh
2026-01-26 10:44 ` [PATCH v10 20/30] KVM: arm64: Add clock support to nVHE/pKVM hyp Vincent Donnefort
2026-01-26 10:44 ` [PATCH v10 21/30] KVM: arm64: Initialise hyp_nr_cpus for nVHE hyp Vincent Donnefort
2026-01-26 10:44 ` [PATCH v10 22/30] KVM: arm64: Support unaligned fixmap in the pKVM hyp Vincent Donnefort
2026-01-26 10:44 ` [PATCH v10 23/30] KVM: arm64: Add tracing capability for the nVHE/pKVM hyp Vincent Donnefort
2026-01-26 10:44 ` [PATCH v10 24/30] KVM: arm64: Add trace remote " Vincent Donnefort
2026-01-26 10:44 ` [PATCH v10 25/30] KVM: arm64: Sync boot clock with " Vincent Donnefort
2026-01-26 10:44 ` [PATCH v10 26/30] KVM: arm64: Add trace reset to " Vincent Donnefort
2026-01-26 10:44 ` [PATCH v10 27/30] KVM: arm64: Add event support to the nVHE/pKVM hyp and trace remote Vincent Donnefort
2026-01-26 10:44 ` [PATCH v10 28/30] KVM: arm64: Add hyp_enter/hyp_exit events to nVHE/pKVM hyp Vincent Donnefort
2026-01-26 10:44 ` [PATCH v10 29/30] KVM: arm64: Add selftest event support " Vincent Donnefort
2026-01-26 10:44 ` [PATCH v10 30/30] tracing: selftests: Add hypervisor trace remote tests Vincent Donnefort
2026-01-29 17:37 ` [PATCH v10 00/30] Tracefs support for pKVM Steven Rostedt
2026-01-29 21:34 ` 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=aX37eRjYBP4WmyS6@google.com \
--to=vdonnefort@google.com \
--cc=aneesh.kumar@kernel.org \
--cc=joey.gouly@arm.com \
--cc=jstultz@google.com \
--cc=kernel-team@android.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=maz@kernel.org \
--cc=mhiramat@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=qperret@google.com \
--cc=rostedt@goodmis.org \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.