From: "Ni, Ray" <ray.ni@intel.com>
To: "Wang, Fan" <fan.wang@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"Gao, Liming" <gaoliming@byosoft.com.cn>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "Jiang, Guomin" <guomin.jiang@intel.com>
Subject: Re: [edk2-devel] [PATCH V2 1/1] MdeModulePkg: Support customized FV Migration Information
Date: Tue, 5 Dec 2023 08:16:50 +0000 [thread overview]
Message-ID: <MN6PR11MB8244194381DD7157203E83DA8C85A@MN6PR11MB8244.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DM8PR11MB5752CA56FF3B2BD2ADDE34219786A@DM8PR11MB5752.namprd11.prod.outlook.com>
> I prefer to refine the hob usage to
> clude all ToMigrateFvInfo data in one hob (rather than each FV publish their
> own) and a field "MigrateAll" in this hob for those platforms who have no
> performance concern. In future, if we want to retire Migration feature PCD, we
> just need replace "check PCD TRUE or FALSE" with "check Hob exists or not".
> What do you think this way?
I am ok with your approach.
Each FV entry can tell two requests:
* Migrate FV or not
* Preserve RAW FV or not
As long as the global flag can provide the two information, I am ok😊
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#112069): https://edk2.groups.io/g/devel/message/112069
Mute This Topic: https://groups.io/mt/102908572/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2023-12-05 8:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1694425833.git.fan.wang@intel.com>
2023-09-11 9:51 ` [edk2-devel] [PATCH V2 1/1] MdeModulePkg: Support customized FV Migration Information Wang Fan
2023-10-16 20:59 ` Michael D Kinney
2023-10-27 8:23 ` Wang Fan
2023-11-20 6:30 ` Wang Fan
2023-12-01 1:01 ` 回复: " gaoliming via groups.io
2023-12-01 3:05 ` Ni, Ray
2023-12-04 10:31 ` Wang Fan
2023-12-04 11:46 ` 回复: " gaoliming via groups.io
2023-12-05 8:16 ` Ni, Ray [this message]
[not found] ` <1783CF665DB6E42F.23877@groups.io>
2023-09-22 5:32 ` Wang Fan
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=MN6PR11MB8244194381DD7157203E83DA8C85A@MN6PR11MB8244.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