All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@csgraf.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] efi_loader: efi_runtime_detach()?
Date: Wed, 29 May 2019 12:13:32 +0200	[thread overview]
Message-ID: <24112a93-97f8-0460-1cf8-3aca811d3db0@csgraf.de> (raw)
In-Reply-To: <20190524071716.GA27279@linaro.org>


On 24.05.19 09:17, AKASHI Takahiro wrote:
> On Fri, May 24, 2019 at 07:27:11AM +0200, Heinrich Schuchardt wrote:
>> On 5/22/19 5:15 AM, AKASHI Takahiro wrote:
>>> Alex,
>>>
>>> It seems to me that the current efi_runtime_detach() has
>>> two meanings:
>>> * changes relating to the transition to virtual address mode
>>> * changes relating to exiting boot services
>>>
>>> In the current implementation, efi_runtime_detach() is
>>> called from efi_set_virtual_address_map() as those two
>>> purposes are apparently the same.
>>> For instance, however, systab.con_in/out/std_err/boottime are set
>>> to NULL in exit_boot_services() as well.
>>> Logically, efi_get_variable() won't work as U-Boot environment data
>>> can be potentially re-used at any time after exit_boot_services().
>>> The only meaningful change is to invalidate efi_set_virtual_address_map().
>>>
>>> So I believe that we should distinguish the two purposes
>>> and make appropriate changes in efi_set_virtual_address_map() and
>>> and exit_boot_services() respectively.
>>>
>>> This will be crucial particularly when I will add
>>> runtime variable support using "cache".
>>>
>>> Any thoughts?
>> Please, consider this pending patch from Alex:
>> https://patchwork.ozlabs.org/patch/1054074/
>> efi_loader: Patch non-runtime code out at ExitBootServices already
> @Alex, what is the current status of this patch?


I don't think I touched it ever since :). It's the right thing to do 
though. Care to debug why it breaks?


Alex

      reply	other threads:[~2019-05-29 10:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22  3:15 [U-Boot] efi_loader: efi_runtime_detach()? AKASHI Takahiro
2019-05-24  5:27 ` Heinrich Schuchardt
2019-05-24  7:17   ` AKASHI Takahiro
2019-05-29 10:13     ` Alexander Graf [this message]

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=24112a93-97f8-0460-1cf8-3aca811d3db0@csgraf.de \
    --to=agraf@csgraf.de \
    --cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.