This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] [AArch64 Linux] Get rid of top byte from tagged address
- From: Pedro Alves <palves at redhat dot com>
- To: Yao Qi <qiyaoltc at gmail dot com>, gdb-patches at sourceware dot org
- Date: Thu, 19 Oct 2017 12:21:25 +0100
- Subject: Re: [PATCH] [AArch64 Linux] Get rid of top byte from tagged address
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx06.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx06.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=palves at redhat dot com
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 8F4023C29
- References: <1508400527-20718-1-git-send-email-yao.qi@linaro.org>
On 10/19/2017 09:08 AM, Yao Qi wrote:
> ARMv8 supports tagged address, that is, the top one byte in address
> is ignored. It is always enabled on aarch64-linux. The patch clear
> the top byte of the virtual address, at the point before GDB/GDBserver
> pass the address to /proc or ptrace syscall. The top byte of address is
> still retained in the rest of GDB, because these bits can be used by
> different applications in different ways. That is reason I didn't
> implement gdbarch method addr_bits_remove to get rid of them.
Something else that came to mind -- do we need to make GDB's
stack/code caches aware of this? I.e., for the case of
writing through a tagged address and reading via a non-tagged
address, and vice-versa.
Thanks,
Pedro Alves