From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Neal Gompa" <ngompa13@gmail.com>
Cc: "Jan Hendrik Farr" <kernel@jfarr.cc>,
<linux-kernel@vger.kernel.org>,
<systemd-devel@lists.freedesktop.org>, <x86@kernel.org>,
<kexec@lists.infradead.org>, <dhowells@redhat.com>,
<keyrings@vger.kernel.org>, <bluca@debian.org>,
<bhelgaas@google.com>, <tglx@linutronix.de>,
<akpm@linux-foundation.org>
Subject: Re: [systemd-devel] [PATCH 0/1] x86/kexec: UKI support
Date: Tue, 12 Sep 2023 13:37:47 +0300 [thread overview]
Message-ID: <CVGVGJIQPIZ2.WN97L6BV5S97@suppilovahvero> (raw)
In-Reply-To: <CAEg-Je9GF5S+QcsspM_CzDSxzCN8h2eRp7BbctC1x7-rH8j68g@mail.gmail.com>
On Tue Sep 12, 2023 at 2:20 AM EEST, Neal Gompa wrote: > On Mon, Sep 11, 2023 at 7:15 PM Jarkko Sakkinen <jarkko@kernel.org> wrote:
> > On Sat Sep 9, 2023 at 7:18 PM EEST, Jan Hendrik Farr wrote:
> > > Hello,
> > >
> > > this patch implements UKI support for kexec_file_load. It will require support
> > > in the kexec-tools userspace utility. For testing purposes the following can be used:
> > > https://github.com/Cydox/kexec-test/
> > >
> > > There has been discussion on this topic in an issue on GitHub that is linked below
> > > for reference.
> > >
> > >
> > > Some links:
> > > - Related discussion: https://github.com/systemd/systemd/issues/28538
> > > - Documentation of UKIs: https://uapi-group.org/specifications/specs/unified_kernel_image/
> > >
> > > Jan Hendrik Farr (1):
> > > x86/kexec: UKI support
> > >
> > > arch/x86/include/asm/kexec-uki.h | 7 ++
> > > arch/x86/include/asm/parse_pefile.h | 32 +++++++
> > > arch/x86/kernel/Makefile | 2 +
> > > arch/x86/kernel/kexec-uki.c | 113 +++++++++++++++++++++++++
> > > arch/x86/kernel/machine_kexec_64.c | 2 +
> > > arch/x86/kernel/parse_pefile.c | 110 ++++++++++++++++++++++++
> > > crypto/asymmetric_keys/mscode_parser.c | 2 +-
> > > crypto/asymmetric_keys/verify_pefile.c | 110 +++---------------------
> > > crypto/asymmetric_keys/verify_pefile.h | 16 ----
> > > 9 files changed, 278 insertions(+), 116 deletions(-)
> > > create mode 100644 arch/x86/include/asm/kexec-uki.h
> > > create mode 100644 arch/x86/include/asm/parse_pefile.h
> > > create mode 100644 arch/x86/kernel/kexec-uki.c
> > > create mode 100644 arch/x86/kernel/parse_pefile.c
> > >
> > > --
> > > 2.40.1
> >
> > What the heck is UKI?
>
> Unified Kernel Images. More details available here:
> https://uapi-group.org/specifications/specs/unified_kernel_image/
>
> It's a way of creating initramfs-style images as fully generic,
> reproducible images that can be built server-side.
You can build today a kernel with these compiled in:
1. EFI stub
2. initeramfs
3. cmdline
Why another way (and label 'UKI') for a pre-existing feature?
BR, Jarkko
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2023-09-12 10:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 16:18 [PATCH 0/1] x86/kexec: UKI support 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
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 [this message]
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=CVGVGJIQPIZ2.WN97L6BV5S97@suppilovahvero \
--to=jarkko@kernel.org \
--cc=akpm@linux-foundation.org \
--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=linux-kernel@vger.kernel.org \
--cc=ngompa13@gmail.com \
--cc=systemd-devel@lists.freedesktop.org \
--cc=tglx@linutronix.de \
--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