From: Ricardo Ribalda <ribalda@chromium.org>
To: Ross Zwisler <zwisler@kernel.org>
Cc: Eric Biederman <ebiederm@xmission.com>,
Baoquan He <bhe@redhat.com>, Philipp Rudo <prudo@redhat.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Simon Horman <horms@kernel.org>
Subject: Re: [PATCH v5 2/2] x86/purgatory: Add linker script
Date: Mon, 3 Apr 2023 17:35:06 +0200 [thread overview]
Message-ID: <CANiDSCv5eKGgQ3f6jstoo9X0Je3T63waVrPH3nth4-280+rcdw@mail.gmail.com> (raw)
In-Reply-To: <CAGRrVHx4S0VxMQ-76i3sQQNLUBKbHr_wJdLhJ8F9D6R=UoCLAA@mail.gmail.com>
Hi Ross
On Fri, 31 Mar 2023 at 21:14, Ross Zwisler <zwisler@kernel.org> wrote:
>
> On Thu, Mar 30, 2023 at 3:45 AM Ricardo Ribalda <ribalda@chromium.org> wrote:
> > Make sure that the .text section is not divided in multiple overlapping
> > sections. This is not supported by kexec_file.
>
> How does this interact with patch #1 from this series, which IIUC
> allows us to handle the case where the .text section is split between
> .text and .text.hot? Do we still need that patch, but only for
> non-x86 platforms? Or do we need both, and this patch will need to be
> replicated for other arches?
Patch 1/2 is a must. Patch 2/2 is a nice_to_have and would be great to
have a similar patch for every arch... but I do not feel confident
enough to send it for every arch :)
If we have linker scripts for all the arches do we need 1/2?
I think so, because the user might want to load a kernel <6.4 built
with clang > 16.
Regards!
--
Ricardo Ribalda
prev parent reply other threads:[~2023-04-03 15:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 9:44 [PATCH v5 0/2] kexec: Fix kexec_file_load for llvm16 Ricardo Ribalda
2023-03-30 9:44 ` [PATCH v5 1/2] kexec: Support purgatories with .text.hot sections Ricardo Ribalda
2023-03-30 15:03 ` Steven Rostedt
2023-04-03 14:42 ` Philipp Rudo
2023-03-30 9:44 ` [PATCH v5 2/2] x86/purgatory: Add linker script Ricardo Ribalda
2023-03-30 15:15 ` Steven Rostedt
2023-03-30 15:18 ` Borislav Petkov
2023-03-30 15:31 ` Steven Rostedt
2023-03-30 16:00 ` Borislav Petkov
2023-04-07 23:22 ` Nick Desaulniers
2023-04-11 21:45 ` Ricardo Ribalda
2023-04-18 17:49 ` Nick Desaulniers
2023-03-31 19:13 ` Ross Zwisler
2023-04-03 15:35 ` Ricardo Ribalda [this message]
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=CANiDSCv5eKGgQ3f6jstoo9X0Je3T63waVrPH3nth4-280+rcdw@mail.gmail.com \
--to=ribalda@chromium.org \
--cc=bhe@redhat.com \
--cc=ebiederm@xmission.com \
--cc=horms@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prudo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=zwisler@kernel.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;
as well as URLs for NNTP newsgroup(s).