mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jan Hendrik Farr" <kernel@jfarr.cc>
To: "Luca Boccassi" <bluca@debian.org>
Cc: linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
	x86@kernel.org, tglx@linutronix.de, dhowells@redhat.com,
	vgoyal@redhat.com, keyrings@vger.kernel.org,
	akpm@linux-foundation.org, bhe@redhat.com, bhelgaas@google.com,
	lennart@poettering.net, systemd-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/1] x86/kexec: UKI support
Date: Sat, 09 Sep 2023 19:57:09 +0200	[thread overview]
Message-ID: <5c94f7f4-697f-4388-9243-009c0c2d745f@app.fastmail.com> (raw)
In-Reply-To: <CAMw=ZnT-Ck-Y4i-MZAf99U5nzgDaj-q8UPRH_c00JgGMtUy_QA@mail.gmail.com>

> - the cmdline section is actually optional, just like it's optional to
> pass it on a traditional kexec load, so it should be used if present,
> but skipped if not

Should be an easy fix.

This should be updated in the UKI documentation as for other optional sections it's explicitly marked. I assumed that in the case of an empty cmdline the section would still be included but empty. Or is that semantically different: empty .cmdline section -> no cmdline allowed, no .cmdline section -> user can specify cmdline in bootloader?

> - the dtb section also is optional but supported, and given kexec
> supports loading a new dtb I think this change should support it too
> immediately.  Moreover, we are adding support for multiple DTBs in a
> single UKI (by simply having multiple .dtb sections, and picking the
> one that matches the firmware), as a stretch goal would be nice to
> support that too, but it can also come later

As far as I know dtb is not supported by kexec_file_load at all at the moment. Maybe someone here knows more about this. I'll look into it.

> - also what would it take to support arm64, which is the other major UEFI arch?

I'm not familiar with UEFI on arm64, but I can certainly look into it. I assume it's not gonna be that difficult.

  reply	other threads:[~2023-09-09 17:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-09 16:18 Jan Hendrik Farr
2023-09-09 16:18 ` [PATCH 1/1] " Jan Hendrik Farr
2023-09-09 17:15 ` [PATCH 0/1] " Luca Boccassi
2023-09-09 17:57   ` Jan Hendrik Farr [this message]
2023-09-09 18:10     ` Luca Boccassi
2023-09-11  3:23       ` Jan Hendrik Farr
2023-09-11 22:02 ` Jarkko Sakkinen
2023-09-11 22:54   ` Jan Hendrik Farr
2023-09-12 10:33     ` Jarkko Sakkinen
2023-09-12 15:32       ` Jan Hendrik Farr
2023-09-12 17:41         ` Jarkko Sakkinen
2023-09-12 18:56           ` Jan Hendrik Farr
2023-09-12 19:24             ` Jarkko Sakkinen
2023-09-12 19:38               ` Jan Hendrik Farr
2023-09-12 20:49               ` Jan Hendrik Farr
2023-09-13 14:45                 ` Jarkko Sakkinen
2023-09-13 15:07                   ` Jan Hendrik Farr
2023-09-13 15:58                     ` Jarkko Sakkinen
2023-09-14  9:11                   ` Lennart Poettering
2023-09-14 12:12                     ` Jarkko Sakkinen
2023-09-14  8:48         ` Lennart Poettering
2023-09-14 11:52           ` Jarkko Sakkinen
2023-09-11 23:20   ` [systemd-devel] " Neal Gompa
2023-09-12 10:37     ` Jarkko Sakkinen
2023-09-18 15:41       ` Dimitri John Ledkov
2023-09-25 16:43         ` Jarkko Sakkinen

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=5c94f7f4-697f-4388-9243-009c0c2d745f@app.fastmail.com \
    --to=kernel@jfarr.cc \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=bluca@debian.org \
    --cc=dhowells@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=keyrings@vger.kernel.org \
    --cc=lennart@poettering.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=systemd-devel@lists.freedesktop.org \
    --cc=tglx@linutronix.de \
    --cc=vgoyal@redhat.com \
    --cc=x86@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

all inboxes | Powered by JetHome®