From: "Willgerodt, Felix" <felix.willgerodt@intel.com>
To: "Schimpe, Christina" <christina.schimpe@intel.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 1/3] gdb: Make tagged pointer support configurable.
Date: Wed, 22 May 2024 13:37:28 +0000 [thread overview]
Message-ID: <MN2PR11MB456698D2D3B9987E6E9CC61D8EEB2@MN2PR11MB4566.namprd11.prod.outlook.com> (raw)
In-Reply-To: <SN7PR11MB76387D836B7CC0041CD36D03F9EE2@SN7PR11MB7638.namprd11.prod.outlook.com>
> > I feel like one of the main reasons for this patch is missing. That on x86 (or
> > some architectures in general) we want to avoid the overhead of doing this
> > unconditionally. E.g. as we don't want to parse a file repeatedly on x86.
>
> I would add the following 2 sentences:
>
> "This way, one can make sure that addresses are only adjusted when
> necessary.
> In case of LAM, this avoids unnecessary parsing of the /proc/<pid>/status file
> to
> get the untag mask."
>
> Is the purpose more clear now?
>
It is, thanks.
Felix
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Sean Fennelly, Jeffrey Schneiderman, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2024-05-22 13:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 7:47 [PATCH 0/3] Add amd64 LAM watchpoint support Schimpe, Christina
2024-03-27 7:47 ` [PATCH 1/3] gdb: Make tagged pointer support configurable Schimpe, Christina
2024-03-28 11:58 ` Luis Machado
2024-04-04 8:18 ` Schimpe, Christina
2024-04-04 8:50 ` Luis Machado
2024-04-24 11:10 ` Willgerodt, Felix
2024-05-17 13:40 ` Schimpe, Christina
2024-05-22 13:37 ` Willgerodt, Felix [this message]
2024-03-27 7:47 ` [PATCH 2/3] LAM: Enable tagged pointer support for watchpoints Schimpe, Christina
2024-03-27 12:37 ` Eli Zaretskii
2024-03-28 12:50 ` Luis Machado
2024-04-24 11:11 ` Willgerodt, Felix
2024-05-17 14:05 ` Schimpe, Christina
2024-05-22 13:37 ` Willgerodt, Felix
2024-05-22 15:17 ` Schimpe, Christina
2024-03-27 7:47 ` [PATCH 3/3] LAM: Support kernel space debugging Schimpe, Christina
2024-04-24 11:11 ` Willgerodt, Felix
2024-05-17 14:07 ` Schimpe, Christina
2024-06-03 16:37 ` [PING][PATCH " Schimpe, Christina
2024-04-15 11:26 ` [PING][PATCH 0/3] Add amd64 LAM watchpoint support Schimpe, Christina
2024-04-22 7:17 ` [PING*2][PATCH " Schimpe, 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=MN2PR11MB456698D2D3B9987E6E9CC61D8EEB2@MN2PR11MB4566.namprd11.prod.outlook.com \
--to=felix.willgerodt@intel.com \
--cc=christina.schimpe@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).