From: Ricardo Ribalda <email@example.com>
To: Nick Desaulniers <firstname.lastname@example.org>
Cc: Steven Rostedt <email@example.com>,
Eric Biederman <firstname.lastname@example.org>,
Baoquan He <email@example.com>, Philipp Rudo <firstname.lastname@example.org>,
Ross Zwisler <email@example.com>,
Simon Horman <firstname.lastname@example.org>,
Borislav Petkov <email@example.com>
Subject: Re: [PATCH v5 2/2] x86/purgatory: Add linker script
Date: Tue, 11 Apr 2023 23:45:56 +0200 [thread overview]
Message-ID: <CANiDSCvSDcQi2Qbwu8ddpPDAYehu2VoOB6x-v_PaMkWnwAGxYQ@mail.gmail.com> (raw)
On Sat, 8 Apr 2023 at 01:22, Nick Desaulniers <firstname.lastname@example.org> wrote:
> Hi Ricardo,
> Thanks for the patch! Please make sure to cc our mailing list
> <email@example.com> for llvm specific issues.
> scripts/get_maintainer.pl should recommend it, or you can find it from
> clangbuiltlinux.github.io. You can also ping me internally for
> toolchain related issues.
> Start of thread.
> On Thu, Mar 30, 2023 at 9:00 AM Borislav Petkov <firstname.lastname@example.org> wrote:
> > On Thu, Mar 30, 2023 at 11:31:27AM -0400, Steven Rostedt wrote:
> > > On Thu, 30 Mar 2023 17:18:26 +0200
> > > Borislav Petkov <email@example.com> wrote:
> > >
> > > > On Thu, Mar 30, 2023 at 11:15:23AM -0400, Steven Rostedt wrote:
> > > > > > Make sure that the .text section is not divided in multiple overlapping
> > > > > > sections. This is not supported by kexec_file.
> Perhaps this is related to CrOS' use of AutoFDO creating .text.hot?
> If so, it's probably more straightforward to straight up disable PGO
> for kexec. See also:
> commit bde971a83bbf ("KVM: arm64: nvhe: Fix build with profile optimization")
It was indeed due to the AutoFDO, adding
KBUILD_CFLAGS := $(filter-out -fprofile-sample-use=% -fprofile-use=%,
It is definitely simpler than adding a linker script, but I am not
sure if it is the correct way to fix this... Seems like splitting
.text in multiple sections is an implementation detail of the compiler
and the only way to force it is with a linker script... Or am I
Shall I send a new version with the KBUILD_CFLAGS ?
> > > >
> > > > And?
> > > >
> > > > What is the failure scenario? Why are you fixing it? Why do we care?
> > > >
> > > > This is way too laconic.
> > > >
> > >
> > > Yeah, I think the change log in patch 1 needs to be in this patch too,
> > > which gives better context.
> > Just read it.
> > Why did it work with clang version < 16?
> I'll bet if we bisect llvm, we can spot what might have changed, which
> may give us a clue on how to get the old behavior back; maybe without
> the need for a linker script.
> Ricardo, how did you verify that your fix was correct? Surely we can
> check using command line utilities without needing a full blown kexec
> setup? If you can share more info, I can bisect llvm quickly. If it
> requires profile data, you'll need to share it, since CrOS engineers
> still have not posted public documentation on AutoFDO as I have
> repeatedly asked for.
The simplest test is to run:
$readelf -S arch/x86/purgatory/purgatory.ro | grep "] \.text"
[ 3] .text PROGBITS 0000000000000000 000002a0
If there is only one .text section then that kernel will be load
properly via kexec_file().
> > + toolchains ML.
> > --
> > Regards/Gruss,
> > Boris.
> > https://people.kernel.org/tglx/notes-about-netiquette
> ~Nick Desaulniers
next prev parent reply other threads:[~2023-04-11 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <firstname.lastname@example.org>
[not found] ` <email@example.com>
[not found] ` <firstname.lastname@example.org>
[not found] ` <20230330151826.GDZCWoQkQBj4BYbwWw@fat_crate.local>
[not found] ` <email@example.com>
2023-03-30 16:00 ` [PATCH v5 2/2] x86/purgatory: Add linker script Borislav Petkov
2023-04-07 23:22 ` Nick Desaulniers
2023-04-11 21:45 ` Ricardo Ribalda [this message]
2023-04-18 17:49 ` Nick Desaulniers
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).