Linux debuggers
 help / color / mirror / Atom feed
From: Stephen Brennan <stephen.s.brennan@oracle.com>
To: Omar Sandoval <osandov@osandov.com>, linux-debuggers@vger.kernel.org
Subject: Re: Linux Kernel Debugging Tools Monthly Meeting on Wednesday, February 18th
Date: Tue, 17 Feb 2026 14:44:37 -0800	[thread overview]
Message-ID: <cb3b1ffb-7b30-4afd-af20-374b660511b1@oracle.com> (raw)
In-Reply-To: <aZTtPsRAMVd_6umd@telecaster>

If content is light, I'd be happy to share progress on the BTF
implementation, which is working quite nicely. Upstream kernels are
still missing type entries for global variables, but that's actually
pretty easily sidestepped for a lot of cases, so it can be practically
useful even with that limitation. It could be interesting to discuss
ideas about how to properly test it in vmtest.

If we can get something useful with BTF merged even with the current
state of kernel BTF, that would be a major factor to share upstream with
the BPF community to motivate adding global variable support in one way
or another.

Stephen

On 2/17/26 2:35 PM, Omar Sandoval wrote:
> The next Linux Kernel Debugging Tools meeting is this Wednesday,
> February 18th at 11:30 AM Pacific time. This meeting is a forum to
> discuss development of Linux kernel debugging tools like drgn, crash,
> and more.
> 
> Here is the agenda so far:
> 
> - drgn release this week.
> 
> Reminder: I will be out of the office from February 23-March 27.
> 
> Please reply with anything else you'd like to add. As always, if you
> would like to attend, please email me offlist.
> 
> Thanks!
> Omar
> 


      reply	other threads:[~2026-02-17 22:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-17 22:35 Linux Kernel Debugging Tools Monthly Meeting on Wednesday, February 18th Omar Sandoval
2026-02-17 22:44 ` Stephen Brennan [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=cb3b1ffb-7b30-4afd-af20-374b660511b1@oracle.com \
    --to=stephen.s.brennan@oracle.com \
    --cc=linux-debuggers@vger.kernel.org \
    --cc=osandov@osandov.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