Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: "Joos, Christina" <christina.joos@intel.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/1] gdb, gdbserver: Add Intel APX register support
Date: Tue, 25 Aug 2026 10:03:46 -0700	[thread overview]
Message-ID: <885068ad-c96f-4e32-ac39-8a004b7c718f@redhat.com> (raw)
In-Reply-To: <SN7PR11MB76383F1926F3C42A77F8B4BC89AF2@SN7PR11MB7638.namprd11.prod.outlook.com>

On 8/25/26 9:11 AM, Joos, Christina wrote:
> I just found a bug in this area:
> https://sourceware.org/bugzilla/show_bug.cgi?id=34561
> 
> Assuming a fix like the one indicated in comment of the bug will be merged
> before this patch I think we can add something like this on top:
> 
> ~~~
> diff --git a/gdb/i387-tdep.c b/gdb/i387-tdep.c
> index 51459c31dcc..51180714e08 100644
> --- a/gdb/i387-tdep.c
> +++ b/gdb/i387-tdep.c
> @@ -955,6 +955,8 @@ i387_guess_xsave_layout (uint64_t xcr0, size_t xsave_size,
>           Otherwise, we are not able to read xsave registers in OS generated
>           corefiles.  */
>         layout.avx_offset = 576;
> +      /* Intel APX can be available on CPUs with PKRU including AMX or not
> +        including AMX support.  */
>         layout.apx_offset = 960;
>         layout.k_offset = 1088;
>         layout.zmm_h_offset = 1152;
> @@ -974,6 +976,7 @@ i387_guess_xsave_layout (uint64_t xcr0, size_t xsave_size,
>       {
>         /* Intel CPUs supporting AVX512.  */
>         layout.avx_offset = 576;
> +      /* Intel APX can be available on CPUs supporting AVX512.  */
>         layout.apx_offset = 960;
>         layout.k_offset = 1088;
>         layout.zmm_h_offset = 1152;
> ~~~
> 
> Or do you have a different comment in mind?

I am satisfied with that. Thank you.

> My original plan was to post this patch once again including the fixes for Eli's
> feedback + ones pointed out by me here
> https://sourceware.org/pipermail/gdb-patches/2026-August/229759.html
> and then wait 1-2 weeks and merge it if there is no more feedback.
> Since it's only in the x86 area I think it should be fine for me to self-approve here.
>   
> However, in the meantime this bug mentioned above popped up.
> I think it makes sense to wait until this is resolved.
FWIW, I think you've got a better handle on all of the issues
at play than I do, so I trust you'll Do The Right Thing (TM).

Keith


  reply	other threads:[~2026-08-25 17:04 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
2026-08-25 16:11     ` Joos, Christina
2026-08-25 17:03       ` Keith Seitz [this message]
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=885068ad-c96f-4e32-ac39-8a004b7c718f@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