From: "Ludovic Courtès" <ludo@gnu.org>
To: guix-devel@gnu.org
Subject: Re: 03/11: reconfigure: Support loading the system for kexec reboot.
Date: Tue, 07 Jan 2025 18:50:54 +0100 [thread overview]
Message-ID: <87r05ezf5t.fsf@gnu.org> (raw)
In-Reply-To: <87a5c5ylj9.fsf@wolfsden.cz> (Tomas Volf's message of "Sun, 05 Jan 2025 22:54:02 +0100")
Hello,
Tomas Volf <~@wolfsden.cz> skribis:
>> Good point! kexec_file_load(2) can only be given one initrd, so I
>> suppose it cannot support extra initrds.
>>
>> That’s something we should at least document and probably protect
>> against.
>
> Based on the kexec_file_load's man page it looks like it takes a file
> descriptor. Is there a technical reason why we cannot just construct
> the unified initrd in memory by overlaying the extra-initrd over the
> initrd (which is what GRUB does anyway) and feed the result to the
> kernel via a pipe?
Woow. Everything’s possible, but it sounds non-trivial (possibly more
code than kexec support in its current form!).
In the meantime, we should at least document the limitation and/or skip
the feature entirely when ‘extra-initrd’ is specified.
Ludo’.
prev parent reply other threads:[~2025-01-07 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <173542420171.3052447.14254740746301984406@vcs3.savannah.gnu.org>
[not found] ` <20241228221642.E5EB9D3CB98@vcs3.savannah.gnu.org>
[not found] ` <87jzbi3f7f.fsf@wolfsden.cz>
[not found] ` <87y0zqqyrr.fsf@gnu.org>
2025-01-05 21:54 ` 03/11: reconfigure: Support loading the system for kexec reboot Tomas Volf
2025-01-07 17:50 ` Ludovic Courtès [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r05ezf5t.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).