linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Pavlu <petr.pavlu@suse.com>
To: rostedt@goodmis.org, mhiramat@kernel.org, mathieu.desnoyers@efficios.com
Cc: zhengyejian1@huawei.com, linux-trace-kernel@vger.kernel.org,
	linux-kernel@vger.kernel.org, Petr Pavlu <petr.pavlu@suse.com>
Subject: [PATCH 0/2] tracing: Simplify and fix "buffered event" synchronization
Date: Mon, 27 Nov 2023 16:12:46 +0100	[thread overview]
Message-ID: <20231127151248.7232-1-petr.pavlu@suse.com> (raw)

Rework the maintenance synchronization for buffered events to simplify
it and to address several found problems.

Petr Pavlu (2):
  tracing: Simplify and fix "buffered event" synchronization
  tracing: Disable events in reverse order of their enable operation

 kernel/trace/trace.c        | 66 +++++++++++++++----------------------
 kernel/trace/trace_events.c | 17 ++++++----
 2 files changed, 37 insertions(+), 46 deletions(-)


base-commit: 2cc14f52aeb78ce3f29677c2de1f06c0e91471ab
-- 
2.35.3


             reply	other threads:[~2023-11-27 15:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27 15:12 Petr Pavlu [this message]
2023-11-27 15:12 ` [PATCH 1/2] tracing: Simplify and fix "buffered event" synchronization Petr Pavlu
2023-11-27 17:41   ` Steven Rostedt
2023-11-28 15:05     ` Petr Pavlu
2023-11-28 15:27       ` Steven Rostedt
2023-11-29  9:22         ` Petr Pavlu
2023-11-29 14:58           ` Steven Rostedt
2023-12-01 14:17             ` Petr Pavlu
2023-12-01 14:46               ` Steven Rostedt
2023-12-05 16:16                 ` Petr Pavlu
2023-11-27 15:12 ` [PATCH 2/2] tracing: Disable events in reverse order of their enable operation Petr Pavlu
2023-11-27 17:58   ` Steven Rostedt
2023-11-28 15:06     ` Petr Pavlu

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=20231127151248.7232-1-petr.pavlu@suse.com \
    --to=petr.pavlu@suse.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 \
    --cc=zhengyejian1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).