diff options
author | Dandan Bi <dandan.bi@intel.com> | 2018-07-02 13:29:52 +0800 |
---|---|---|
committer | Liming Gao <liming.gao@intel.com> | 2018-07-04 10:42:36 +0800 |
commit | dd3907f221fd9b774a5734cb7a000377acdfd5ca (patch) | |
tree | 6d25ebb62db0b49fd4fe34db1416c42fe90f95dd /BaseTools/Source/Python/UPT/GenMetaFile/GenXmlFile.py | |
parent | 5895956dd955714c0e578a413d0e289153cc9eea (diff) | |
download | edk2-dd3907f221fd9b774a5734cb7a000377acdfd5ca.tar.gz edk2-dd3907f221fd9b774a5734cb7a000377acdfd5ca.tar.bz2 edk2-dd3907f221fd9b774a5734cb7a000377acdfd5ca.zip |
MdeModulePkg/SmmCorePerformanceLib: Update mPerformanceLength
In mSmmBootPerformanceTable there are two parts,
one is the FPDT table header and the other is FPDT records.
Currently:
mPerformanceLength: The length of existing FPDT records.
mMaxPerformanceLength: The maximum length allocated for
mSmmBootPerformanceTable(including FPDT table header length
and existing FPDT records length)
But when compare mPerformanceLength with mMaxPerformanceLength
to check whether need to allocate new buffer for new FPDT
record, we miss to add mPerformanceLength with header length,
which will cause pool allocation behavior is not correct.
Now update the mPerformanceLength to fix this issue:
updated mPerformanceLength = FPDT table header length
+ existing FPDT records length.
Cc: Liming Gao <liming.gao@intel.com>
Cc: Star Zeng <star.zeng@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Dandan Bi <dandan.bi@intel.com>
Reviewed-by: Liming Gao <liming.gao@intel.com>
Diffstat (limited to 'BaseTools/Source/Python/UPT/GenMetaFile/GenXmlFile.py')
0 files changed, 0 insertions, 0 deletions