From: Steven Rostedt <rostedt@goodmis.org>
To: Vincent Donnefort <vdonnefort@google.com>
Cc: mhiramat@kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
mathieu.desnoyers@efficios.com, kernel-team@android.com
Subject: Re: [PATCH v17 3/6] tracing: Add snapshot refcount
Date: Mon, 19 Feb 2024 13:17:54 -0500 [thread overview]
Message-ID: <20240219131754.5d26f4e6@gandalf.local.home> (raw)
In-Reply-To: <20240213114945.3528801-4-vdonnefort@google.com>
On Tue, 13 Feb 2024 11:49:42 +0000
Vincent Donnefort <vdonnefort@google.com> wrote:
> @@ -9678,7 +9739,9 @@ trace_array_create_systems(const char *name, const char *systems)
> raw_spin_lock_init(&tr->start_lock);
>
> tr->max_lock = (arch_spinlock_t)__ARCH_SPIN_LOCK_UNLOCKED;
> -
> +#ifdef CONFIG_TRCER_MAX_TRACE
Oops!
I'll fix this too.
-- Steve
> + spinlock_init(&tr->snapshot_trigger_lock);
> +#endif
> tr->current_trace = &nop_trace;
>
> INIT_LIST_HEAD(&tr->systems);
next prev parent reply other threads:[~2024-02-19 18:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 11:49 [PATCH v17 0/6] Introducing trace buffer mapping by user-space Vincent Donnefort
2024-02-13 11:49 ` [PATCH v17 1/6] ring-buffer: Zero ring-buffer sub-buffers Vincent Donnefort
2024-02-13 11:49 ` [PATCH v17 2/6] ring-buffer: Introducing ring-buffer mapping functions Vincent Donnefort
2024-02-13 20:53 ` Steven Rostedt
2024-02-13 22:51 ` Steven Rostedt
2024-02-14 1:23 ` kernel test robot
2024-02-14 10:26 ` kernel test robot
2024-02-13 11:49 ` [PATCH v17 3/6] tracing: Add snapshot refcount Vincent Donnefort
2024-02-19 18:17 ` Steven Rostedt [this message]
2024-02-19 18:22 ` Steven Rostedt
2024-02-13 11:49 ` [PATCH v17 4/6] tracing: Allow user-space mapping of the ring-buffer Vincent Donnefort
2024-02-13 11:49 ` [PATCH v17 5/6] Documentation: tracing: Add ring-buffer mapping Vincent Donnefort
2024-02-13 11:49 ` [PATCH v17 6/6] ring-buffer/selftest: Add ring-buffer mapping test 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=20240219131754.5d26f4e6@gandalf.local.home \
--to=rostedt@goodmis.org \
--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=vdonnefort@google.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®