From: Cornelia Huck <cohuck@redhat.com>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Shuah Khan <shuah@kernel.org>,
Joey Gouly <joey.gouly@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org
Subject: Re: [ARM64] status of MTE selftests?
Date: Mon, 09 May 2022 16:59:32 +0200 [thread overview]
Message-ID: <87ee124uqz.fsf@redhat.com> (raw)
In-Reply-To: <87levb3u1s.fsf@redhat.com>
On Mon, May 09 2022, Cornelia Huck <cohuck@redhat.com> wrote:
> On Fri, May 06 2022, Mark Brown <broonie@kernel.org> wrote:
>
>> On Fri, May 06, 2022 at 04:50:41PM +0200, Cornelia Huck wrote:
>>
>>> I'm currently trying to run the MTE selftests on the FVP simulator (Base
>>> Model)[1], mainly to verify things are sane on the host before wiring up
>>> the KVM support in QEMU. However, I'm seeing some failures (the non-mte
>>> tests seemed all fine):
>>
>>> Are the MTE tests supposed to work on the FVP model? Something broken in
>>> my config? Anything I can debug?
>>
>> I would expect them to work, they seemed happy when I was doing
>> the async mode support IIRC and a quick spin with -next in qemu
>> everything seems fine, I'm travelling so don't have the
>> environment for models to hand right now.
>
> Thanks; I think that points to some setup/config problem on my side,
> then :/ (I ran the selftests under QEMU's tcg emulation, and while it
> looks better, I still get timeouts for check_gcr_el1_cswitch and
> check_user_mem.)
...so these two tests are simply very slow; if I run them directly, they
take longer than 45s, but eventually finish. So all seems good (in a
slow way) on QEMU + tcg.
On the simulator, running check_gcr_el1_cswitch directly finishes
successfully after several minutes as well; however, I get all the other
failures in tests that I reported in my first mail even when I run them
directly.
next prev parent reply other threads:[~2022-05-09 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87wney4svy.fsf@redhat.com>
2022-05-06 15:09 ` [ARM64] status of MTE selftests? Cornelia Huck
2022-05-06 16:32 ` Mark Brown
2022-05-09 9:59 ` Cornelia Huck
2022-05-09 14:59 ` Cornelia Huck [this message]
2022-05-09 15:18 ` Mark Brown
2022-05-09 15:40 ` Cornelia Huck
2022-05-11 12:48 ` Mark Brown
2022-05-11 13:15 ` Cornelia Huck
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=87ee124uqz.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=will@kernel.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