public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: Ray Ni <ray.ni@intel.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	edk2-devel-groups-io <devel@edk2.groups.io>
Subject: setting PcdPlatformBootTimeOut in PlatformBootManagerLib
Date: Mon, 2 Mar 2020 00:13:11 +0100	[thread overview]
Message-ID: <fef62d68-37c8-b2ea-5587-32532f1f2479@redhat.com> (raw)

Hi Ray,

OvmfPkg and ArmVirtPkg platforms set PcdPlatformBootTimeOut in their
PlatformBootManagerLib instances, in BeforeConsole(). This generally
works, except for one aspect: in BdsEntry(), the Timeout UEFI variable
is set from the PCD before BeforeConsole() is called.

The Timeout variable is in this case purely informative, but I'd still
like it to reflect the PCD's value. Given that I'd like to keep the
subject PcdSet16S() call in PlatformBootManagerLib, I see two options:

(1) Modify BdsEntry(): re-check the value of the PCD a bit before
BdsWait() -- when the PCD is really needed --, and if it has changed
relative to the first seen value, store the new PCD value to the UEFI
variable *again*.

This would keep platforms happy that expect Timeout to already carry the
PCDs value upon entering BeforeConsole(), and it would allow platforms
to re-set the PCD (and Timeout too) in either BeforeConsole() or
AfterConsole().

(2) Alternatively, add a CONSTRUCTOR function to the
PlatformBootManagerLib instances for setting the PCD before BdsEntry()
is invoked at all. I'm a bit concerned about this, as we'd have to
ensure that *all* the lib instances that participate in this PCD setting
(including the lib instances that let us calculate the value) have
CONSTRUCTOR functions (otherwise the topological sorting of CONSTRUCTOR
calls is not complete).

Thanks,
Laszlo


             reply	other threads:[~2020-03-01 23:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-01 23:13 Laszlo Ersek [this message]
2020-03-02  9:40 ` setting PcdPlatformBootTimeOut in PlatformBootManagerLib Laszlo Ersek
2020-03-02  9:43   ` Ard Biesheuvel
2020-03-02  9:45     ` Laszlo Ersek
2020-03-02  9:47       ` [edk2-devel] " 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=fef62d68-37c8-b2ea-5587-32532f1f2479@redhat.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