From: Jan Hendrik Farr <kernel@jfarr.cc>
To: 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, bhe@redhat.com, bhelgaas@google.com,
lennart@poettering.net, bluca@debian.org,
systemd-devel@lists.freedesktop.org, kernel@jfarr.cc
Subject: [PATCH 0/1] x86/kexec: UKI support
Date: Sat, 9 Sep 2023 18:18:50 +0200 [thread overview]
Message-ID: <20230909161851.223627-1-kernel@jfarr.cc> (raw)
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
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Jan Hendrik Farr <kernel@jfarr.cc>
To: 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, bhe@redhat.com, bhelgaas@google.com,
lennart@poettering.net, bluca@debian.org,
systemd-devel@lists.freedesktop.org, kernel@jfarr.cc
Subject: [PATCH 0/1] x86/kexec: UKI support
Date: Sat, 9 Sep 2023 18:18:50 +0200 [thread overview]
Message-ID: <20230909161851.223627-1-kernel@jfarr.cc> (raw)
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
next reply other threads:[~2023-09-09 16:19 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 16:18 Jan Hendrik Farr [this message]
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 16:18 ` Jan Hendrik Farr
2023-09-09 17:15 ` [PATCH 0/1] " Luca Boccassi
2023-09-09 17:15 ` Luca Boccassi
2023-09-09 17:57 ` Jan Hendrik Farr
2023-09-09 17:57 ` Jan Hendrik Farr
2023-09-09 18:10 ` Luca Boccassi
2023-09-09 18:10 ` Luca Boccassi
2023-09-11 3:23 ` Jan Hendrik Farr
2023-09-11 3:23 ` Jan Hendrik Farr
2023-09-11 22:02 ` Jarkko Sakkinen
2023-09-11 22:02 ` Jarkko Sakkinen
2023-09-11 22:54 ` Jan Hendrik Farr
2023-09-11 22:54 ` Jan Hendrik Farr
2023-09-12 10:33 ` Jarkko Sakkinen
2023-09-12 10:33 ` Jarkko Sakkinen
2023-09-12 15:32 ` Jan Hendrik Farr
2023-09-12 15:32 ` Jan Hendrik Farr
2023-09-12 17:41 ` Jarkko Sakkinen
2023-09-12 17:41 ` Jarkko Sakkinen
2023-09-12 18:56 ` Jan Hendrik Farr
2023-09-12 18:56 ` Jan Hendrik Farr
2023-09-12 19:24 ` Jarkko Sakkinen
2023-09-12 19:24 ` Jarkko Sakkinen
2023-09-12 19:38 ` Jan Hendrik Farr
2023-09-12 19:38 ` Jan Hendrik Farr
2023-09-12 20:49 ` Jan Hendrik Farr
2023-09-12 20:49 ` Jan Hendrik Farr
2023-09-13 14:45 ` Jarkko Sakkinen
2023-09-13 14:45 ` Jarkko Sakkinen
2023-09-13 15:07 ` Jan Hendrik Farr
2023-09-13 15:07 ` Jan Hendrik Farr
2023-09-13 15:58 ` Jarkko Sakkinen
2023-09-13 15:58 ` Jarkko Sakkinen
2023-09-14 9:11 ` Lennart Poettering
2023-09-14 9:11 ` Lennart Poettering
2023-09-14 12:12 ` Jarkko Sakkinen
2023-09-14 12:12 ` Jarkko Sakkinen
2023-09-14 8:48 ` Lennart Poettering
2023-09-14 8:48 ` Lennart Poettering
2023-09-14 11:52 ` Jarkko Sakkinen
2023-09-14 11:52 ` Jarkko Sakkinen
2023-09-11 23:20 ` [systemd-devel] " Neal Gompa
2023-09-11 23:20 ` Neal Gompa
2023-09-12 10:37 ` Jarkko Sakkinen
2023-09-12 10:37 ` Jarkko Sakkinen
2023-09-18 15:41 ` Dimitri John Ledkov
2023-09-18 15:41 ` Dimitri John Ledkov
2023-09-25 16:43 ` Jarkko Sakkinen
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=20230909161851.223627-1-kernel@jfarr.cc \
--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 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.