linux-debuggers.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: linux-debuggers@vger.kernel.org
Subject: Linux Kernel Debugging Tools Monthly Meeting on Wednesday, February 22nd
Date: Tue, 21 Feb 2023 17:09:05 -0800	[thread overview]
Message-ID: <Y/VrMXDb6dow836M@telecaster> (raw)

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.

Thanks!
Omar

             reply	other threads:[~2023-02-22  1:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22  1:09 Omar Sandoval [this message]
2023-02-22 20:24 ` Linux Kernel Debugging Tools Monthly Meeting on Wednesday, February 22nd Omar Sandoval

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/VrMXDb6dow836M@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 NNTP newsgroup(s).