From: Steven Rostedt <rostedt@goodmis.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Sachin Sant <sachinp@linux.ibm.com>
Subject: Re: [PATCH] tracing: Have trace_marker writes be just half of TRACE_SEQ_SIZE
Date: Mon, 4 Mar 2024 21:37:50 -0500 [thread overview]
Message-ID: <20240304213750.1baef01d@gandalf.local.home> (raw)
In-Reply-To: <20240304213538.13fe1f3b@gandalf.local.home>
On Mon, 4 Mar 2024 21:35:38 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> > And it's not for debugging, it's for validation of assumptions
> > made about an upper bound limit defined for a compile-time
> > check, so as the code evolves issues are caught early.
>
> validating is debugging.
Did Linus put you up to this? To test me to see if I'm learning how to say "No" ;-)
-- Steve
next prev parent reply other threads:[~2024-03-05 2:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 0:27 [PATCH] tracing: Have trace_marker writes be just half of TRACE_SEQ_SIZE Steven Rostedt
2024-03-05 0:43 ` Randy Dunlap
2024-03-05 0:49 ` Steven Rostedt
2024-03-05 1:15 ` Mathieu Desnoyers
2024-03-05 1:35 ` Steven Rostedt
2024-03-05 1:36 ` Mathieu Desnoyers
2024-03-05 1:57 ` Steven Rostedt
2024-03-05 1:41 ` Steven Rostedt
2024-03-05 1:42 ` Mathieu Desnoyers
2024-03-05 1:59 ` Steven Rostedt
2024-03-05 2:18 ` Mathieu Desnoyers
2024-03-05 2:35 ` Steven Rostedt
2024-03-05 2:37 ` Steven Rostedt [this message]
2024-03-05 2:48 ` Mathieu Desnoyers
2024-03-05 3:07 ` 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=20240304213750.1baef01d@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=sachinp@linux.ibm.com \
--cc=torvalds@linux-foundation.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