From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Xi Ruoyao <xry111@xry111.site>,
broonie@kernel.org
Subject: Re: [PATCH] selftests: vDSO: Do not rely on $ARCH for vdso_test_getrandom && vdso_test_chacha
Date: Mon, 2 Sep 2024 14:22:38 +0200 [thread overview]
Message-ID: <fe8ea6a6-71d7-4cfc-b20b-fa0a7f39a4be@csgroup.eu> (raw)
In-Reply-To: <ZtRqp-uZe5C07qOF@zx2c4.com>
Hi Jason,
Le 01/09/2024 à 15:22, Jason A. Donenfeld a écrit :
> Hi Christophe,
>
> Hmm, I'm not so sure I like this very much. I think it's important for
> these tests to fail when an arch tries to hook up the function to the
> vDSO, but it's still not exported for some reason. This also regresses
> the ARCH=x86_64 vs ARCH=x86 thing, which SRCARCH fixes.
>
If we take the exemple of getcpu:
Only powerpc and s390 implement __kernel_getcpu.
Until recently, it was implemented on ppc64 but not on ppc32
Only loongarch, riscv and x86 implement __vdso_getcpu.
Nevertheless, vdso_test_getcpu is always builts, regardless of the
architecture.
When vdso_test_getcpu doesn't find the vDSO entry point, it prints an
error text and returns KSFT_SKIP
I thought it would be more correct to have the same behaviour on
vdso_test_getrandom instead of trying to build it only when the
underlying kernel supports it.
Christophe
next prev parent reply other threads:[~2024-09-02 12:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-31 17:11 Christophe Leroy
2024-09-01 13:22 ` Jason A. Donenfeld
2024-09-01 18:00 ` Christophe Leroy
2024-09-01 18:02 ` Jason A. Donenfeld
2024-09-01 18:43 ` Christophe Leroy
2024-09-02 1:20 ` Jason A. Donenfeld
2024-09-02 12:39 ` LEROY Christophe
2024-09-02 12:43 ` Jason A. Donenfeld
2024-09-02 12:22 ` Christophe Leroy [this message]
2024-09-02 12:37 ` Mark Brown
2024-09-02 13:23 ` Christophe Leroy
2024-09-02 13:57 ` Jason A. Donenfeld
2024-09-02 14:18 ` Christophe Leroy
2024-09-02 14:23 ` Christophe Leroy
2024-11-07 8:40 ` Christophe Leroy
2024-09-01 13:27 ` kernel test robot
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=fe8ea6a6-71d7-4cfc-b20b-fa0a7f39a4be@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=Jason@zx2c4.com \
--cc=adhemerval.zanella@linaro.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=xry111@xry111.site \
/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
all inboxes | Powered by JetHome®