All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Arnout Vandecappelle <arnout@mind.be>, Joel Stanley <joel@jms.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] linux: Fix powerpc64le defconfig selection
Date: Mon, 16 May 2022 23:17:13 +1000	[thread overview]
Message-ID: <87a6bh7h2e.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <a18d0411-9134-2ee7-62d0-4ba6a1780846@mind.be>

Arnout Vandecappelle <arnout@mind.be> writes:
> On 10/05/2022 04:20, Joel Stanley wrote:
>> The default defconfig target for the 64 bit powerpc kernel is
>> ppc64_defconfig, the big endian configuration.
>> 
>> When building for powerpc64le users want the little endian kernel as
>> they can't boot LE userspace on a BE kernel.
>> 
>> Fix up the defconfig used in this case. This will avoid the following
>> autobuilder failure:
>> 
>>   VDSO32A arch/powerpc/kernel/vdso32/sigtramp.o
>>   cc1: error: ‘-m32’ not supported in this configuratioin
>>   make[4]: *** [arch/powerpc/kernel/vdso32/Makefile:49: arch/powerpc/kernel/vdso32/sigtramp.o] Error 1
>> 
>>   http://autobuild.buildroot.net/results/dd76d53bab56470c0b83e296872d7bb90f9e8296/
>> 
>> Note that the failure indicates the toolchain is configured to disable
>> the 32 bit target, causing the kernel to fail when building the 32 bit
>> VDSO. This is only a problem on the BE kernel as the LE kernel disables
>> CONFIG_COMPAT, aka 32 bit userspace support, by default.
>> 
>> Signed-off-by: Joel Stanley <joel@jms.id.au>
>
>   Applied to master, thanks. However, the defconfig mechanism for *all* powerpc 
> seems pretty broken. Here's what we have in 5.16, before that there was 
> something similar:
>
> # If we're on a ppc/ppc64/ppc64le machine use that defconfig, otherwise just use
> # ppc64_defconfig because we have nothing better to go on.
> uname := $(shell uname -m)
> KBUILD_DEFCONFIG := $(if $(filter ppc%,$(uname)),$(uname),ppc64)_defconfig
>
>   So I guess we should use a specific defconfig for *all* powerpc.
>
>   The arch-default defconfig is generally not really reliable, for example for 
> arm it always takes v7_multi, but that won't work for v7m targets...

There's a fundamental problem that just the "arch" is not sufficient
detail when you're building a kernel.

Two CPUs that implement the same user-visible "arch" may differ enough
at the kernel level to require a different defconfig.

Having said that I think we could handle this better in the powerpc
kernel. Other arches allow specifying a different value for ARCH, which
then is fed into the defconfig.

That way you could at least pass ARCH=ppc/ppc64/ppc64le, and get an
appropriate defconfig.

I'll work on some kernel changes for that.

cheers

  reply	other threads:[~2022-05-16 13:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10  2:20 [Buildroot] [PATCH] linux: Fix powerpc64le defconfig selection Joel Stanley
2022-05-13 21:52 ` Arnout Vandecappelle
2022-05-16 13:17   ` Michael Ellerman [this message]
2022-05-18 12:03     ` Arnd Bergmann
2022-05-18 17:23     ` Arnout Vandecappelle
2022-05-18 17:23       ` Arnout Vandecappelle
2022-05-26  6:57       ` Michael Ellerman
2022-05-17  6:13   ` Joel Stanley
2022-05-18 17:32     ` Arnout Vandecappelle
2022-05-28 19:25 ` Peter Korsgaard

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=87a6bh7h2e.fsf@mpe.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=arnout@mind.be \
    --cc=buildroot@buildroot.org \
    --cc=joel@jms.id.au \
    --cc=linuxppc-dev@lists.ozlabs.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.