From: "Gerd Hoffmann" <kraxel@redhat.com>
To: "Sun, CepingX" <cepingx.sun@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Aktas, Erdem" <erdemaktas@google.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"Xu, Min M" <min.m.xu@intel.com>,
"Reshetova, Elena" <elena.reshetova@intel.com>
Subject: Re: [edk2-devel] [PATCH V1 1/1] OvmfPkg/QemuBootOrderLib: Measure the etc/boot-menu-wait
Date: Thu, 14 Mar 2024 10:30:35 +0100 [thread overview]
Message-ID: <pcavopv4ypqzu2fzvo36zqghty7jp7wyerclvdi24c7ayl3yzk@t4dfgrbskv3i> (raw)
In-Reply-To: <IA0PR11MB8355EB2E5953452721BEEBFEE72A2@IA0PR11MB8355.namprd11.prod.outlook.com>
Hi,
> > (3) Cache the measured data somewhere if needed multiple times
> > (or simply cache unconditionally).
> >
> Yes, agree.
> Cache the measured data into HOB in the PEI phase
> and cache the measured data into the global variables in the DXE phase.
> How about this?
Load, measure and cache all fw_cfg entries we care about early in the
PEI phase (or SEC phase for pei-less builds), so we can
(a) easily have a fixed order, and
(b) store them all in HOBs?
Which implies SEC/PEI must read all relevant fw_cfg entries, even in
case they are used only later in the DXE phase.
Advantage is we have a single cache which can be used in all firmware
phases. When using global variables in DXE we still can end up reading
entries multiple times, either because entries are needed by both PEI
and DXE, or because multiple DXE modules need them (global variables are
per module).
take care,
Gerd
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#116734): https://edk2.groups.io/g/devel/message/116734
Mute This Topic: https://groups.io/mt/104880546/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-03-14 9:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 23:51 [edk2-devel] [PATCH V1 1/1] OvmfPkg/QemuBootOrderLib: Measure the etc/boot-menu-wait sunceping
2024-03-12 7:57 ` Yao, Jiewen
2024-03-13 8:39 ` sunceping
2024-03-12 11:04 ` Gerd Hoffmann
2024-03-13 8:50 ` sunceping
2024-03-14 9:30 ` Gerd Hoffmann [this message]
2024-03-20 8:41 ` sunceping
2024-03-20 10:04 ` Gerd Hoffmann
2024-03-21 8:39 ` sunceping
2024-03-21 12:25 ` Gerd Hoffmann
2024-03-22 8:29 ` sunceping
2024-03-22 9:05 ` Gerd Hoffmann
2024-03-26 9:08 ` sunceping
2024-03-26 15:44 ` Gerd Hoffmann
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=pcavopv4ypqzu2fzvo36zqghty7jp7wyerclvdi24c7ayl3yzk@t4dfgrbskv3i \
--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