From: Pratyush Yadav <pratyush@kernel.org>
To: "Michał Cłapiński" <mclapinski@google.com>
Cc: Pratyush Yadav <pratyush@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <bhe@redhat.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Mike Rapoport <rppt@kernel.org>,
kexec@lists.infradead.org
Subject: Re: [PATCH] kho: try to allocate contiguous memory for kexec segments
Date: Tue, 02 Jun 2026 19:09:03 +0200 [thread overview]
Message-ID: <2vxzjysgdg40.fsf@kernel.org> (raw)
In-Reply-To: <CAAi7L5fDmbXgvZunn6hq2GoZqFGZ-YdJtgmSLD6pa06baF-KCQ@mail.gmail.com> ("Michał Cłapiński"'s message of "Tue, 2 Jun 2026 19:08:09 +0200")
On Tue, Jun 02 2026, Michał Cłapiński wrote:
> On Tue, Jun 2, 2026 at 6:58 PM Pratyush Yadav <pratyush@kernel.org> wrote:
>>
>> On Mon, Jun 01 2026, Michal Clapinski wrote:
>>
>> > This allows us to skip relocations (and maybe checksum calculation
>> > in the future).
>>
>> I'm confused. Doesn't your patch "kexec_file: skip checksum verification
>> when safe" [0] skip the checksum for KHO already? So this only skips the
>> relocations part then?
>>
>> And based on the discussion on that thread, relocations don't seem to
>> take much time. So is there a real need for this patch?
>
> I sent this patch out yesterday, then realized it wasn't going to work
> so I abandoned this approach.
> Today I sent patch [0] that skips the checksum for KHO, so this patch
> is no longer needed.
Makes sense, thanks for clarifying.
[...]
--
Regards,
Pratyush Yadav
prev parent reply other threads:[~2026-06-02 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 19:30 [PATCH] kho: try to allocate contiguous memory for kexec segments Michal Clapinski
2026-06-01 19:52 ` Michał Cłapiński
2026-06-02 16:58 ` Pratyush Yadav
2026-06-02 17:08 ` Michał Cłapiński
2026-06-02 17:09 ` Pratyush Yadav [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=2vxzjysgdg40.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=mclapinski@google.com \
--cc=pasha.tatashin@soleen.com \
--cc=rppt@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 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.