summaryrefslogtreecommitdiffstats
path: root/IntelFspPkg/Tools
diff options
context:
space:
mode:
authorStar Zeng <star.zeng@intel.com>2015-06-02 10:20:13 +0000
committerlzeng14 <lzeng14@Edk2>2015-06-02 10:20:13 +0000
commitdccfb097ec73d1ae9b675e58a6909bb1f2df52ae (patch)
tree7be005b663142e7c2a7fc570df8807b633528845 /IntelFspPkg/Tools
parentf41c71d26a3ddeaf0f5e1442ab5f5eb87d951892 (diff)
downloadedk2-dccfb097ec73d1ae9b675e58a6909bb1f2df52ae.tar.gz
edk2-dccfb097ec73d1ae9b675e58a6909bb1f2df52ae.tar.bz2
edk2-dccfb097ec73d1ae9b675e58a6909bb1f2df52ae.zip
MdeModulepkg DxeSmmPerformanceLib: Dump all PEI/DXE/SMM performance data.
For boot performance dump, as current behavior. It depends on which PerformanceLib instance the DP application linked to. For example, if DxePerfrmanceLib(MdeModulePkg\Library\DxePerformanceLib) got linked, it will try to dump PEI and DXE performance data; and if DxeSmmPerfrmanceLib(MdeModulePkg\Library\DxeSmmPerformanceLib) got linked, then SMM performance data are expected. It has burden and confusion to developers about the DP application need to be linked to different PerformanceLib instance in *.dsc and rebuilt for the performance data dump. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Star Zeng <star.zeng@intel.com> Reviewed-by: Liming Gao <liming.gao@intel.com> git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@17548 6f19259b-4bc3-4df7-8a09-765794883524
Diffstat (limited to 'IntelFspPkg/Tools')
0 files changed, 0 insertions, 0 deletions