MdeModulePkg: Optimize PEI Core Migration Algorithm #5875
Conversation
|
Have you collected the performance data with this change? |
awiralsh
force-pushed
the
Optimize_Migration_Algorithm
branch
3 times, most recently
from
99bf4f3
to
b9070cc
Compare
This may or may not improve performance depending on the behavior of temporary RAM and the actual performance changes must be measured with the feature enabled and disabled. |
I understand this change will improve the performance on the specific condition. Right? |
Yes, If the Temporary memory is faster than the permanent memory, this change improves the performance. |
REF : https://bugzilla.tianocore.org/show_bug.cgi?id=4750 Migrate the FV that doesn't contain the currently executing PEI Core when permanent memory is initialized but PEI Core is still potentially running from faster memory (Tepmorary RAM). This may reduce the time required to migrate FVs to permanent memory. The FV containing PEI Core is migrated after the PEI Core reentry when it is executed from permanent memory. This may or may not improve performance depending on the behavior of temporary RAM and the actual performance changes must be measured with the feature enabled and disabled. This migration algorithm is only used for FVs specified in the gEdkiiMigrationInfoGuid HOB and built with flag FLAGS_FV_MIGRATE_BEFORE_PEI_CORE_REENTRY. Signed-off-by: Awiral Shrivastava <[email protected]>
lgao4
force-pushed
the
Optimize_Migration_Algorithm
branch
from
b9070cc
to
bf6a551
Compare
Description
Migrate the FV that doesn't contain the currently executing PEI Core when memory is initialized but PEI Core is still potentially running from faster memory. This may reduce the time required to migrate FVs to permanent memory. The FV containing PEI Core is migrated after the PEI Core reentry when it is executed from permanent memory.
This migration algorithm is only used for FVs specified in the gEdkiiMigrationInfoGuid HOB.
How This Was Tested
Tested by tianocore edk2 CI