From: Conor Dooley <conor@kernel.org>
To: Alexandre Ghiti <alexghiti@rivosinc.com>
Cc: Alexandre Ghiti <alex@ghiti.fr>,
Conor Dooley <conor.dooley@microchip.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Andreas Schwab <schwab@linux-m68k.org>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -fixes] riscv: Fix relocatable kernels with early alternatives using -fno-pie
Date: Tue, 30 May 2023 21:22:54 +0100 [thread overview]
Message-ID: <20230530-atrocious-control-bcb37de558fc@spud> (raw)
In-Reply-To: <CAHVXubgG31moSNOe3fRqFzUSJK9tRWKH1KPP_BO7wRNC4WzxTQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 548 bytes --]
On Tue, May 30, 2023 at 08:04:17PM +0200, Alexandre Ghiti wrote:
>
> Ahah, I think we found the culprit!
>
> With CONFIG_RELOCATABLE, vmlinux is actually stripped from all the
> relocations (so that it can be shipped) and vmlinux.relocs is what you
> should use instead, since it is just a copy of vmlinux before the
> removal of the relocations!
That probably makes us both eejits for not realising sooner...
Tested-by: Conor Dooley <conor.dooley@microchip.com> # booted on nezha & unmatched
Thanks for your patience here Alex.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-05-30 20:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 15:46 [PATCH -fixes] riscv: Fix relocatable kernels with early alternatives using -fno-pie Alexandre Ghiti
2023-05-26 16:24 ` Conor Dooley
2023-05-26 16:35 ` Conor Dooley
2023-05-27 9:13 ` Alexandre Ghiti
2023-05-27 10:02 ` Conor Dooley
2023-05-28 13:00 ` Alexandre Ghiti
2023-05-28 13:12 ` Conor Dooley
2023-05-28 13:42 ` Alexandre Ghiti
2023-05-28 13:56 ` Conor Dooley
2023-05-29 18:51 ` Alexandre Ghiti
2023-05-29 19:06 ` Conor Dooley
2023-05-29 19:37 ` Alexandre Ghiti
2023-05-30 11:27 ` Conor Dooley
2023-05-30 14:33 ` Alexandre Ghiti
2023-05-30 17:47 ` Conor Dooley
2023-05-30 18:04 ` Alexandre Ghiti
2023-05-30 20:22 ` Conor Dooley [this message]
2023-05-31 7:26 ` Alexandre Ghiti
2023-05-31 9:32 ` Conor Dooley
2023-05-31 11:03 ` Alexandre Ghiti
2023-05-26 16:38 ` Alexandre Ghiti
2023-05-31 15:03 ` Palmer Dabbelt
2023-05-31 15:10 ` patchwork-bot+linux-riscv
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=20230530-atrocious-control-bcb37de558fc@spud \
--to=conor@kernel.org \
--cc=alex@ghiti.fr \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=schwab@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox