mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Documentation <linux-doc@vger.kernel.org>,
	Linux EFI <linux-efi@vger.kernel.org>
Cc: Ard Biesheuvel <ardb@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, Hugo Osvaldo Barrera <hugo@whynothugo.nl>
Subject: Re: [PATCH] x86/Documentation: explain LINUX_EFI_INITRD_MEDIA_GUID
Date: Wed, 10 Sep 2025 13:09:50 -0700	[thread overview]
Message-ID: <0C55A642-8BC8-4C19-9FF5-8B803E2CCABA@zytor.com> (raw)
In-Reply-To: <aMEUUkVQv2tqpO2L@archie.me>

On September 9, 2025 11:01:54 PM PDT, Bagas Sanjaya <bagasdotme@gmail.com> wrote:
>On Tue, Sep 09, 2025 at 08:25:34PM -0700, Randy Dunlap wrote:
>> On 9/9/25 6:57 PM, Bagas Sanjaya wrote:
>> > +.. _pe-coff-entry-point:
>> > +
>> > +PE/COFF entry point
>> > +===================
>> > +
>> > +When compiled with ``CONFIG_EFI_STUB=y``, the kernel can be executed as a
>> > +regular PE/COFF binary. See Documentation/admin-guide/efi-stub.rst for
>> > +implementation details.
>> > +
>> > +The stub loader can request the initrd via a UEFI protocol. For this to work,
>> > +the firmware or bootloader needs to register a handle which implements the
>> > +``EFI_LOAD_FILE2`` protocol with the ``LINUX_EFI_INITRD_MEDIA_GUID`` device
>> > +path. In this case, a kernel booting via the EFI stub will use the ``LoadFile``
>> > +function on the registered handle to obtain a reference to the initrd.
>> 
>> drivers/firmware/efi/libstub/efi-stub-helper.c (line 509) says LoadFile2
>> protocol. Is that the same as the LoadFile function?
>> 
>> https://github.com/u-boot/u-boot/commit/ec80b4735a593961fe701cc3a5d717d4739b0fd0
>> (the link below) also says LoadFile2() 4 times (and LoadFile 0 times).
>
>From UEFI spec [1], both LoadFile and LoadFile2 protocol versions of LoadFile()
>function has same prototype but somewhat different in behavior. To answer
>your question, however, I think so.
>
>EFI folks, what are your opinions?
>
>Thanks.
>
>[1]: https://uefi.org/specs/UEFI/2.10/13_Protocols_Media_Access.html
>

Sounds like the code was updated but not the documentation.

  reply	other threads:[~2025-09-10 20:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-10  1:57 Bagas Sanjaya
2025-09-10  3:25 ` Randy Dunlap
2025-09-10  6:01   ` Bagas Sanjaya
2025-09-10 20:09     ` H. Peter Anvin [this message]
2025-09-11  6:35       ` Ard Biesheuvel
2025-09-11  6:46 ` Ard Biesheuvel
2025-09-11 11:22   ` Hugo Osvaldo Barrera
2025-09-11 11:50     ` Bagas Sanjaya
2025-09-11 12:16       ` Hugo Osvaldo Barrera
2025-09-11 21:22         ` Randy Dunlap
2025-09-11 12:49     ` Ard Biesheuvel
2025-09-11 14:07       ` Hugo Osvaldo Barrera
2025-09-11 17:06         ` Ard Biesheuvel
2025-09-11 11:36   ` Bagas Sanjaya

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=0C55A642-8BC8-4C19-9FF5-8B803E2CCABA@zytor.com \
    --to=hpa@zytor.com \
    --cc=ardb@kernel.org \
    --cc=bagasdotme@gmail.com \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=hugo@whynothugo.nl \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rdunlap@infradead.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

all inboxes | Powered by JetHome®