Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alan Hayward <alan.hayward@arm.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH 0/8] AARCH64 SVE: Initial SVE support
Date: Mon, 05 Dec 2016 12:25:00 -0000	[thread overview]
Message-ID: <D46B0D3D.154CD%alan.hayward@arm.com> (raw)

Hi,

I'd like to submit GDB and gdbserver support for ARM's Scalable Vector
Extension (SVE).

For more details about the extension itself, please see Nigel's blog post
at:

  
https://community.arm.com/groups/processors/blog/2016/08/22/technology-upda
te-the-scalable-vector-extension-sve-for-the-armv8-a-architecture

Francesco has also written a white paper about programming for SVE,
with some worked examples:

  http://developer.arm.com/hpc/a-sneak-peek-into-sve-and-vla-programming

In order to support SVE, GDB needs to be able to handle registers which may
change size at any time whilst the debugged program is running. The target
architecture descriptions (patch 5) contain a minimum size for each
variable
register. GDB (patch 7) and gdbserver (patch 8) must then scale these
registers
using the current VG for the target (obtained using ptrace).
This also requires increasing the maximum register size to 256 bytes
(patch 1).

For these sets of patches to work, Linux Kernel support also needs adding,
which is currently under review here:
  
http://archive.arm.linux.org.uk/lurker/message/20161125.193848.bec98fed.en.
html
Without kernel support, the code will safely fall back to non-SVE Aarch64.

These patches assume the vector length the same across a process, which is
consistant with the current Kernel implementation. Once support is added to
the kernel for independent vector lengths per thread, then further patches
will be required to allow a different target descriptor for each thread.


Thanks,
Alan Hayward.



             reply	other threads:[~2016-12-05 12:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-05 12:25 Alan Hayward [this message]
2016-12-13 11:36 ` Yao Qi

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=D46B0D3D.154CD%alan.hayward@arm.com \
    --to=alan.hayward@arm.com \
    --cc=gdb-patches@sourceware.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