qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@arm.com>
To: "Richard Henderson" <richard.henderson@linaro.org>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [PATCH 09/11] tests/tcg: disable pauth for aarch64 gdb tests
Date: Tue, 14 Mar 2023 08:20:42 +0000	[thread overview]
Message-ID: <a777850f-0551-9b5d-2f09-0a94c9d51a63@arm.com> (raw)
In-Reply-To: <29307e46-00f1-9e02-94a3-de8b4a399ada@linaro.org>

On 3/13/23 19:21, Richard Henderson wrote:
> On 3/13/23 04:44, Luis Machado wrote:
>>> Luis: I think that rather than doing (2) with a QEMU namespace,
>>> we should define a gdb namespace for this. That makes it clear
>>> that this is still a gdb-upstream-sanctioned way of exposing
>>> the pauth registers.
>>
>> That should be fine as well, and would work to side-step the gdb 12 bug so it doesn't crash.
>>
>> We could name the feature "org.gnu.gdb.aarch64.pauth_v2" or somesuch, and slowly stop using the original
>> "org.gnu.gdb.aarch64.pauth" feature. I can document the requirements for a compliant pauth_v2.
>
> What if we leave the original two registers, pauth_[cd]mask, in org.gnu.gdb.aarch64.pauth and move the new *_high registers into a different feature?  That would maximize the set of gdb version for which the original user-only support is functional.

 From what I recall from the gdb bug, I don't think that will help. gdb will detect pauth support, will add the ra_sign_state pseudo-register internally with the incorrect numbering and will also see the additional system registers from QEMU, resulting in a crash.

>
>
> r~
>

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.


  parent reply	other threads:[~2023-03-14  8:22 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10 10:31 [PATCH 00/11] tweaks and fixes for 8.0-rc1 (tests, plugins, docs) Alex Bennée
2023-03-10 10:31 ` [PATCH 01/11] tests/avocado: update AArch64 tests to Alpine 3.17.2 Alex Bennée
2023-03-10 10:31 ` [PATCH 02/11] tests/docker: all add DOCKER_BUILDKIT to RUNC environment Alex Bennée
2023-03-10 10:31 ` [PATCH 03/11] scripts/ci: add libslirp-devel to build-environment Alex Bennée
2023-03-10 10:31 ` [PATCH 04/11] scripts/ci: update gitlab-runner playbook to handle CentOS Alex Bennée
2023-03-10 10:31 ` [PATCH 05/11] gitlab: update centos-8-stream job Alex Bennée
2023-03-10 10:31 ` [PATCH 06/11] include/qemu: add documentation for memory callbacks Alex Bennée
2023-03-10 10:31 ` [PATCH 07/11] tcg: Clear plugin_mem_cbs on TB exit Alex Bennée
2023-03-10 17:39   ` Richard Henderson
2023-03-10 17:41     ` Richard Henderson
2023-03-10 17:56       ` Alex Bennée
2023-03-10 17:59         ` Richard Henderson
2023-03-10 10:31 ` [PATCH 08/11] tests/tcg: add some help output for running individual tests Alex Bennée
2023-03-10 10:31 ` [PATCH 09/11] tests/tcg: disable pauth for aarch64 gdb tests Alex Bennée
2023-03-10 17:44   ` Richard Henderson
2023-03-10 17:47   ` Peter Maydell
2023-03-10 18:00     ` Fabiano Rosas
2023-03-10 18:07       ` Peter Maydell
2023-03-10 18:15         ` Fabiano Rosas
2023-03-13 11:16         ` Luis Machado
2023-03-10 18:14       ` Alex Bennée
2023-03-13 11:22         ` Peter Maydell
2023-03-13 11:44           ` Luis Machado
2023-03-13 19:21             ` Richard Henderson
2023-03-13 21:35               ` Peter Maydell
2023-03-14  8:20               ` Luis Machado [this message]
2023-03-15  9:50             ` Luis Machado
2023-03-17 16:37               ` Peter Maydell
2023-03-17 16:55                 ` Luis Machado
2023-03-17 17:07                   ` Peter Maydell
2023-03-17 17:12                     ` Luis Machado
2023-03-17 17:16                       ` Luis Machado
2023-03-10 18:07     ` Richard Henderson
2023-03-10 10:31 ` [PATCH 10/11] include/exec: fix kerneldoc definition Alex Bennée
2023-03-10 12:38   ` Philippe Mathieu-Daudé
2023-03-13 17:00   ` Thomas Huth
2023-03-13 17:03     ` Peter Maydell
2023-03-13 17:14       ` Thomas Huth
2023-03-13 17:30         ` Peter Maydell
2023-03-13 18:08           ` Peter Maydell
2023-03-10 10:31 ` [PATCH 11/11] tests/avocado: don't use tags to define drive Alex Bennée
2023-03-10 11:04   ` David Woodhouse
2023-03-10 12:42   ` Philippe Mathieu-Daudé

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=a777850f-0551-9b5d-2f09-0a94c9d51a63@arm.com \
    --to=luis.machado@arm.com \
    --cc=alex.bennee@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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;
as well as URLs for NNTP newsgroup(s).