From: "Arnd Bergmann" <arnd@arndb•de>
To: "Palmer Dabbelt" <palmer@dabbelt•com>,
"Randy Dunlap" <rdunlap@infradead•org>
Cc: "Alexandre Ghiti" <alex@ghiti•fr>,
"Stephen Rothwell" <sfr@canb•auug.org.au>,
linux-next <linux-next@vger•kernel.org>,
linux-kernel@vger•kernel.org,
"Paul Walmsley" <paul.walmsley@sifive•com>,
"Albert Ou" <aou@eecs•berkeley.edu>,
linux-riscv@lists•infradead.org,
"Conor Dooley" <conor@kernel•org>
Subject: Re: linux-next: Tree for May 15 (several RV64 build errors)
Date: Wed, 24 May 2023 08:23:41 +0200 [thread overview]
Message-ID: <65124759-26de-4111-bc54-545a00620d75@app.fastmail.com> (raw)
In-Reply-To: <mhng-e172207d-d67d-46ab-ab95-85f0a854ace2@palmer-ri-x1c9a>
On Wed, May 24, 2023, at 03:29, Palmer Dabbelt wrote:
> On Tue, 23 May 2023 17:22:20 PDT (-0700), rdunlap@infradead•org wrote:
>> On 5/23/23 06:07, Alexandre Ghiti wrote:
>>> On 23/05/2023 04:28, Randy Dunlap wrote:
>>>> On 5/19/23 03:42, Alexandre Ghiti wrote:
>>>>>>> /opt/crosstool/gcc-12.2.0-nolibc/riscv64-linux/bin/riscv64-linux-ld: section .data LMA [000000000041a000,00000000075bffd7] overlaps section .text LMA [00000000000f09d4,00000000033562ab]
>>>>>>> /opt/crosstool/gcc-12.2.0-nolibc/riscv64-linux/bin/riscv64-linux-ld: section .init.pi.text LMA [00000000033562ac,0000000003359137] overlaps section .data LMA [000000000041a000,00000000075bffd7]
>>>>>>
>>>>>> I'll check this one too which seems to be related to kernel/pi introduction.
>>>>>
>>>>> Thanks to Bjorn: this is caused by XIP_KERNEL, which is known to have limited size, hence the overlap, so no fix for this one. Is there a way to exclude this config from randconfig?
>>>> Does this mean exclude XIP_KERNEL or something else from randconfigs?
>>>
>>>
>>> I meant excluding XIP_KERNEL from randconfigs: it has very strict constraints regarding what can/can't be enabled then it needs human intervention to make sure the error above does not happen. So I would not bother testing this in randconfigs if possible.
>>
>> I can exclude it from my randconfig builds, but I don't know of a way to exclude it from randconfig builds in general (i.e., for everyone).
>
> Arnd had suggested a trick related to menus that would result in
> randconfig never enabling some config. It'd suggested for
> CONFIG_NONPORTABLE, but we didn't use it because it'd reduce randconfig
> coverage.
>
> Maybe we should add a CONFIG_VERYSPECIAL of some sort and hide things
> like XIP behind it (maybe M-mode too)?
I usually add 'depends on !COMPILE_TEST', that excludes it from most
build bots.
Arnd
next prev parent reply other threads:[~2023-05-24 6:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 4:12 linux-next: Tree for May 15 Stephen Rothwell
2023-05-16 2:18 ` linux-next: Tree for May 15 (drivers/dma/ti/k3-udma.c) Randy Dunlap
2023-05-16 17:35 ` Vinod Koul
2023-05-16 2:23 ` linux-next: Tree for May 15 (net/ipv4/ipconfig.c:) Randy Dunlap
2023-05-18 3:57 ` David Ahern
2023-05-16 2:26 ` linux-next: Tree for May 15 (drivers/macintosh/ams/ams-core.c) Randy Dunlap
2023-05-16 2:40 ` linux-next: Tree for May 15 (drivers/tty/serial/8250/8250_omap.c) Randy Dunlap
2023-05-17 5:51 ` Tony Lindgren
2023-05-16 2:45 ` linux-next: Tree for May 15 (several RV64 build errors) Randy Dunlap
2023-05-16 6:18 ` Alexandre Ghiti
2023-05-19 10:42 ` Alexandre Ghiti
2023-05-19 11:22 ` Conor Dooley
2023-05-19 12:09 ` Alexandre Ghiti
2023-05-23 2:28 ` Randy Dunlap
2023-05-23 13:07 ` Alexandre Ghiti
2023-05-24 0:22 ` Randy Dunlap
2023-05-24 1:29 ` Palmer Dabbelt
2023-05-24 6:23 ` Arnd Bergmann [this message]
2023-05-24 22:41 ` Randy Dunlap
2023-05-24 22:49 ` Conor Dooley
2023-05-24 23:11 ` Palmer Dabbelt
2023-05-25 12:50 ` Conor Dooley
2023-05-16 2:51 ` linux-next: Tree for May 15 (config SERIAL_CPM) Randy Dunlap
2023-05-18 5:49 ` Jiri Slaby
2023-05-18 5:50 ` Jiri Slaby
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=65124759-26de-4111-bc54-545a00620d75@app.fastmail.com \
--to=arnd@arndb$(echo .)de \
--cc=alex@ghiti$(echo .)fr \
--cc=aou@eecs$(echo .)berkeley.edu \
--cc=conor@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-riscv@lists$(echo .)infradead.org \
--cc=palmer@dabbelt$(echo .)com \
--cc=paul.walmsley@sifive$(echo .)com \
--cc=rdunlap@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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