linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ian Rogers <irogers@google.com>
To: linux-perf-users <linux-perf-users@vger.kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>
Subject: Linux Plumbers Tracing/Perf events Microconference - abstract deadline tomorrow
Date: Thu, 11 Jul 2024 09:54:27 -0700	[thread overview]
Message-ID: <CAP-5=fV+i3cuCWOrAw9sxYW7WSb47joWFpa3K3Eqw1MpLkqNfw@mail.gmail.com> (raw)

Hi,

There will be microconference at LPC on tracing and perf events:
https://lpc.events/event/18/abstracts/1778/

Potential topics include:
 - Feedback about the tracing/perf subsystems overall (e.g. how can
people help the maintainers).
 - Reboot persistent in-memory tracing buffers, this would make ftrace
a very powerful debugging and performance analysis tool for kexec and
could also be used for post crash debugging.
 - Dynamic change of ftrace events to improve symbolic printing.
 - Userspace instrumentation (libside), including discussion of its
impacts on the User events ABI.
 - Collect state dump events from kernel drivers (e.g. dump wifi
interfaces configuration at a given point in time through trace
buffers).
 - Current work implementing performance monitoring in the kernel,
 - User land profiling and analysis tools using the perf event API,
 - Improving the kernel perf event and PMU APIs,
 - Interaction between perf events and subsystems like cgroups, kvm,
drm, bpf, etc.,
 - Improving the perf tool and its interfaces in particular w.r.t. to
scalability of the tool,
 - Implementation of new perf features and tools using eBPF, like the
ones in tools/perf/util/bpf_skel/.
 - Further use of type information to augment the perf tools,
 - Novel uses of perf events for debugging and correctness,
 - New challenges in performance monitoring for the Linux kernel,
 - Regression testing/CI integration for the perf kernel
infrastructure and tools,
 - Improving documentation,
 - Security aspects of using tracing/perf tools,

Abstract submissions happen through the website (you don't need a full
presentation):
https://lpc.events/event/18/abstracts/#submit-abstract

With the deadline being tomorrow July 12th.

Thanks,
Ian

                 reply	other threads:[~2024-07-11 16:54 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='CAP-5=fV+i3cuCWOrAw9sxYW7WSb47joWFpa3K3Eqw1MpLkqNfw@mail.gmail.com' \
    --to=irogers@google.com \
    --cc=acme@kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=namhyung@kernel.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;
as well as URLs for NNTP newsgroup(s).