public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, arvidjaar@gmail.com
Subject: Re: [edk2-devel] EFI Timeout variable is ignored (initialized to default on every boot)
Date: Mon, 13 Jul 2020 17:44:12 +0200	[thread overview]
Message-ID: <2c5ad688-fd7d-5211-e525-48cff7503905@redhat.com> (raw)
In-Reply-To: <824523a7-4c5e-5fae-66b5-2cc4bd4beb26@gmail.com>

Hi,

On 07/11/20 15:12, Andrei Borzenkov wrote:
> Using 202005 version I am not able to change "Boot Maintenance Manager"
> - "Auto Boot Time-out" or set Timeout variable from within Linux with
> efibootmgr - value is overwritten with default (normally 0) on every
> boot. The only possibility is to use -boot menu=on QEMU option. Looking
> at code, PlatformBootManagerBeforeConsole() unconditionally sets Timeout
> to value obtained from GetFrontPageTimeoutFromQemu() which in turn
> returns PcdPlatformBootTimeOut (default 0) if nothing was present on
> command line (or in general passed via fw_cfg).
> 
> I'd expect that default should be current value of Timeout unless
> overridden by command line/fw_cfg. It is OK to initialize it for the
> first time to PcdPlatformBootTimeOut if Timeout was not defined, but
> certainly not every time on every boot.

BdsDxe overwrites the Timeout non-volatile variable with
PcdPlatformBootTimeOut, before calling PlatformBootManagerBeforeConsole().

OvmfPkg platform code does not write to the Timeout non-volatile
variable. OvmfPkg platform code only sets PcdPlatformBootTimeOut (from
fw_cfg), but that happens only after BdsDxe has overwritten Timeout with
PcdPlatformBootTimeOut.

https://bugzilla.tianocore.org/show_bug.cgi?id=2488#c1

Laszlo


      reply	other threads:[~2020-07-13 15:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-11 13:12 EFI Timeout variable is ignored (initialized to default on every boot) Andrei Borzenkov
2020-07-13 15:44 ` Laszlo Ersek [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-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=2c5ad688-fd7d-5211-e525-48cff7503905@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