From: Arvind Sankar <nivedita@alum.mit.edu>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-efi@vger.kernel.org, agraf@csgraf.de,
daniel.kiper@oracle.com, mjg59@google.com,
mbrown@fensystems.co.uk, hdegoede@redhat.com,
nivedita@alum.mit.edu, pjones@redhat.com, leif@nuviainc.com,
lersek@redhat.com, mingo@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 2/3] efi/x86: add true mixed mode entry point into .compat section
Date: Thu, 13 Feb 2020 11:59:03 -0500 [thread overview]
Message-ID: <20200213165902.GA1400002@rani.riverdale.lan> (raw)
In-Reply-To: <20200213145928.7047-3-ardb@kernel.org>
On Thu, Feb 13, 2020 at 03:59:27PM +0100, Ard Biesheuvel wrote:
> Currently, mixed mode is closely tied to the EFI handover protocol
> and relies on intimate knowledge of the bootparams structure, setup
> header etc, all of which are rather byzantine and entirely specific
> to x86.
>
> Even though no other EFI supported architectures are currently known
> that could support something like mixed mode, it makes sense to
> abstract a bit from this, and make it part of a generic Linux on EFI
> boot protocol.
>
> To that end, add a .compat section to the mixed mode binary, and populate
> it with the PE machine type and entry point address, allowing firmware
> implementations to match it to their native machine type, and invoke
> non-native binaries using a secondary entry point.
This patch refers to efi32_pe_entry which is only defined in the next
one.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-02-13 16:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 14:59 [RFC PATCH 0/3] efi/x86: add support for generic EFI mixed mode boot Ard Biesheuvel
2020-02-13 14:59 ` [RFC PATCH 1/3] efi/x86: drop redundant .bss section Ard Biesheuvel
2020-02-13 14:59 ` [RFC PATCH 2/3] efi/x86: add true mixed mode entry point into .compat section Ard Biesheuvel
2020-02-13 16:59 ` Arvind Sankar [this message]
2020-02-13 17:13 ` Ard Biesheuvel
2020-02-13 14:59 ` [RFC PATCH 3/3] efi/x86: implement mixed mode boot without the handover protocol Ard Biesheuvel
2020-02-13 17:23 ` Arvind Sankar
2020-02-13 17:42 ` Ard Biesheuvel
2020-02-13 17:53 ` [RFC PATCH 0/3] efi/x86: add support for generic EFI mixed mode boot Arvind Sankar
2020-02-13 17:55 ` Ard Biesheuvel
2020-02-13 18:47 ` Arvind Sankar
2020-02-13 22:36 ` Ard Biesheuvel
2020-02-14 0:10 ` Arvind Sankar
2020-02-14 0:12 ` Arvind Sankar
2020-02-14 0:21 ` Ard Biesheuvel
2020-02-14 0:38 ` Arvind Sankar
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=20200213165902.GA1400002@rani.riverdale.lan \
--to=nivedita@alum.mit.edu \
--cc=agraf@csgraf.de \
--cc=ardb@kernel.org \
--cc=daniel.kiper@oracle.com \
--cc=hdegoede@redhat.com \
--cc=leif@nuviainc.com \
--cc=lersek@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=mbrown@fensystems.co.uk \
--cc=mingo@kernel.org \
--cc=mjg59@google.com \
--cc=pjones@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;
as well as URLs for NNTP newsgroup(s).