From: Steven Rostedt <steven@rostedt.org>
To: LKML <linux-kernel@vger.kernel.org>,
"linux-trace-users@vger.kernel.org"
<linux-trace-users@vger.kernel.org>,
Linux trace kernel <linux-trace-kernel@vger.kernel.org>,
Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Mark Rutland <mark.rutland@arm.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ian Rogers <irogers@google.com>,
Dylan Hatch <dylanbhatch@google.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Jens Remus <jremus@linux.ibm.com>,
Indu Bhagat <ibhagatgnu@gmail.com>,
Beau Belgrave <beaub@linux.microsoft.com>,
Tomas Glozar <tglozar@redhat.com>,
Gabriele Monaco <gmonaco@redhat.com>
Subject: [ANNOUNCE/CFP] Tracing Microconference at Linux Plumbers
Date: Tue, 9 Jun 2026 11:02:42 -0400 [thread overview]
Message-ID: <20260609110242.467f37ce@fedora> (raw)
The Tracing Microconference is accepting new topic proposals.
https://lpc.events/event/20/contributions/2316/
All Linux kernel tracing related topics are appropriate to discuss. If
there's a Linux kernel tracing issue that you are having or a feature
you would like to see, please submit your problem statement at:
https://lpc.events/event/20/abstracts/
Make sure to select "Tracing MC" in the "Track" pulldown.
Topics may include but not limited to;
o Stack tracing features
o Better lock statistic tracing
o Better system call tracepoint recording
o Updates to the persistent ring buffer
o More features for dynamic events
o Better integration between perf, ftrace and BPF
o Integration with BTF
The above is just ideas for topics, but is not an exhausted list. Feel
free to submit anything you think is relevant.
For what is expected for a microconference, please read the blog on
"The Ideal Microconference Topic Session":
https://lpc.events/blog/current/index.php/2023/06/26/the-ideal-microconference-topic-session/
Note, those that submit topics before July 10th will become eligible to
pre-register for the conference.
The CFP itself closes on August 7th.
Looking forward to seeing you at Linux Plumbers in Prague!
-- Steve
reply other threads:[~2026-06-09 15:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260609110242.467f37ce@fedora \
--to=steven@rostedt.org \
--cc=acme@kernel.org \
--cc=beaub@linux.microsoft.com \
--cc=dylanbhatch@google.com \
--cc=gmonaco@redhat.com \
--cc=ibhagatgnu@gmail.com \
--cc=irogers@google.com \
--cc=jpoimboe@kernel.org \
--cc=jremus@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tglozar@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.