From: Willy Tarreau <w@1wt.eu>
To: Zhangjin Wu <falcon@tinylab.org>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, thomas@t-8ch.de
Subject: Re: [PATCH v1 3/8] selftests/nolibc: select_null: fix up for big endian powerpc64
Date: Wed, 19 Jul 2023 22:25:05 +0200 [thread overview]
Message-ID: <20230719202505.GA6842@1wt.eu> (raw)
In-Reply-To: <20230719064912.59792-1-falcon@tinylab.org>
Hi Zhangjin,
On Wed, Jul 19, 2023 at 02:49:12PM +0800, Zhangjin Wu wrote:
> Hi, Willy
>
> > Hi Zhangjin,
> >
> > On Wed, Jul 19, 2023 at 07:56:37AM +0800, Zhangjin Wu wrote:
> > > It made me recalled I have at last disabled (not enabled for tinyconfig) the following options:
> > >
> > > CONFIG_ALTIVEC
> > > CONFIG_VSX --> This option enables kernel support for the Vector Scaler extensions
> > >
> > > Or we can disable the vsx instructions explicitly:
> > >
> > > -mno-vsx
> > >
> > > Both of them work well, but I prefer -mno-vsx for to get a faster build, what about you?
> > >
> > > +CFLAGS_powerpc64 = -m64 -mbig-endian -Wl,-EB,-melf64ppc -mno-vsx
> > > +CFLAGS_powerpc64le = -m64 -mlittle-endian -Wl,-EL,-melf64ppc -mno-vsx
> > >
> > > So, this patch itself is wrong, let's drop it from the next revision.
> >
> > Better explicitly disable it in the CFLAGS (2nd option) if we want to
> > make sure we don't want to rely on this, at least for portability
> > purposes.
>
> Ok, thanks, have updated CFLAGS in these two patches locally:
>
> [PATCH v1 7/8] selftests/nolibc: add test support for powerpc64le
> [PATCH v1 8/8] selftests/nolibc: add test support for powerpc64
>
> what about the other ones? I'm ready to send v2 ;-)
I have not had the time to review them yet. Please just don't send
another series yet, that just adds more noise and makes it hard to
distinguish all of them. I hope to be able to check these and hopefully
the tinyconfig series by the week-end.
Thanks,
Willy
next prev parent reply other threads:[~2023-07-19 20:25 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 21:09 [PATCH v1 0/8] tools/nolibc: add 32/64-bit powerpc support Zhangjin Wu
2023-07-18 21:10 ` [PATCH v1 1/8] tools/nolibc: add support for powerpc Zhangjin Wu
2023-07-23 7:32 ` Thomas Weißschuh
2023-07-23 8:15 ` Willy Tarreau
2023-07-25 5:44 ` Zhangjin Wu
2023-07-25 6:29 ` Willy Tarreau
2023-07-25 11:02 ` Zhangjin Wu
2023-07-25 14:45 ` Ammar Faizi
2023-07-25 17:04 ` Zhangjin Wu
2023-07-25 18:23 ` Ammar Faizi
2023-07-25 20:23 ` Zhangjin Wu
2023-07-25 18:27 ` Willy Tarreau
2023-07-25 20:52 ` Zhangjin Wu
2023-07-25 6:14 ` Zhangjin Wu
2023-07-18 21:11 ` [PATCH v1 2/8] tools/nolibc: add support for powerpc64 Zhangjin Wu
2023-07-18 21:13 ` [PATCH v1 3/8] selftests/nolibc: select_null: fix up for big endian powerpc64 Zhangjin Wu
2023-07-18 22:17 ` Thomas Weißschuh
2023-07-18 23:56 ` Zhangjin Wu
2023-07-19 4:33 ` Willy Tarreau
2023-07-19 6:49 ` Zhangjin Wu
2023-07-19 20:25 ` Willy Tarreau [this message]
2023-07-20 6:11 ` Thomas Weißschuh
2023-07-18 21:14 ` [PATCH v1 4/8] selftests/nolibc: add extra config file customize support Zhangjin Wu
2023-07-22 12:00 ` Willy Tarreau
2023-07-25 14:30 ` Zhangjin Wu
2023-07-29 7:45 ` Willy Tarreau
2023-07-29 9:43 ` Zhangjin Wu
2023-07-18 21:15 ` [PATCH v1 5/8] selftests/nolibc: add XARCH and ARCH mapping support Zhangjin Wu
2023-07-22 12:03 ` Willy Tarreau
2023-07-18 21:16 ` [PATCH v1 6/8] selftests/nolibc: add test support for powerpc Zhangjin Wu
2023-07-18 21:17 ` [PATCH v1 7/8] selftests/nolibc: add test support for powerpc64le Zhangjin Wu
2023-07-22 12:07 ` Willy Tarreau
2023-07-18 21:18 ` [PATCH v1 8/8] selftests/nolibc: add test support for powerpc64 Zhangjin Wu
2023-07-22 12:10 ` Willy Tarreau
2023-07-25 5:50 ` Zhangjin Wu
2023-07-25 6:02 ` Willy Tarreau
2023-07-23 7:47 ` [PATCH v1 0/8] tools/nolibc: add 32/64-bit powerpc support 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=20230719202505.GA6842@1wt.eu \
--to=w@1wt.eu \
--cc=arnd@arndb.de \
--cc=falcon@tinylab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=thomas@t-8ch.de \
/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