Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org, Ulrich Weigand <uweigand@de.ibm.com>
Subject: Re: [RFA/RFT PATCH 0/3] Add TDB regset support
Date: Fri, 07 Jun 2013 15:03:00 -0000	[thread overview]
Message-ID: <51B1F629.5070006@redhat.com> (raw)
In-Reply-To: <87fvwu5937.fsf@br87z6lw.de.ibm.com>

On 06/07/2013 02:44 PM, Andreas Arnez wrote:
> The new z/Architecture introduces restricted hardware transactional
> memory with the "transactional-execution facility".  Diagnostic
> capabilities of this feature include the "program interruption
> transaction diagnostic block" (TDB), which is written by the hardware
> whenever a transaction is aborted due to a program interruption.
> 
> This patch set makes the TDB accessible from GDB as a new register set.
> The first patch reworks the S/390 register map handling without any
> functional changes, the second adds the new TDB register set, and the
> third implements "dynamic regset" support.
> 
> The third patch changes GDB's approach for enumerating core file
> register note sections: Instead of a static array, an iterator function
> is now provided by the target-dependent code.  This allows for
> dynamically selecting a register set for inclusion in a core file
> (written with gcore), and making the selection dependent on the current
> register values.  This is needed for correct treatment of the TDB
> register set, because its register values are unavailable when the
> inferior was interrupted outside transactions, and then the TDB should
> *not* be written into the core file.
> 
> This last patch affects multiple architectures, specifically:
> 
> - GNU/Linux ARM
> - GNU/Linux PowerPC
> - GNU/Linux S/390
> - GNU/Linux x86
> 
> In most cases the patch simplifies the target-dependent logic.  I've
> tested on S/390 and x86 and did not find any regressions.
> 

Why isn't this exposed as a new target description that includes the
new register set?

-- 
Pedro Alves


  parent reply	other threads:[~2013-06-07 15:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-07 13:44 Andreas Arnez
2013-06-07 13:50 ` [PATCH 1/3] S/390 regmap rework Andreas Arnez
2015-05-05 19:17   ` Regression on gdb.base/checkpoint.exp on S/390 (was: Re: [PATCH 1/3] S/390 regmap rework) Sergio Durigan Junior
2015-05-06 18:16     ` Regression on gdb.base/checkpoint.exp on S/390 Andreas Arnez
2013-06-07 13:51 ` [PATCH 2/3] Add TDB regset Andreas Arnez
2013-06-07 13:53 ` [PATCH 3/3] Dynamic core regset sections support Andreas Arnez
2013-06-07 14:43   ` Luis Machado
2013-06-07 16:40     ` Andreas Arnez
2013-06-07 15:03 ` Pedro Alves [this message]
2013-06-07 15:59   ` [RFA/RFT PATCH 0/3] Add TDB regset support Andreas Arnez
2013-06-07 16:44     ` Pedro Alves
2013-06-07 18:16       ` Andreas Arnez
2013-06-07 19:06         ` Pedro Alves
2013-06-10 16:59           ` Andreas Arnez
2013-06-11 10:48             ` Pedro Alves

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=51B1F629.5070006@redhat.com \
    --to=palves@redhat.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --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