From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
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: Sun, 1 Sep 2024 20:02:54 +0200 [thread overview]
Message-ID: <ZtSsTkTUCGyxaN_d@zx2c4.com> (raw)
In-Reply-To: <667622ae-dde5-410f-a9f8-4801788af278@csgroup.eu>
On Sun, Sep 01, 2024 at 08:00:30PM +0200, Christophe Leroy wrote:
> 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.
> >
> > What about, instead, something like below, replacing the other commit?
>
> I need to look at it in more details and perfom a test, but after first
> look I can't figure out how it would work.
>
> When I build selftests,
>
> to build 32 bits selftests I do:
>
> make ARCH=powerpc CROSS_COMPILE=ppc-linux-
>
> to build a 64 bits BE selftests I do:
>
> make ARCH=powerpc CROSS_COMPILE=powerpc64-linux-
>
> to build a 64 bits LE selftests I do:
>
> make ARCH=powerpc CROSS_COMPILE=powerpc64le-linux-
>
>
> I addition, in case someone does the build on a native platform directly,
>
> On 32 bits, uname -m returns 'ppc'
> On 64 bits, uname -m returns 'ppc64'
> On 64 bits little endian, uname -m returns 'ppc64le'
>
> How would this fit in the logic where IIUC you just remove '_64' from
> 'x86_64' to get 'x86'
Huh? That's not what tools/scripts/Makefile.arch does.
next prev parent reply other threads:[~2024-09-01 18:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-31 17:11 [PATCH] selftests: vDSO: Do not rely on $ARCH for vdso_test_getrandom && vdso_test_chacha 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 [this message]
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
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=ZtSsTkTUCGyxaN_d@zx2c4.com \
--to=jason@zx2c4.com \
--cc=adhemerval.zanella@linaro.org \
--cc=broonie@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--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