From: Alan Hayward <Alan.Hayward@arm.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: nd <nd@arm.com>
Subject: [PING][PATCH v2 0/3] Core file support for Aarch64 SVE
Date: Mon, 06 Aug 2018 10:10:00 -0000 [thread overview]
Message-ID: <4D090DA4-79B9-4212-B7A7-19D95D0E8DA2@arm.com> (raw)
In-Reply-To: <20180730092528.98739-1-alan.hayward@arm.com>
Ping.
> On 30 Jul 2018, at 10:25, Alan Hayward <Alan.Hayward@arm.com> wrote:
>
> Support both the reading and writing of core files on aarch64 SVE.
>
> SVE core files are doumented here:
> https://github.com/torvalds/linux/blob/master/Documentation/arm64/sve.txt
> * A NT_ARM_SVE note will be added to each coredump for each thread of the
> dumped process. The contents will be equivalent to the data that would have
> been read if a PTRACE_GETREGSET of NT_ARM_SVE were executed for each thread
> when the coredump was generated.
>
> The first patch adds support allowing writing of core files for targets with
> variable length core files. Currently all targets with variable length core
> files do not allow the creation of core files.
>
> The second patch detects SVE state in a core file.
> The final patch adds the supply/collect functions for core file parsing.
>
> Checked with make check on x86 (all targets) and aarch64.
> Generated core files on SVE emulator both from gdb "generate-core-file"
> command and a segfault. Loaded these back into gdb.
>
>
> Alan Hayward (3):
> Add min size to regset section iterations
> Detect SVE when reading aarch64 core files
> Parse SVE registers in aarch64 core file reading/writing
>
> gdb/aarch64-fbsd-tdep.c | 8 +-
> gdb/aarch64-linux-tdep.c | 190 +++++++++++++++++++++++++++++++++++++++++++++--
> gdb/alpha-linux-tdep.c | 4 +-
> gdb/alpha-nbsd-tdep.c | 6 +-
> gdb/amd64-fbsd-tdep.c | 8 +-
> gdb/amd64-linux-tdep.c | 6 +-
> gdb/arm-bsd-tdep.c | 6 +-
> gdb/arm-fbsd-tdep.c | 7 +-
> gdb/arm-linux-tdep.c | 11 +--
> gdb/corelow.c | 27 ++++---
> gdb/fbsd-tdep.c | 2 +-
> gdb/frv-linux-tdep.c | 8 +-
> gdb/gdbarch.h | 2 +-
> gdb/gdbarch.sh | 2 +-
> gdb/hppa-linux-tdep.c | 6 +-
> gdb/hppa-nbsd-tdep.c | 3 +-
> gdb/hppa-obsd-tdep.c | 6 +-
> gdb/i386-fbsd-tdep.c | 11 ++-
> gdb/i386-linux-tdep.c | 9 ++-
> gdb/i386-tdep.c | 6 +-
> gdb/ia64-linux-tdep.c | 6 +-
> gdb/linux-tdep.c | 2 +-
> gdb/m32r-linux-tdep.c | 3 +-
> gdb/m68k-bsd-tdep.c | 6 +-
> gdb/m68k-linux-tdep.c | 6 +-
> gdb/mips-fbsd-tdep.c | 8 +-
> gdb/mips-linux-tdep.c | 14 ++--
> gdb/mips-nbsd-tdep.c | 8 +-
> gdb/mips64-obsd-tdep.c | 3 +-
> gdb/mn10300-linux-tdep.c | 8 +-
> gdb/nios2-linux-tdep.c | 3 +-
> gdb/ppc-fbsd-tdep.c | 6 +-
> gdb/ppc-linux-tdep.c | 12 +--
> gdb/ppc-nbsd-tdep.c | 4 +-
> gdb/ppc-obsd-tdep.c | 2 +-
> gdb/regcache.h | 8 ++
> gdb/rs6000-aix-tdep.c | 4 +-
> gdb/s390-linux-tdep.c | 23 +++---
> gdb/score-tdep.c | 4 +-
> gdb/sh-tdep.c | 6 +-
> gdb/sparc-tdep.c | 6 +-
> gdb/tilegx-linux-tdep.c | 4 +-
> gdb/vax-tdep.c | 2 +-
> gdb/xtensa-tdep.c | 4 +-
> 44 files changed, 350 insertions(+), 130 deletions(-)
>
> --
> 2.15.2 (Apple Git-101.1)
>
prev parent reply other threads:[~2018-08-06 10:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 9:26 [PATCH " Alan Hayward
2018-07-30 9:25 ` [PATCH v2 2/3] Detect SVE when reading aarch64 core files Alan Hayward
2018-08-06 18:28 ` Simon Marchi
2018-07-30 9:26 ` [PATCH v2 3/3] Parse SVE registers in aarch64 core file reading/writing Alan Hayward
2018-08-06 18:29 ` Simon Marchi
2018-07-30 9:26 ` [PATCH v2 1/3] Add min size to regset section iterations Alan Hayward
2018-08-06 18:27 ` Simon Marchi
2018-08-07 11:01 ` Alan Hayward
2018-08-07 16:05 ` Simon Marchi
2018-08-08 8:19 ` Alan Hayward
2018-08-08 13:34 ` Simon Marchi
2018-08-09 18:29 ` Simon Marchi
2018-08-09 18:53 ` Simon Marchi
2018-08-06 10:10 ` Alan Hayward [this message]
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=4D090DA4-79B9-4212-B7A7-19D95D0E8DA2@arm.com \
--to=alan.hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.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