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: Fri, 22 Mar 2024 10:05:55 +0100 [thread overview]
Message-ID: <4t224udqjvt4kfg45skznhrj6n2ftez3eumgjerblbhl3iwv4c@zbvo45wwqksj> (raw)
In-Reply-To: <IA0PR11MB8355BD60B5E48880B4FA8280E7312@IA0PR11MB8355.namprd11.prod.outlook.com>
On Fri, Mar 22, 2024 at 08:29:28AM +0000, Sun, CepingX wrote:
> On Thursday, March 21, 2024 8:25 PM Gerd Hoffmann wrote:
> > Well, just try to read them. If present they can just be measured.
> > If not present we can either skip them, or measure with an empty data
> > field to indicate it is not present.
> My understanding :
> If the fw_cfg is present, it must be measured and consumed later.
> Is this correct?
I think that would be the best strategy. In SEC or early PEI read the
items, cache them in HOBs, optionally measure them.
When consumed just fetch them from the cache. For entries we are
measuring caching is mandatory (to make sure we are actually using
the same data we have measured).
> > But then you have to find and update all callsites (or at least the
> > ones where we care about measurement).
> In your solution, if we cache all items that need to be measured,
> we would have to add a new API (example: QemuFwCfgGetDataFromCache ()) to get the data from cache.
No, we only need to update QemuFwCfgSelectItem + QemuFwCfgReadBytes to
support reading from the cache.
QemuFwCfgGetDataFromCache() can be added as additional API, and
callsites have the option to either switch over, or continue to
use the existing API.
take care,
Gerd
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#117032): https://edk2.groups.io/g/devel/message/117032
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-22 9:06 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
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 [this message]
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=4t224udqjvt4kfg45skznhrj6n2ftez3eumgjerblbhl3iwv4c@zbvo45wwqksj \
--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