public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Gustavo Romero <gromero@linux.vnet.ibm.com>
To: Mark Wielaard <mark@klomp.org>
Cc: elfutils-devel@sourceware.org
Subject: Re: [PATCH] ppc64: Add HTM SPRs support to readelf
Date: Mon, 24 Jul 2017 14:54:00 -0000	[thread overview]
Message-ID: <59760A2A.30606@linux.vnet.ibm.com> (raw)
In-Reply-To: <1500666946.14595.485.camel@klomp.org>

Hi Mark,

On 21-07-2017 16:55, Mark Wielaard wrote:
> On Thu, 2017-07-20 at 17:49 -0400, Gustavo Romero wrote:
>> Since POWER8, PowerPC 64 supports Hardware Transactional Memory, which has
>> three special purpose registers associated to it: tfhar, tfiar, and texasr.
>> This commit add HTM SPRs set as known note type so it's possible to use
>> 'readelf --notes' to inspect the HTM SPRs in a coredump file generated in
>> such a machines.
> 
> This patch looks perfect, thanks.

Thanks for reviewing it!


> 
> We normally keep elf.h in sync with glibc.
> Could you submit this elf.h change to libc-alpha@sourceware.org?
> Then we resync elf.h from glibc to pull in the new constants.

It looks like glibc community won't review / push that change as it is in
freeze for glibc 2.26 cut right now accordingly to [1].

If my understanding is correct, it's a blocker or my change can be pushed
to elfutils and once glibc is open again (in about a week) I can submit
this elf.h change to libc-alpha@sourceware.org?


Thank you and best regards,
Gustavo

[1] https://sourceware.org/ml/libc-alpha/2017-07/msg00018.htm

  reply	other threads:[~2017-07-24 14:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-20 21:49 Gustavo Romero
2017-07-21 19:55 ` Mark Wielaard
2017-07-24 14:54   ` Gustavo Romero [this message]
2017-07-24 19:17     ` Mark Wielaard
2017-07-24 20:47       ` Gustavo Romero
2017-07-24 20:50         ` Gustavo Romero
2017-07-25 10:34           ` Mark Wielaard
2017-08-15 14:25             ` Gustavo Romero
2017-08-15 20:51               ` Mark Wielaard

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=59760A2A.30606@linux.vnet.ibm.com \
    --to=gromero@linux.vnet.ibm.com \
    --cc=elfutils-devel@sourceware.org \
    --cc=mark@klomp.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).