From: Heiko Carstens <hca@linux.ibm.com>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Shuah Khan <shuah@kernel.org>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH 3/3] selftests: vDSO: chacha: Provide default definition of HWCAP_S390_VXRS
Date: Tue, 25 Mar 2025 08:18:40 +0100 [thread overview]
Message-ID: <20250325071840.7910A12-hca@linux.ibm.com> (raw)
In-Reply-To: <20250325074319-b478adcc-3e04-447f-81b5-c92741c91bfd@linutronix.de>
On Tue, Mar 25, 2025 at 07:48:48AM +0100, Thomas Weißschuh wrote:
> On Mon, Mar 24, 2025 at 04:55:13PM +0100, Heiko Carstens wrote:
> > On Mon, Mar 24, 2025 at 03:03:17PM +0100, Thomas Weißschuh wrote:
> > > s390 does not provide a hwcap.h UAPI header.
> > >
> > > Add an inline definition for the constant HWCAP_S390_VXRS until a proper
> > > UAPI header is introduced.
> > >
> > > Fixes: 210860e7f733 ("selftests: vDSO: check cpu caps before running chacha test")
> > > Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
> > > ---
> > > tools/testing/selftests/vDSO/vdso_test_chacha.c | 3 +++
> > > 1 file changed, 3 insertions(+)
...
> > > #elif defined(__s390x__)
> > > +#ifndef HWCAP_S390_VXRS
> > > +#define HWCAP_S390_VXRS (1 << 11)
> > > +#endif
> > > static bool cpu_has_capabilities(void)
> > > {
> > > return getauxval(AT_HWCAP) & HWCAP_S390_VXRS;
> >
> > How did this cause a problem?
> >
> > Did you use something different than glibc(-devel) on your test
> > system? Just wondering since glibc-devel provides the define since
> > ages and is also required for getauxval().
>
> I used nolibc (from the kernel tree at tools/include/nolibc/) to make cross
> platform usage of the tests easier. See also [0].
> I got confused by the existence of hwcap.h in the kernel UAPI headers for
> various architectures and didn't check the libc headers.
> So this isn't really a bug right now, and the hwcap changes will only really be
> necessary once my other work goes upstream.
Thanks for explaining!
Acked-by: Heiko Carstens <hca@linux.ibm.com>
next prev parent reply other threads:[~2025-03-25 7:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 14:03 [PATCH 0/3] selftests: vDSO: chacha: Bugfixes Thomas Weißschuh
2025-03-24 14:03 ` [PATCH 1/3] selftests: vDSO: chacha: Correctly skip test if necessary Thomas Weißschuh
2025-03-24 14:03 ` [PATCH 2/3] selftests: vDSO: chacha: Include asm/hwcap.h for arm64 Thomas Weißschuh
2025-03-24 14:03 ` [PATCH 3/3] selftests: vDSO: chacha: Provide default definition of HWCAP_S390_VXRS Thomas Weißschuh
2025-03-24 15:55 ` Heiko Carstens
2025-03-25 6:48 ` Thomas Weißschuh
2025-03-25 7:18 ` Heiko Carstens [this message]
2025-03-25 10:54 ` Thomas Weißschuh
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=20250325071840.7910A12-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=Jason@zx2c4.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tglx@linutronix.de \
--cc=thomas.weissschuh@linutronix.de \
--cc=vincenzo.frascino@arm.com \
/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