From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: nd@arm.com, qemu-devel@nongnu.org
Subject: Re: tst-arm-mte bug: PSTATE.TCO is cleared on exceptions
Date: Wed, 6 May 2020 13:57:09 +0100 [thread overview]
Message-ID: <20200506125709.GK23080@arm.com> (raw)
In-Reply-To: <ec85fd40-229b-c965-1f58-d4cbe825419c@linaro.org>
The 04/24/2020 12:47, Richard Henderson wrote:
> On 4/21/20 9:39 PM, Richard Henderson wrote:
> > Yep. I failed to update aarch64_pstate_valid_mask for TCO.
> > Will fix. Thanks,
>
> Fixed on the branch.
>
> I still need to work out how best to plumb the arm,armv8.5-memtag property so
> the devel/mte-v3 kernel branch isn't usable as-is for the moment. For myself,
> I've just commented that test out for now.
The fix worked well thanks (in linux devel/mte-v3 i
reverted the patch that introduced arm,armv8.5-memtag)
However later on during testing malloc with PROT_MTE
i got a qemu assert failure:
Bail out! ERROR:/S/target/arm/mte_helper.c:97:allocation_tag_mem: assertion failed: (tag_size <= in_page)
i can reproduce it, but i don't know how to debug it
further, i don't know what the application is doing
when this happens, nor what the kernel is doing.
i rebuilt qemu with --enable-debug but now it's very
slow (still booting into linux 3h later).
let me know if there are ways to narrow this down.
next prev parent reply other threads:[~2020-05-06 13:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 10:29 tst-arm-mte bug: PSTATE.TCO is cleared on exceptions Szabolcs Nagy
2020-04-22 4:39 ` Richard Henderson
2020-04-24 19:47 ` Richard Henderson
2020-05-06 12:57 ` Szabolcs Nagy [this message]
2020-05-07 9:59 ` Szabolcs Nagy
2020-05-07 17:21 ` Richard Henderson
2020-05-18 12:59 ` Szabolcs Nagy
2020-05-19 18:46 ` Richard Henderson
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=20200506125709.GK23080@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=nd@arm.com \
--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).