From: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
To: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Cc: uweigand@de.ibm.com, edjunior@gmail.com
Subject: Re: [PATCH v4 12/12] [PowerPC] Add support for HTM registers
Date: Thu, 16 Aug 2018 23:47:00 -0000 [thread overview]
Message-ID: <87mutlj2m3.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <87d0uixe1b.fsf@linux.vnet.ibm.com>
Pedro Franco de Carvalho <pedromfc@linux.ibm.com> writes:
> Pedro Franco de Carvalho <pedromfc@linux.ibm.com> writes:
>
>> Pedro Alves <palves@redhat.com> writes:
>>
>>> I won't pretend to understand the above fully (not an Power expert),
>>> but the question I ended up with was, after all this, will the
>>> GDB-generated files end up looking like kernel-generated cores?
>>> Or are there plans for that?
>>
>> They will end up looking different for this regset note section. This
>> really seems like a kernel bug, which I'm hoping will get fixed.
>
> Correction: the size of the regset note section for 32-bit threads seems
> like a kernel bug. The fact that the kernel includes values for
> registers that GDB doesn't include in the note section (by zeroing them)
> isn't a kernel bug, but to do this GDB would have to be aware of all
> these registers that aren't defined in the architecture.
>
> --
> Pedro Franco de Carvalho
Does this issue block the patches?
I could add the registers to GDB but it would be messy, since it would
require a linux-specific target description with these extra registers.
Alternatively, I can make GDB not generate this specific note section,
this is a simple change in the current patches. The only confusing
thing is that when reading back the core file through GDB the
checkpointed GPRs will show up as unavailable, even if the thread was in
the middle of a transaction when the core file was generated, while all
the other checkpointed registers will be available.
Thanks!!
--
Pedro Franco de Carvalho
next prev parent reply other threads:[~2018-08-16 23:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 0:07 [PATCH v4 00/12] GDB support for more powerpc registers on linux Pedro Franco de Carvalho
2018-08-15 0:07 ` [PATCH v4 04/12] [PowerPC] Remove rs6000_pseudo_register_reggroup_p Pedro Franco de Carvalho
2018-08-15 0:07 ` [PATCH v4 05/12] [PowerPC] Fix two if statements in gdb/ppc-linux-nat.c Pedro Franco de Carvalho
2018-08-15 0:07 ` [PATCH v4 06/12] [PowerPC] Fix indentation in arch/ppc-linux-common.c Pedro Franco de Carvalho
2018-08-15 0:07 ` [PATCH v4 03/12] Add decfloat registers to float reggroup Pedro Franco de Carvalho
2018-08-15 0:07 ` [PATCH v4 11/12] [PowerPC] Reject tdescs with VSX and no FPU or Altivec Pedro Franco de Carvalho
2018-08-15 0:07 ` [PATCH v4 09/12] [PowerPC] Add support for TAR Pedro Franco de Carvalho
2018-08-15 0:07 ` [PATCH v4 01/12] Zero-initialize linux note sections Pedro Franco de Carvalho
2018-08-15 0:07 ` [PATCH v4 10/12] [PowerPC] Add support for EBB and PMU registers Pedro Franco de Carvalho
2018-08-16 16:51 ` Pedro Alves
2018-08-16 18:16 ` Pedro Franco de Carvalho
2018-08-15 0:07 ` [PATCH v4 07/12] [PowerPC] Refactor have_ initializers in rs6000-tdep.c Pedro Franco de Carvalho
2018-08-15 0:07 ` [PATCH v4 02/12] [PowerPC] Don't zero-initialize vector register buffers Pedro Franco de Carvalho
2018-08-15 0:55 ` [PATCH v4 12/12] [PowerPC] Add support for HTM registers Pedro Franco de Carvalho
2018-08-16 16:53 ` Pedro Alves
2018-08-16 17:50 ` Pedro Franco de Carvalho
2018-08-16 20:16 ` Pedro Franco de Carvalho
2018-08-16 23:47 ` Pedro Franco de Carvalho [this message]
2018-08-17 18:11 ` Pedro Alves
2018-08-17 19:25 ` Pedro Franco de Carvalho
2018-08-15 1:16 ` [PATCH v4 08/12] [PowerPC] Add support for PPR and DSCR Pedro Franco de Carvalho
2018-08-16 16:46 ` [PATCH v4 00/12] GDB support for more powerpc registers on linux Pedro Franco de Carvalho
2018-08-16 17:00 ` Pedro Alves
2018-08-16 17:42 ` Pedro Franco de Carvalho
2018-08-16 18:02 ` Eli Zaretskii
2018-08-16 18:08 ` Pedro Franco de Carvalho
2018-08-16 18:45 ` Eli Zaretskii
2018-08-16 19:23 ` Pedro Franco de Carvalho
2018-10-08 19:09 ` ping: " Jan Kratochvil
2018-10-08 19:32 ` Pedro Franco de Carvalho
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=87mutlj2m3.fsf@linux.vnet.ibm.com \
--to=pedromfc@linux.ibm.com \
--cc=edjunior@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=uweigand@de.ibm.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