From: "Joos, Christina" <christina.joos@intel.com>
To: Keith Seitz <keiths@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH v3 0/1] Add Intel APX support
Date: Wed, 21 Oct 2026 20:43:13 +0000 [thread overview]
Message-ID: <SN7PR11MB7638E6AF1C533EA8CB95496989662@SN7PR11MB7638.namprd11.prod.outlook.com> (raw)
In-Reply-To: <b03912c1-645f-4795-b38c-1465b2e2a4b5@redhat.com>
> -----Original Message-----
> From: Keith Seitz <keiths@redhat.com>
> Sent: Mittwoch, 14. Oktober 2026 20:28
> To: Joos, Christina <christina.joos@intel.com>
> Cc: gdb-patches@sourceware.org
> Subject: Re: [PATCH v3 0/1] Add Intel APX support
>
> Hi,
>
> On 10/8/26 12:54 PM, Joos, Christina wrote:
> > It has been regression-tested on different CPUs
> > - without APX support,
> > - with APX support but without AMX support,
> > - with both APX and AMX support.
> >
> > The following board files were included:
> > unix, unix/-m32, native-gdbserver, native-gdbserver/-m32,
> > native-extended-gdbserver
> >
> > I will wait until the end of next week in case anyone has additional feedback
> or concerns.
> > If no issues are raised, I plan to self-approve and push the patch.
> I don't have access to APX-enabled hardware, but I have run testing on other
> x86 hardware. Since you've addressed all my issues (and then some!), I have
> nothing further to ask. I agree that this patch is ready. [I've already given my
> Reviewed-By.]
Thanks, Keith. I've pushed this now.
Christina
________________________________________
Intel Deutschland GmbH
Registered Address: Dornacher Strasse 1, 85622 Feldkirchen, Germany
Tel: +49 (89) 99143-0
www.intel.de
Managing Directors: Candice Moore, Jeffrey Schneiderman, Ramachandran Sitaraman
Chairperson of the Supervisory Board: Sonja Pierer
Registered Seat: Munich Commercial Register B: Amtsgericht Munich HRB 186928
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
prev parent reply other threads:[~2026-10-21 20:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 15:09 Christina Joos
2026-09-29 15:09 ` [PATCH v3 1/1] gdb, gdbserver: Add Intel APX register support Christina Joos
2026-09-29 15:15 ` [PATCH v3 0/1] Add Intel APX support Joos, Christina
2026-10-08 19:54 ` Joos, Christina
2026-10-14 18:28 ` Keith Seitz
2026-10-21 20:43 ` Joos, Christina [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=SN7PR11MB7638E6AF1C533EA8CB95496989662@SN7PR11MB7638.namprd11.prod.outlook.com \
--to=christina.joos@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.com \
/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