From: Uros Bizjak <ubizjak@gmail.com>
To: linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Uros Bizjak <ubizjak@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>
Subject: [PATCH 0/3] Improve trace/ring_buffer.c
Date: Tue, 28 Feb 2023 18:59:26 +0100 [thread overview]
Message-ID: <20230228175929.7534-1-ubizjak@gmail.com> (raw)
This series improves ring_buffer.c by changing the type of some
static functions to void or bool and uses try_cmpxchg instead of
cmpxchg (*ptr, old, new) == old where appropriate.
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>
Uros Bizjak (3):
ring_buffer: Change some static functions to void
ring_buffer: Change some static functions to bool
ring_buffer: Use try_cmpxchg instead of cmpxchg
kernel/trace/ring_buffer.c | 89 ++++++++++++++++----------------------
1 file changed, 37 insertions(+), 52 deletions(-)
--
2.39.2
next reply other threads:[~2023-02-28 17:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 17:59 Uros Bizjak [this message]
2023-02-28 17:59 ` [PATCH 1/3] ring_buffer: Change some static functions to void Uros Bizjak
2023-02-28 22:55 ` Masami Hiramatsu
2023-03-01 8:46 ` Uros Bizjak
2023-03-01 16:34 ` Steven Rostedt
2023-03-02 23:57 ` Masami Hiramatsu
2023-02-28 17:59 ` [PATCH 2/3] ring_buffer: Change some static functions to bool Uros Bizjak
2023-02-28 17:59 ` [PATCH 3/3] ring_buffer: Use try_cmpxchg instead of cmpxchg Uros Bizjak
2023-02-28 21:43 ` Steven Rostedt
2023-03-01 9:37 ` Uros Bizjak
2023-03-01 15:49 ` Joel Fernandes
2023-03-01 15:50 ` Joel Fernandes
2023-03-01 16:18 ` Steven Rostedt
2023-03-01 16:28 ` Steven Rostedt
2023-03-01 17:57 ` Uros Bizjak
2023-03-01 18:08 ` Uros Bizjak
2023-03-01 17:16 ` Uros Bizjak
2023-03-01 18:18 ` Steven Rostedt
2023-03-01 18:28 ` Steven Rostedt
2023-03-01 18:37 ` Uros Bizjak
2023-02-28 19:35 ` [PATCH 0/3] Improve trace/ring_buffer.c Steven Rostedt
2023-03-01 8:35 ` Uros Bizjak
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=20230228175929.7534-1-ubizjak@gmail.com \
--to=ubizjak@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--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
Powered by JetHome