From: "sunceping" <cepingx.sun@intel.com>
To: "kraxel@redhat.com" <kraxel@redhat.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>,
"Sun, CepingX" <cepingx.sun@intel.com>
Subject: Re: [edk2-devel] [PATCH V1 1/1] OvmfPkg/QemuBootOrderLib: Measure the etc/boot-menu-wait
Date: Tue, 26 Mar 2024 09:08:59 +0000 [thread overview]
Message-ID: <IA0PR11MB8355A195E36F4F5BAF839E9AE7352@IA0PR11MB8355.namprd11.prod.outlook.com> (raw)
In-Reply-To: <4t224udqjvt4kfg45skznhrj6n2ftez3eumgjerblbhl3iwv4c@zbvo45wwqksj>
On Friday, March 22, 2024 5:06 PM Gerd Hoffmann wrote:
>
> > > 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.
Do you mean the existing API (QemuFwCfgSelectItem + QemuFwCfgReadBytes) need to be changed to support reading from the cache?
If that is the case, there are some concerns as below:
1: One or more new parameters (of QemuFwCfgReadBytes()) need to be added to search
the item in cache, which is equivalent to adding a new API.
2: The current QemuFwCfgReadBytes can read in chunks from qemu (example etc/e820)
If we call QemuFwCfgReadBytes to get data from cache , we also need to support reading in chunks.
Then we have to add more parameters ( to set offset). This will make the API more and more complicated.
> QemuFwCfgGetDataFromCache() can be added as additional API, and callsites have the option to either switch over, or continue to use the existing API.
Base above concerns, we think QemuFwCfgGetDataFromCache is must.
Thanks
Ceping
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#117105): https://edk2.groups.io/g/devel/message/117105
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-26 9:09 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
2024-03-26 9:08 ` sunceping [this message]
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=IA0PR11MB8355A195E36F4F5BAF839E9AE7352@IA0PR11MB8355.namprd11.prod.outlook.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