From: "Laszlo Ersek" <lersek@redhat.com>
To: "Li, Walon" <walon.li@hpe.com>,
gaoliming <gaoliming@byosoft.com.cn>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Wang, Sunny (HPS SW)" <sunnywang@hpe.com>,
"ray.ni@intel.com" <ray.ni@intel.com>,
"hao.a.wu@intel.com" <hao.a.wu@intel.com>
Subject: Re: [edk2-devel] [PATCH] MdeModulePkg/UefiBootManagerLib: Put BootMenu at the end of BootOrder
Date: Fri, 19 Feb 2021 16:52:25 +0100 [thread overview]
Message-ID: <4d25bf28-e147-365a-64d4-6ecf0a1184d2@redhat.com> (raw)
In-Reply-To: <CS1PR8401MB0951477CC3A501DCB420EFD698849@CS1PR8401MB0951.NAMPRD84.PROD.OUTLOOK.COM>
On 02/19/21 02:33, Li, Walon wrote:
> Hi Liming,
>
> As edk2 design, any new boot options should be put at the end of BootOrder because these are NEW . That means system should "append" BootOrder instead of override original order.
> For example, if system has three boot options currently - Boot0001, Boot0002, Boot0003 and then one new option - Boot0000 will be added. The order should become Boot0001,Boot0002,Boot0003,Boot0000. However, in this case, BootmanagerMenu doesn't follow this rule. We set "zero" priority so system would put BootManagerMenu boot option at start.
> This case is a corner case because the symptom only be gotten when user delete BootManagerMenu on OS or EFI shell. But it's a possible case. For keeping behavior consistent, we should keep BootManagerMenu option behavior as same as others boot option.
>
> Thanks
> Walon
>
> -----Original Message-----
> From: gaoliming <gaoliming@byosoft.com.cn>
> Sent: Friday, February 19, 2021 8:59 AM
> To: devel@edk2.groups.io; Li, Walon <walon.li@hpe.com>
> Cc: Wang, Sunny (HPS SW) <sunnywang@hpe.com>; lersek@redhat.com; ray.ni@intel.com; hao.a.wu@intel.com
> Subject: 回复: [edk2-devel] [PATCH] MdeModulePkg/UefiBootManagerLib: Put BootMenu at the end of BootOrder
>
> Walon:
> Can you specify the detail reason why BootManagerMenu should be placed at end of BootOrder?
In addition to Walon's answer, I'd like to point out that the current
code doesn't seem to explain why BootManagerMenu was ever placed at the
front.
Of course when we change code, the burden of justification is on the
patch that's being proposed; so I agree with the question.
However, answering that question is easier if the pre-patch code has an
explicit explanation, and that explanation can be shown to be wrong (or
at least to have missed a corner case or similar). If the pre-patch code
is undocumented, then arguing for the new code is more difficult.
Laszlo
next prev parent reply other threads:[~2021-02-19 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 3:26 [PATCH] MdeModulePkg/UefiBootManagerLib: Put BootMenu at the end of BootOrder Li, Walon
2021-02-19 0:58 ` 回复: [edk2-devel] " gaoliming
2021-02-19 1:33 ` Li, Walon
2021-02-19 15:52 ` Laszlo Ersek [this message]
2021-02-20 5:43 ` 回复: " gaoliming
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=4d25bf28-e147-365a-64d4-6ecf0a1184d2@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