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 v2 0/3] tracing: Simplify and fix "buffered event" synchronization
Date: Tue,  5 Dec 2023 17:17:33 +0100	[thread overview]
Message-ID: <20231205161736.19663-1-petr.pavlu@suse.com> (raw)

Fix a few problems related to the maintenance of buffered events.

Changes since v1 [1]:
* Address found problems individually. The approach in v1 tried to
  simplify the buffered event synchronization but had performance
  issues.

[1] https://lore.kernel.org/linux-trace-kernel/20231127151248.7232-1-petr.pavlu@suse.com/

Petr Pavlu (3):
  tracing: Fix incomplete locking when disabling buffered events
  tracing: Fix a warning when allocating buffered events fails
  tracing: Fix a possible race when disabling buffered events

 kernel/trace/trace.c | 35 +++++++++++++++++------------------
 1 file changed, 17 insertions(+), 18 deletions(-)


base-commit: bee0e7762ad2c6025b9f5245c040fcc36ef2bde8
-- 
2.35.3


             reply	other threads:[~2023-12-05 16:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 16:17 Petr Pavlu [this message]
2023-12-05 16:17 ` [PATCH v2 1/3] tracing: Fix incomplete locking when disabling buffered events Petr Pavlu
2023-12-05 16:17 ` [PATCH v2 2/3] tracing: Fix a warning when allocating buffered events fails Petr Pavlu
2023-12-05 16:17 ` [PATCH v2 3/3] tracing: Fix a possible race when disabling buffered events 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=20231205161736.19663-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).