From: Omar Sandoval <osandov@osandov.com>
To: Serapheim Dimitropoulos <serapheimd@gmail.com>
Cc: linux-debuggers@vger.kernel.org, Usama Arif <usama.arif@linux.dev>
Subject: Re: Debugging Microconference at Linux Plumbers Conference?
Date: Tue, 30 Jun 2026 10:27:31 -0700 [thread overview]
Message-ID: <akP8g_SiT2H2VwrZ@telecaster> (raw)
In-Reply-To: <20260409144144.72399-1-sdimitropoulos@coreweave.com>
On Thu, Apr 09, 2026 at 10:41:44AM -0400, Serapheim Dimitropoulos wrote:
> On Wed, Apr 08, 2026 at 12:50:14PM -0700, Omar Sandoval wrote:
> > We are gauging interest in hosting another Debugging Microconference at
> > Linux Plumbers Conference this year. Topics would focus on common
> > challenges people are facing with debugging tooling: collecting and
> > analyzing core dumps, doing live analysis, developing more powerful
> > debugger features and tools, etc.
>
> I'd be interested in attending and potentially starting a discussion
> over a few things that we've been working on at CoreWeave!
>
> Specifically:
>
> (1) Capturing crash dumps with tight memory and space constraints at
> scale
>
> (2) Triaging, deduplicating, and categorizing crash dumps in
> production
>
> (3) We've been experimenting with out-of-band kernel introspection
> (using drgn in a DPU to introspect the host with one-sided RDMA
> ops). Would be cool to see if others have worked on the same or
> similar problems.
>
> Thanks,
> Serapheim
Just to update the list, instead of having a separate Debugging
Microconference, we're going to submit topics to the Monitoring and
Observability MC since that has a lot of overlap:
https://lpc.events/event/20/sessions/262/.
Serapheim: Usama, who is one of the Monitoring and Observability MC
leads, expressed interest in your topics and asked if you could submit
something.
Thanks,
Omar
prev parent reply other threads:[~2026-06-30 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 19:50 Debugging Microconference at Linux Plumbers Conference? Omar Sandoval
2026-04-09 14:41 ` Serapheim Dimitropoulos
2026-06-30 17:27 ` Omar Sandoval [this message]
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=akP8g_SiT2H2VwrZ@telecaster \
--to=osandov@osandov.com \
--cc=linux-debuggers@vger.kernel.org \
--cc=serapheimd@gmail.com \
--cc=usama.arif@linux.dev \
/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