Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pingfan Liu <piliu@redhat.com>
To: kexec@lists.infradead.org
Cc: Pingfan Liu <piliu@redhat.com>, Simon Horman <horms@kernel.org>,
	Philipp Rudo <prudo@redhat.com>
Subject: [PATCH 0/3] Enable UKI image load on x86_64
Date: Tue,  5 Nov 2024 11:57:04 +0800	[thread overview]
Message-ID: <20241105035710.11384-1-piliu@redhat.com> (raw)

The correct kernel fd instead of UKI image fd should be
passed to the syscall. On arm64, it is not a problem, but on x86_64, it
is.(see commit log in 2/3)

This series aims to address the above problem.

Cc: Simon Horman <horms@kernel.org>
Cc: Philipp Rudo <prudo@redhat.com>
To: kexec@lists.infradead.org

Pingfan Liu (3):
  UKI: Split out the routine to create temporary fd
  kexec: Create a temporary file to hold .linux section in uki_probe()
  x86_64: Support UKI image format

 kexec/arch/arm64/kexec-vmlinuz-arm64.c |  2 +
 kexec/arch/x86_64/kexec-x86_64.c       |  1 +
 kexec/kexec-uki.c                      | 67 +++++++++++++++++---------
 3 files changed, 47 insertions(+), 23 deletions(-)

-- 
2.41.0


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

             reply	other threads:[~2024-11-05  3:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05  3:57 Pingfan Liu [this message]
2024-11-05  3:57 ` [PATCH 1/3] UKI: Split out the routine to create temporary fd Pingfan Liu
2024-11-05  3:57 ` [PATCH 2/3] kexec: Create a temporary file to hold .linux section in uki_probe() Pingfan Liu
2024-11-05  3:57 ` [PATCH 3/3] x86_64: Support UKI image format Pingfan Liu
2024-11-22  2:12 ` [PATCH 0/3] Enable UKI image load on x86_64 Dave Young
2024-12-02 13:06   ` Simon Horman
2024-12-02 13:34     ` Simon Horman

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=20241105035710.11384-1-piliu@redhat.com \
    --to=piliu@redhat.com \
    --cc=horms@kernel.org \
    --cc=kexec@lists.infradead.org \
    --cc=prudo@redhat.com \
    /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