mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Jan Hendrik Farr" <kernel@jfarr.cc>, <linux-kernel@vger.kernel.org>
Cc: <kexec@lists.infradead.org>, <x86@kernel.org>,
	<tglx@linutronix.de>, <dhowells@redhat.com>, <vgoyal@redhat.com>,
	<keyrings@vger.kernel.org>, <akpm@linux-foundation.org>,
	"Baoquan He" <bhe@redhat.com>, <bhelgaas@google.com>,
	<lennart@poettering.net>, "Luca Boccassi" <bluca@debian.org>
Subject: Re: [PATCH 0/1] x86/kexec: UKI support
Date: Tue, 12 Sep 2023 22:24:02 +0300	[thread overview]
Message-ID: <CVH6NGLENMPH.271W6X80061M@suppilovahvero> (raw)
In-Reply-To: <5a67051d-eb21-4a96-acc4-40f829a59e23@app.fastmail.com>

On Tue Sep 12, 2023 at 9:56 PM EEST, Jan Hendrik Farr wrote:
> > What sort of bottleneck does the EFI stub have so that we need yet
> > another envelope?
>
> Well I can come up with a few advantages of UKI compared to normal bzImage with builtin initrd and cmdline.
>
> 1. You already identified this one. Using addons to adjust your cmdline

It is not a benefit as this is already possible today.

> 2. I can use my normal initramfs generation tooling. Just install my
> compiled kernel, my distros install script will generate the
> initramfs. Then I package it up as a UKI. This will be a lot more
> awkward with a builtin initrd.
> 3. Measured boot. You can place PCR signatures in the UKI using
> systemd-measure. This will sign the expected PCR values for booting
> this UKI. I think with normal bzImage this will be a lot more
> difficult. If you place those PCR signatures in the builtin initrd
> this will change the kernel image which means now the values you
> signed no longer match (depending on how you measure the kernel; I
> don't think the normal EFI stub even measures the kernel in first
> place, but I could be mistaken about this)
> 4. UKIs are automatically recognized by systemd-boot

These are sort of "tautological" arguments. There must be some
objective reasons why this architecture was chosen instead of
other (i.e. using what already pre-exists).

BR, Jarkko

  reply	other threads:[~2023-09-12 19:24 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
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 [this message]
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=CVH6NGLENMPH.271W6X80061M@suppilovahvero \
    --to=jarkko@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=bluca@debian.org \
    --cc=dhowells@redhat.com \
    --cc=kernel@jfarr.cc \
    --cc=kexec@lists.infradead.org \
    --cc=keyrings@vger.kernel.org \
    --cc=lennart@poettering.net \
    --cc=linux-kernel@vger.kernel.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®