From: Omar Sandoval <osandov@osandov.com>
To: linux-debuggers@vger.kernel.org
Subject: Re: Linux Kernel Debugging Tools Monthly Meeting on Wednesday, February 22nd
Date: Wed, 22 Feb 2023 12:24:10 -0800 [thread overview]
Message-ID: <Y/Z56qVhd9m/Ycyb@telecaster> (raw)
In-Reply-To: <Y/VrMXDb6dow836M@telecaster>
On Tue, Feb 21, 2023 at 05:09:05PM -0800, Omar Sandoval wrote:
> Hello! The next Linux Kernel Debugging Tools meeting is tomorrow,
> Wednesday, February 22nd at 11:30 AM Pacific time. This meeting is a
> forum to discuss development of Linux kernel debugging tools like drgn,
> crash, and more.
>
> I apologize for the short notice. Presidents' Day in the US threw me
> off. If you would like to attend, please email me offlist!
>
> The agenda so far is:
>
> - Testing on architectures other than x86-64.
> - /proc/kcore can't be enabled on Arm. I've patched it in for the drgn
> test kernel builds:
> https://github.com/osandov/drgn/blob/08cb38cc2f9a6c1c1ca0352e9962d77bd2e0c0d4/vmtest/patches/proc-kcore-allow-enabling-CONFIG_PROC_KCORE-on-ARM.patch.
> I'm curious if anyone else has encountered this or has more
> background.
> - drgn module API prototype:
> https://github.com/osandov/drgn/tree/modules. Are there any important
> use cases not covered?
> - Jay Kamat: adding type/member alignment to drgn APIs.
>
> Feel free to reply with anything else you'd like to add to the agenda.
>
> Also note that I will be on paternity leave from March 1st-May 3rd
> (possibly earlier). I'm dedicating my time until then to catching up on
> code review. If there's anything you would like me to prioritize
> reviewing, please let me know.
Here are the notes from today's meeting:
- LPC is scheduled for November 13th-15th in Richmond, Virginia. We will
try to arrange a kernel debugging tools micro-conference or BoF.
- Omar's setup for testing AArch64, Arm, ppc64, and s390x support in
drgn.
- Kernels are being built along with x86-64 kernels now.
- I'm still setting up a userspace environment with debootstrap
manually and testing locally. I'll get some form of this in the
repository so we can start running it in CI.
- I asked whether crash had any tips for testing to share or any way
they could leverage drgn's infrastructure, but Philipp Rudo noted
that their testing is mostly manual, so there's not much that can
be done at this point.
- No one had any additional background on /proc/kcore for Arm. It's
probably worth trying to enable it upstream.
- Proposed drgn module API covers the main use cases brought up.
- It will require changes for users that rely on -s or
load_debug_info() loading arbitrary files that don't match
anything in the program (e.g., Object Introspection).
- Jay Kamat talked about adding type and member alignment to the drgn
APIs for Object Introspection to make use of. No one else currently
has a use case for this (the member offsets are usually good enough),
so we'll probably go with a minimal solution to unblock Object
Introspection.
- Meetings in March and April are cancelled. See everyone in a couple of
months!
Thanks,
Omar
prev parent reply other threads:[~2023-02-22 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 1:09 Linux Kernel Debugging Tools Monthly Meeting on Wednesday, February 22nd Omar Sandoval
2023-02-22 20:24 ` 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=Y/Z56qVhd9m/Ycyb@telecaster \
--to=osandov@osandov.com \
--cc=linux-debuggers@vger.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 read-only IMAP folder(s) and NNTP newsgroup(s).