From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: Masahisa Kojima <masahisa.kojima@linaro.org>
Cc: u-boot@lists.denx.de, Heinrich Schuchardt <xypron.glpk@gmx.de>,
Simon Glass <sjg@chromium.org>,
Takahiro Akashi <takahiro.akashi@linaro.org>
Subject: Re: [PATCH v4 5/8] efi_loader: set EFI HTTP Boot download buffer as reserved
Date: Mon, 25 Sep 2023 15:46:11 +0300 [thread overview]
Message-ID: <ZRGBE9HUjLB8f7lS@hera> (raw)
In-Reply-To: <20230922071119.1439482-6-masahisa.kojima@linaro.org>
Kojima-san,
[...]
> /* Carve out DT reserved memory ranges */
> void efi_carve_out_dt_rsv(void *fdt);
> /* Purge unused kaslr-seed */
> diff --git a/lib/efi_loader/efi_bootmgr.c b/lib/efi_loader/efi_bootmgr.c
> index 605be5041e..4991056946 100644
> --- a/lib/efi_loader/efi_bootmgr.c
> +++ b/lib/efi_loader/efi_bootmgr.c
> @@ -326,6 +326,11 @@ static efi_status_t try_load_from_uri_path(struct efi_device_path_uri *uridp,
> return EFI_INVALID_PARAMETER;
>
> ret = load_default_file_from_blk_dev(blk, handle);
> + if (ret != EFI_SUCCESS)
> + return ret;
> +
> + /* whole ramdisk must be reserved */
> + efi_reserve_memory(image_addr, image_size, true);
Why is this a different patch though?
My concern is code duplication when we add similar functionality in
eficonfig. Isn't there a better place to handle the memory reservation?
[...]
Thanks
/Ilias
next prev parent reply other threads:[~2023-09-25 12:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 7:11 [PATCH v4 0/8] Add EFI HTTP boot support Masahisa Kojima
2023-09-22 7:11 ` [PATCH v4 1/8] net: wget: prevent overwriting reserved memory Masahisa Kojima
2023-09-25 10:50 ` Ilias Apalodimas
2023-09-22 7:11 ` [PATCH v4 2/8] net: wget: add wget with dns utility function Masahisa Kojima
2023-09-25 10:52 ` Ilias Apalodimas
2023-09-22 7:11 ` [PATCH v4 3/8] blk: blkmap: add ramdisk creation " Masahisa Kojima
2023-09-25 12:09 ` Ilias Apalodimas
2023-09-22 7:11 ` [PATCH v4 4/8] efi_loader: support boot from URI device path Masahisa Kojima
2023-09-25 12:37 ` Ilias Apalodimas
2023-09-26 3:01 ` Masahisa Kojima
2023-09-28 11:35 ` Maxim Uvarov
2023-09-29 2:13 ` Masahisa Kojima
2023-09-29 6:24 ` Maxim Uvarov
2023-09-29 7:00 ` Masahisa Kojima
2023-09-29 7:43 ` Maxim Uvarov
2023-09-22 7:11 ` [PATCH v4 5/8] efi_loader: set EFI HTTP Boot download buffer as reserved Masahisa Kojima
2023-09-25 12:46 ` Ilias Apalodimas [this message]
2023-09-26 3:11 ` Masahisa Kojima
2023-09-22 7:11 ` [PATCH v4 6/8] cmd: efidebug: add uri device path Masahisa Kojima
2023-09-22 7:11 ` [PATCH v4 7/8] doc: uefi: add HTTP Boot support Masahisa Kojima
2023-09-25 12:12 ` Ilias Apalodimas
2023-09-26 3:02 ` Masahisa Kojima
2023-09-22 7:11 ` [PATCH v4 8/8] efi_loader: create BlockIo device boot option Masahisa Kojima
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=ZRGBE9HUjLB8f7lS@hera \
--to=ilias.apalodimas@linaro.org \
--cc=masahisa.kojima@linaro.org \
--cc=sjg@chromium.org \
--cc=takahiro.akashi@linaro.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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