From: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
To: Abhay Kandpal <abhay@linux.ibm.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "cel@linux.ibm.com" <cel@linux.ibm.com>, Abhay Kandpal <Abhay.k@ibm.com>
Subject: Re: [PATCH v1] PowerPC: Add support for Dense Math registers (RFC02653)
Date: Mon, 28 Sep 2026 09:22:37 +0000 [thread overview]
Message-ID: <f499fa0f30f8ab4ba6daf176b551ee031ec0e52d.camel@de.ibm.com> (raw)
In-Reply-To: <687032cb-729a-437e-b1cc-0fa01772e0ac@linux.ibm.com>
Abhay Kandpal <abhay@linux.ibm.com> wrote:
>The existing names encode the base ISA level, but DMR is a later ISA
>feature layered on an isa207-derived description, so isa207-dmr would
>misstate the ISA level. A few options:
>
>1. powerpc-isa207-dmr-vsx64l - names the base feature set the description extends
>2. powerpc-isa32-dmr-vsx64l - names DMR's own ISA level (ISA 3.2)
>3. powerpc-dmr-vsx64l - as posted, no ISA level
I'm not familiar with ISA 3.2 - is DMR mandatory or optional in 3.2?
And are there any *other* 3.2 features that GDB needs to implement?
I'd prefer "powerpc-isa32-vsx64l" to refer to an implementation of
all mandatory features (including DMR if mandatory), and if DMR is
optional, then in addition "powerpc-isa32-dmr-vsx64l" for the
combination of mandatory ISA 3.2 features plus DMR.
>So in v2 I'll convert the native side to the regset mechanism
>throughout: fetch_regset/store_regset with NT_PPC_DMR in
>fetch_register, fetch_ppc_registers, store_register and
>store_ppc_registers, and a regset-based availability check in
>read_description. That removes the need for the
>PTRACE_GETDMREGS/PTRACE_SETDMREGS defines, so I'll drop the
>block rather than move it - unless something still needs them,
>in which case I'll relocate it as you suggest.
No, if they're not needed, it's better to drop these defines.
>Yes - PPC_FEATURE2_DMF (0x00008000, Dense Math Facility). I'll add
that
>check. The kernel does save and restore these registers across context
>switches. The hwcap bit and the DMR ptrace support are currently in
>separate kernel branches here, so I'm assembling a tree with both before
>validating v2.
Thanks!
Bye,
Ulrich
prev parent reply other threads:[~2026-09-28 9:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 6:30 Abhay Kandpal
2026-09-25 12:05 ` Ulrich Weigand
2026-09-26 9:34 ` Abhay Kandpal
2026-09-28 9:22 ` Ulrich Weigand [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=f499fa0f30f8ab4ba6daf176b551ee031ec0e52d.camel@de.ibm.com \
--to=ulrich.weigand@de.ibm.com \
--cc=Abhay.k@ibm.com \
--cc=abhay@linux.ibm.com \
--cc=cel@linux.ibm.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