Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jiong Wang <jiong.wang@foss.arm.com>
Cc: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: [AArch64][1/6] Add new "pauth" feature and native support
Date: Wed, 09 Aug 2017 16:09:00 -0000	[thread overview]
Message-ID: <83o9rosoyw.fsf@gnu.org> (raw)
In-Reply-To: <21a7c0c7-45a0-6059-789f-d68e4cd03d37@foss.arm.com> (message from	Jiong Wang on Wed, 9 Aug 2017 13:21:33 +0100)

> From: Jiong Wang <jiong.wang@foss.arm.com>
> Date: Wed, 9 Aug 2017 13:21:33 +0100
> 
> This patch teach GDB to return the new ARMv8.3-A Pointer Authentication feature
> description when there is related support.
> 
>    * A new "pauth" feature description file is added.
>      The new pointer authentication feature, "pauth", contains two virtual
>      registers, "pauth_dmask" and "pauth_cmask".  Their values are supplied by
>      kernel to GDB through ptrace interface.  They are masks to indicate which
>      bits will be signature when data pointer or code pointer is signed.  Those
>      bits will be set to "1" in the mask.
> 
>    * HWCAP is used to detect whether the hardware support exists.
>      Currently we only support return address signing with A key, so using ptrace
>      trial read would not be reliable as it will return successfully when other
>      keys are used inside kernel.
> 
> The change on include/elf/common.h needs approval from Binutils maintainers.
> 
> gdb/
> 2017-08-09  Jiong Wang<jiong.wang@arm.com>
>              Yao Qi<yao.qi@linaro.org>
> 
> 	* aarch64-linux-nat.c (fetch_pauth_masks_from_thread): New
> 	function.
> 	(aarch64_linux_fetch_inferior_registers): Support pauth
> 	description.
> 	(aarch64_linux_read_description): Likewise.
> 	* aarch64-tdep.c: #include "features/aarch64-pauth.c".
> 	(aarch64_pauth_register_names): New register names array for
> 	pauth.
> 	(aarch64_cannot_store_register): New function.
> 	(aarch64_tdep_has_pauth_p): New function.
> 	(aarch64_gdbarch_init): Handle pauth description.  Initialize
> 	the optional "regnum" field.  Register cannot_store_register hook.
> 	(_initialize_aarch64_tdep): Call initialize_tdesc_aarch64_pauth.
> 	* aarch64-tdep.h (struct aarch64_optional_regnum): New structure
> 	type.
> 	(struct gdbarch_tdep) <regnum>: New field.
>   	(tdesc_aarch64_pauth): New variable declaration.
> 	(aarch64_tdep_has_pauth_p): New function declaration.
> 	* nat/aarch64-linux.c: Include <sys/auxv.h>.
> 	(aarch64_host_hwcap): New function.
> 	* nat/aarch64-linux.h (HWCAP_APIA): New macro.
> 	(aarch64_host_hwcap): New function declaration.
> 	* features/Makefile (WHICH): Add aarch64-pauth.
> 	(XMLTOC): Add aarch64-pauth.xml.
> 	* features/aarch64-pauth-core.xml: New file.
> 	* features/aarch64-pauth.c: Generated.
> 	* features/aarch64-pauth.xml: New file.
> 	* regformats/aarch64-pauth.dat: Generated.
> 
> include/
> 	* elf/common.h (NT_ARM_PAC_MASK): New.
> 
> gdb/doc/
> 	* gdb.texinfo (AArch64 Features): New feature
> 	"org.gnu.gdb.aarch64.pauth".

Thanks, the patch for gdb.texinfo is approved.


  reply	other threads:[~2017-08-09 16:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-09 12:21 Jiong Wang
2017-08-09 16:09 ` Eli Zaretskii [this message]
2017-08-09 16:19 ` Nick Clifton

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=83o9rosoyw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jiong.wang@foss.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