From: Keith Seitz <keiths@redhat.com>
To: Christina Joos <christina.joos@intel.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/1] gdb, gdbserver: Add Intel APX register support
Date: Thu, 13 Aug 2026 11:14:11 -0700 [thread overview]
Message-ID: <c92d7d18-cc51-40ac-8413-5c048e336cda@redhat.com> (raw)
In-Reply-To: <20260725105335.2664219-2-christina.joos@intel.com>
Hi,
On 7/25/26 3:53 AM, Christina Joos wrote:
> From: "H.J. Lu" <hjl.tools@gmail.com>
>
> Intel Advanced Performance Extensions (APX) doubles the number of
> general-purpose registers (GPRs) from 16 to 32 (r16-r31).
Thank you for pursuing this. I'm not going to claim that I completely
understand the nuiance of modern x86_64 features, but generally,
the code seems okay to me.
> Those new 64-bit Extended GPRs (EGPRs) do not change the size of the
> XSAVE area, as they take up the space left behind by the deprecated
> MPX registers.
>
> In contrast to the legacy GPRS, EGPRs are not enabled by default in 64-bit
> mode but are xcr0 enabled based on APX_F Intel APX state. Define
> X86_XSTATE_APX_F to support this new configuration.
>
> Add gdb and gdbserver registers support for those new 64-bit EGPRs.
> Also add byte, word and dword pseudo register support.
I appreciate the simplified approach in this revision, removing the
previously proposed maint commands. Generating core files is much
better/safe approach.
One trivial nit (no need to repost):
I previously asked whether apx_offset should be set independently of
PKRU/AVX512 in i387_guess_xsave_layout()[1]. You explained that APX is
only expected with PKRU or AVX512 on known Intel CPUs addresses[2].
A brief comment documenting that assumption would be helpful for future
readers. 'Cause, as expected, I forgot all about that discussion
already! :-p
Reviewed-By: Keith Seitz <keiths@redhat.com>
Keith
[1] https://sourceware.org/pipermail/gdb-patches/2026-June/228135.html
[2] https://sourceware.org/pipermail/gdb-patches/2026-July/228491.html
next prev parent reply other threads:[~2026-08-13 18:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-25 10:53 [PATCH 0/1] Add Intel APX support Christina Joos
2026-07-25 10:53 ` [PATCH 1/1] gdb, gdbserver: Add Intel APX register support Christina Joos
2026-07-25 11:07 ` Eli Zaretskii
2026-08-13 18:14 ` Keith Seitz [this message]
2026-08-25 16:11 ` Joos, Christina
2026-08-25 17:03 ` Keith Seitz
2026-08-25 14:22 ` Joos, Christina
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=c92d7d18-cc51-40ac-8413-5c048e336cda@redhat.com \
--to=keiths@redhat.com \
--cc=christina.joos@intel.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