Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis <luis.machado.foss@gmail.com>
To: Matthieu Longo <matthieu.longo@arm.com>,
	srinath.parvathaneni@arm.com, gdb-patches@sourceware.org
Cc: guinevere@redhat.com, thiago.bauermann@linaro.org
Subject: Re: [PATCH v1] gdb/aarch64: Add support for FEAT_S1POE POR_EL0 register
Date: Sun, 21 Jun 2026 12:32:40 +0100	[thread overview]
Message-ID: <47582751-6fc5-47f3-8799-2db6dd2809a1@gmail.com> (raw)
In-Reply-To: <1d26b2c8-d8d1-486f-b2fc-8bd2ca1f2d05@arm.com>

On 18/06/2026 18:04, Matthieu Longo wrote:
>> +  user_poe user_poe;
>> +  iovec iovec;
>> +
>> +  iovec.iov_base = &user_poe;
>> +  iovec.iov_len = sizeof (user_poe);
>> +
>> +  int tid = get_ptrace_pid (regcache->ptid ());
> 
> * Question for maintainers: *
> 
> It seems that there are different methods to get the thread ID.
> I observed in the same file 3 different ways:
> - int tid = get_ptrace_pid (inferior_ptid);
> - int tid = regcache->ptid ().lwp ();
> - int tid = get_ptrace_pid (regcache->ptid ());
> 
> What is the "correct" method ?
> 

get_ptrace_pid here.

> 
> * Question for maintainers: *
> 
> All the architectural tests are already in the same directory, so moving 
> them inside subdirectories (one per architecture) is out of scope of 
> this patch.
> However, would it make sense to do it in a separate patch ?
> This directory starts getting very messy.
> 

Seems like a worthwhile refactor, but I'm not sure off the top of my 
head how the current makefile infra will handle it. If we decide to run 
gdb.arch tests, will it run gdb.arch/aarch64/*.exp?

I'm all for keeping things clean, but it needs to make it simple as well.

Thanks for the reviews by the way.

  reply	other threads:[~2026-06-21 11:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-17 17:00 srinath.parvathaneni
2026-06-17 23:38 ` Ezra Sitorus
2026-06-18 17:04 ` Matthieu Longo
2026-06-21 11:32   ` Luis [this message]
2026-06-21 11:50 ` Luis

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=47582751-6fc5-47f3-8799-2db6dd2809a1@gmail.com \
    --to=luis.machado.foss@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=guinevere@redhat.com \
    --cc=matthieu.longo@arm.com \
    --cc=srinath.parvathaneni@arm.com \
    --cc=thiago.bauermann@linaro.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