From: Daniel Kiper <daniel.kiper@oracle.com>
To: xen-devel@lists.xenproject.org
Cc: andrew.cooper3@citrix.com, jbeulich@suse.com
Subject: [PATCH RFC 0/7] Change xen.efi build and add SHIM_LOCK verification into efi_multiboot2()
Date: Sat, 8 Jul 2017 23:53:15 +0200 [thread overview]
Message-ID: <1499550803-25664-1-git-send-email-daniel.kiper@oracle.com> (raw)
Hey,
As in subject... This way we get:
- one binary which can be loaded by the EFI loader,
Multiboot and Multiboot2 protocols,
- if we wish, in the future we can drop xen/xen.gz
and build xen.efi only,
- crash dumps generated by the xen.efi loaded from
the EFI loader can be analyzed by crash tool,
- simpler code,
- simpler build,
- Xen build will no longer depend on ld i386pep support.
This is RFC, so, e.g. xen.mb.efi does not boot if loaded from EFI loader.
TODO:
- make xen.mb.efi bootable from EFI loader which probably requires
some changes in the code relocating trampoline,
- drop old PE build code,
- remove build recipes for old PE code,
- drop xen ELF build recipes (now or later?),
- cleanup the code.
Daniel
xen/Makefile | 14 ++++---
xen/arch/x86/Makefile | 1 +
xen/arch/x86/Rules.mk | 2 +
xen/arch/x86/boot/head.S | 197 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++----
xen/arch/x86/efi/efi-boot.h | 12 +++++-
xen/arch/x86/efi/stub.c | 5 ++-
xen/arch/x86/xen.lds.S | 16 ++++++-
xen/common/efi/boot.c | 19 ++++++---
xen/include/xen/compile.h.in | 1 +
9 files changed, 245 insertions(+), 22 deletions(-)
Daniel Kiper (7):
xen: Introduce XEN_COMPILE_POSIX_TIME
xen/x86: Manually build PE header
xen/x86: Add some addresses to the Multiboot header
xen/x86: Add some addresses to the Multiboot2 header
efi: split out efi_shim_lock()
xen/x86/efi: Verify dom0 kernel with SHIM_LOCK protocol in efi_multiboot2()
xen/x86: Build xen.mb.efi directly from xen-syms
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2017-07-08 21:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-08 21:53 Daniel Kiper [this message]
2017-07-08 21:53 ` [PATCH RFC 1/7] xen: Introduce XEN_COMPILE_POSIX_TIME Daniel Kiper
2018-04-30 15:56 ` Jan Beulich
2018-05-08 12:18 ` Daniel Kiper
2018-05-14 10:30 ` Jan Beulich
2018-05-14 16:25 ` Daniel Kiper
2018-05-15 7:47 ` Jan Beulich
2017-07-08 21:53 ` [PATCH RFC 2/7] xen/x86: Manually build PE header Daniel Kiper
2018-05-04 15:38 ` Jan Beulich
2018-05-08 12:47 ` Daniel Kiper
2018-05-14 10:40 ` Jan Beulich
2018-05-14 16:52 ` Daniel Kiper
2018-05-15 8:01 ` Jan Beulich
2017-07-08 21:53 ` [PATCH RFC 3/7] xen/x86: Add some addresses to the Multiboot header Daniel Kiper
2018-05-04 15:40 ` Jan Beulich
2018-05-08 13:01 ` Daniel Kiper
2017-07-08 21:53 ` [PATCH RFC 4/7] xen/x86: Add some addresses to the Multiboot2 header Daniel Kiper
2017-07-08 21:53 ` [PATCH RFC 5/7] efi: split out efi_shim_lock() Daniel Kiper
2017-07-08 21:53 ` [PATCH RFC 6/7] xen/x86/efi: Verify dom0 kernel with SHIM_LOCK protocol in efi_multiboot2() Daniel Kiper
2018-05-04 15:46 ` Jan Beulich
2018-05-08 13:09 ` Daniel Kiper
2018-05-14 10:43 ` Jan Beulich
2018-05-14 16:56 ` Daniel Kiper
2018-05-15 8:06 ` Jan Beulich
2017-07-08 21:53 ` [PATCH RFC 7/7] xen/x86: Build xen.mb.efi directly from xen-syms Daniel Kiper
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=1499550803-25664-1-git-send-email-daniel.kiper@oracle.com \
--to=daniel.kiper@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).