From: Eli Zaretskii <eliz@gnu.org>
To: "Schimpe, Christina" <christina.schimpe@intel.com>
Cc: gdb-patches@sourceware.org, felix.willgerodt@intel.com,
luis.machado@arm.com
Subject: Re: [PATCH v4 2/2] LAM: Enable tagged pointer support for watchpoints.
Date: Mon, 08 Jul 2024 17:53:15 +0300 [thread overview]
Message-ID: <861q440wbo.fsf@gnu.org> (raw)
In-Reply-To: <SN7PR11MB76380659345D1FAB71DD0330F9DA2@SN7PR11MB7638.namprd11.prod.outlook.com> (christina.schimpe@intel.com)
> From: "Schimpe, Christina" <christina.schimpe@intel.com>
> CC: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>, "Willgerodt,
> Felix" <felix.willgerodt@intel.com>, "luis.machado@arm.com"
> <luis.machado@arm.com>
> Date: Mon, 8 Jul 2024 14:25:50 +0000
>
> I understand that the NEWS text seems rather short, especially compared
> to my commit message.
> One reason why I kept the NEWS generic (without LAM and its specifics) is
> because theoretically the patch should work for AMD's tagged pointer support, too.
> They call their tagged pointer support "upper address ignore" (UAI).
>
> However, I still could mention LAM in that way in the NEWS:
>
> - GDB now supports watchpoints for tagged data pointers on amd64,
> e.g. as provided by Intel's linear address masking (LAM) feature.
>
> or
>
> - GDB now supports watchpoints for tagged data pointers on amd64.
> For more information on tagged data pointers, see
> https://en.wikipedia.org/wiki/Tagged_pointer.
>
> Although given that I did not test UAI and don't know about its current
> state, I think it's better to use my first suggestion.
I think we can do both:
GDB now supports watchpoints for tagged data pointers (see
https://en.wikipedia.org/wiki/Tagged_pointer) on amd64, such as the
one used by the Linear Address Masking (LAM) feature provided by
Intel.
> If you don't like my current suggestion, I have no problem adding a
> proper documentation on tagged pointers in the manual or adding
> more info to the NEWS.
An informative enough NEWS entry should be fine in this case, I think.
Thanks.
next prev parent reply other threads:[~2024-07-08 14:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 10:17 [PATCH v4 0/2] Add amd64 LAM watchpoint support Schimpe, Christina
2024-07-04 10:17 ` [PATCH v4 1/2] gdb: Make tagged pointer support configurable Schimpe, Christina
2024-07-04 10:17 ` [PATCH v4 2/2] LAM: Enable tagged pointer support for watchpoints Schimpe, Christina
2024-07-04 12:37 ` Willgerodt, Felix
2024-07-04 12:52 ` Eli Zaretskii
2024-07-04 13:05 ` Schimpe, Christina
2024-07-04 13:15 ` Schimpe, Christina
2024-07-04 14:06 ` Eli Zaretskii
2024-07-05 8:53 ` Schimpe, Christina
2024-07-05 10:47 ` Eli Zaretskii
2024-07-08 8:52 ` Schimpe, Christina
2024-07-08 11:42 ` Eli Zaretskii
2024-07-08 14:25 ` Schimpe, Christina
2024-07-08 14:53 ` Eli Zaretskii [this message]
2024-07-08 14:57 ` Schimpe, Christina
2024-07-04 14:02 ` Eli Zaretskii
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=861q440wbo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=christina.schimpe@intel.com \
--cc=felix.willgerodt@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.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