From: Aaron Griffith <aargri@gmail.com>
To: "Alkallas, Mouhanad" <Mouhanad.Alkallas@amd.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Proposed Addition to GDB packets
Date: Thu, 21 Aug 2025 19:07:35 -0400 [thread overview]
Message-ID: <CAPcvo0RuPisN1Uf2tAA24hCPCRx0PYqVckLLR3dGjWVq9Civow@mail.gmail.com> (raw)
In-Reply-To: <DM6PR12MB362505230AEE5BF14BCE7869F332A@DM6PR12MB3625.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 954 bytes --]
On Thu, Aug 21, 2025 at 5:05 PM Alkallas, Mouhanad <
Mouhanad.Alkallas@amd.com> wrote:
> The proposal is to add a packet “J” for customization in privately
> defined KGDB IO Module.
>
> Packet format would “J <custom data>”, instead of gdbstub.c handling
> the packet, it would forward the call to the attached KGDB IO Module
> to service the packet.
I'm not familiar with KGDB specifically, but a common solution used by
other stubs is to use the "qRcmd" packet for custom commands. I know the
Black Magic debug probe uses this to allow the user to scan the JTAG chain
it's connected to and a few other things.
The documentation for KGDB [1] indicates it already uses this packet for
some commands. Is it possible to hook in to that existing mechanism? Or is
that unsuitable for the problem you're trying to solve?
[1]:
https://www.kernel.org/doc/html/v4.14/dev-tools/kgdb.html#running-kdb-commands-from-gdb
-Aaron
[-- Attachment #2: Type: text/html, Size: 1227 bytes --]
next prev parent reply other threads:[~2025-08-21 23:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 21:05 Alkallas, Mouhanad
2025-08-21 23:07 ` Aaron Griffith [this message]
2025-08-25 14:54 ` Alkallas, Mouhanad
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=CAPcvo0RuPisN1Uf2tAA24hCPCRx0PYqVckLLR3dGjWVq9Civow@mail.gmail.com \
--to=aargri@gmail.com \
--cc=Mouhanad.Alkallas@amd.com \
--cc=gdb-patches@sourceware.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