From: Mark Brown <broonie@kernel.org>
To: "misono.tomohiro@fujitsu.com" <misono.tomohiro@fujitsu.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Shuah Khan <shuah@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH v1 4/4] selftests: arm64: Verify that all possible vector lengths are handled
Date: Fri, 17 Sep 2021 13:01:03 +0100 [thread overview]
Message-ID: <20210917120103.GA4700@sirena.org.uk> (raw)
In-Reply-To: <TYCPR01MB69937F4D2E0C9542ADB18194E5DD9@TYCPR01MB6993.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 514 bytes --]
On Fri, Sep 17, 2021 at 09:27:04AM +0000, misono.tomohiro@fujitsu.com wrote:
> Actually I tried to run these sve tests update on A64FX and got the above error:
> # # SVE VL 48 returned 32 test logic failure
> but returning 32 is expected behavior as A64FX's supported VL lens are 16, 32, 64.
Right, I see. That's not triggering on the virtual platforms since they
just support all the VLs. Your fix looks right, it was supposed to be
an assert in case of logic failures but that doesn't actually work out.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: "misono.tomohiro@fujitsu.com" <misono.tomohiro@fujitsu.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Shuah Khan <shuah@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH v1 4/4] selftests: arm64: Verify that all possible vector lengths are handled
Date: Fri, 17 Sep 2021 13:01:03 +0100 [thread overview]
Message-ID: <20210917120103.GA4700@sirena.org.uk> (raw)
In-Reply-To: <TYCPR01MB69937F4D2E0C9542ADB18194E5DD9@TYCPR01MB6993.jpnprd01.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 514 bytes --]
On Fri, Sep 17, 2021 at 09:27:04AM +0000, misono.tomohiro@fujitsu.com wrote:
> Actually I tried to run these sve tests update on A64FX and got the above error:
> # # SVE VL 48 returned 32 test logic failure
> but returning 32 is expected behavior as A64FX's supported VL lens are 16, 32, 64.
Right, I see. That's not triggering on the virtual platforms since they
just support all the VLs. Your fix looks right, it was supposed to be
an assert in case of logic failures but that doesn't actually work out.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-09-17 12:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 12:37 [PATCH v1 0/4] selftests: arm64: vec-syscfg updates Mark Brown
2021-09-13 12:37 ` Mark Brown
2021-09-13 12:37 ` [PATCH v1 1/4] selftests: arm64: Fix printf() format mismatch in vec-syscfg Mark Brown
2021-09-13 12:37 ` Mark Brown
2021-09-13 12:37 ` [PATCH v1 2/4] selftests: arm64: Remove bogus error check on writing to files Mark Brown
2021-09-13 12:37 ` Mark Brown
2021-09-13 12:37 ` [PATCH v1 3/4] selftests: arm64: Fix and enable test for setting current VL in vec-syscfg Mark Brown
2021-09-13 12:37 ` Mark Brown
2021-09-13 12:37 ` [PATCH v1 4/4] selftests: arm64: Verify that all possible vector lengths are handled Mark Brown
2021-09-13 12:37 ` Mark Brown
2021-09-17 9:27 ` misono.tomohiro
2021-09-17 9:27 ` misono.tomohiro
2021-09-17 12:01 ` Mark Brown [this message]
2021-09-17 12:01 ` Mark Brown
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=20210917120103.GA4700@sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=misono.tomohiro@fujitsu.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.