public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ardb@kernel.org>
To: Grzegorz Bernacki <gjb@semihalf.com>
Cc: devel@edk2.groups.io, leif@nuviainc.com,
	ardb+tianocore@kernel.org,  Samer.El-Haj-Mahmoud@arm.com,
	sunny.Wang@arm.com, mw@semihalf.com,  upstream@semihalf.com,
	pete@akeo.ie
Subject: Re: [edk2-platforms PATCH] Platform/RaspberryPi: Check for Boot Discovery Policy change.
Date: Tue, 31 Aug 2021 14:11:11 +0200	[thread overview]
Message-ID: <CAMj1kXEx3CCHfdn6i4bsjUff7=+x9sQDLU5DLP0n4=dXrqzqrQ@mail.gmail.com> (raw)
In-Reply-To: <20210818073811.3571796-1-gjb@semihalf.com>

On Wed, 18 Aug 2021 at 09:38, Grzegorz Bernacki <gjb@semihalf.com> wrote:
>
> This patch adds checks if Boot Discovery Policy has been
> changed. Only in that case EfiBootManagerRefreshAllBootOption()
> should be called.
>
> Signed-off-by: Grzegorz Bernacki <gjb@semihalf.com>

To be honest, I'm not a fan of this bodge. Can you explain why we need
two separate EFI variables to keep track of this state?


> ---
>  Platform/RaspberryPi/Library/PlatformBootManagerLib/PlatformBm.c | 24 +++++++++++++++++++-
>  1 file changed, 23 insertions(+), 1 deletion(-)
>
> diff --git a/Platform/RaspberryPi/Library/PlatformBootManagerLib/PlatformBm.c b/Platform/RaspberryPi/Library/PlatformBootManagerLib/PlatformBm.c
> index c8305ce4f5..378ba0ebf4 100644
> --- a/Platform/RaspberryPi/Library/PlatformBootManagerLib/PlatformBm.c
> +++ b/Platform/RaspberryPi/Library/PlatformBootManagerLib/PlatformBm.c
> @@ -617,6 +617,7 @@ BootDiscoveryPolicyHandler (
>  {
>    EFI_STATUS                       Status;
>    UINT32                           DiscoveryPolicy;
> +  UINT32                           DiscoveryPolicyOld;
>    UINTN                            Size;
>    EFI_BOOT_MANAGER_POLICY_PROTOCOL *BMPolicy;
>    EFI_GUID                         *Class;
> @@ -678,7 +679,28 @@ BootDiscoveryPolicyHandler (
>      return Status;
>    }
>
> -  EfiBootManagerRefreshAllBootOption();
> +  //
> +  // Refresh Boot Options if Boot Discovery Policy has been changed
> +  //
> +  Size = sizeof (DiscoveryPolicyOld);
> +  Status = gRT->GetVariable (
> +                  BOOT_DISCOVERY_POLICY_OLD_VAR,
> +                  &gBootDiscoveryPolicyMgrFormsetGuid,
> +                  NULL,
> +                  &Size,
> +                  &DiscoveryPolicyOld
> +                  );
> +  if ((Status == EFI_NOT_FOUND) || (DiscoveryPolicyOld != DiscoveryPolicy)) {
> +    EfiBootManagerRefreshAllBootOption();
> +
> +    Status = gRT->SetVariable (
> +                    BOOT_DISCOVERY_POLICY_OLD_VAR,
> +                    &gBootDiscoveryPolicyMgrFormsetGuid,
> +                    EFI_VARIABLE_NON_VOLATILE | EFI_VARIABLE_BOOTSERVICE_ACCESS,
> +                    sizeof (DiscoveryPolicyOld),
> +                    &DiscoveryPolicy
> +                    );
> +  }
>
>    return EFI_SUCCESS;
>  }
> --
> 2.25.1
>

  parent reply	other threads:[~2021-08-31 12:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18  7:38 [edk2-platforms PATCH] Platform/RaspberryPi: Check for Boot Discovery Policy change Grzegorz Bernacki
2021-08-18 19:42 ` Samer El-Haj-Mahmoud
2021-08-22 21:23 ` [edk2-devel] " Mario Bălănică
2021-08-31 12:11 ` Ard Biesheuvel [this message]
2021-09-01  8:45   ` Grzegorz Bernacki
2021-09-01  8:48     ` Ard Biesheuvel

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-list 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='CAMj1kXEx3CCHfdn6i4bsjUff7=+x9sQDLU5DLP0n4=dXrqzqrQ@mail.gmail.com' \
    --to=devel@edk2.groups.io \
    /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