slimbootloader/PayloadPkg/OsLoader/PerformanceData.c

73 lines
1.4 KiB
C
Raw Normal View History

Use LF line endings in the repository Convert the line endings stored for all text files in the repository to LF. The majority previously used DOS-style CRLF line endings. Add a .gitattributes file to enforce this and treat certain extensions as never being text files. Update PatchCheck.py to insist on LF line endings rather than CRLF. However, its other checks fail on this commit due to lots of pre-existing complaints that it only notices because the line endings have changed. Silicon/QemuSocPkg/FspBin/Patches/0001-Build-QEMU-FSP-2.0-binaries.patch needs to be treated as binary since it contains a mixture of line endings. This change has implications depending on the client platform you are using the repository from: * Windows The usual configuration for Git on Windows means that text files will be checked out to the work tree with DOS-style CRLF line endings. If that's not the case then you can configure Git to do so for the entire machine with: git config --global core.autocrlf true or for just the repository with: git config core.autocrlf true Line endings will be normalised to LF when they are committed to the repository. If you commit a text file with only LF line endings then it will be converted to CRLF line endings in your work tree. * Linux, MacOS and other Unices The usual configuration for Git on such platforms is to check files out of the repository with LF line endings. This is probably the right thing for you. In the unlikely even that you are using Git on Unix but editing or compiling on Windows for some reason then you may need to tweak your configuration to force the use of CRLF line endings as described above. * General For more information see https://docs.github.com/en/get-started/getting-started-with-git/configuring-git-to-handle-line-endings . Fixes: https://github.com/slimbootloader/slimbootloader/issues/1400 Signed-off-by: Mike Crowe <mac@mcrowe.com>
2021-11-10 19:36:23 +08:00
/** @file
Copyright (c) 2017 - 2018, Intel Corporation. All rights reserved.<BR>
SPDX-License-Identifier: BSD-2-Clause-Patent
**/
#include "OsLoader.h"
/**
Decodes the description as per the provided Id.
@param[in] PerfId Id number to decode the string.
@retval String correspoding to the Id.
**/
STATIC
CHAR8 *
EFIAPI
LinuxPerfIdToStr (
IN UINT32 PerfId
)
{
switch (PerfId) {
case 0x4000:
return "Payload entry point";
case 0x4010:
return "OS loader main entry";
case 0x4020:
return "Shell exit";
case 0x4040:
return "Load image entry";
case 0x4050:
return "Boot device init";
case 0x4055:
return "Boot device tuning";
case 0x4060:
return "Parse partition info";
case 0x4070:
return "Load boot images";
case 0x4080:
OsLoader Cleanup (IAS) (#1778) * OsLoader: remove references to IAS images Change IAS references to 'Boot Image' since IAS support is deprecated. Signed-off-by: Atharva Lele <atharva.lele@intel.com> * ContainerLib: add container type defines Add comments to indicate the use cases of each container type Signed-off-by: Atharva Lele <atharva.lele@intel.com> * OsLoader: Use container defines instead of IAS defines This commit also changes some comments referencing IAS instead of a container. Signed-off-by: Atharva Lele <atharva.lele@intel.com> * OsLoader: remove ParseIasImage() since it is deprecated Remove deprecated functionality and header include. Signed-off-by: Atharva Lele <atharva.lele@intel.com> Signed-off-by: Chirag Vijay Kolhe <chirag.vijay.kolhe@intel.com> * OsLoader: add check for normal container type and fix comment NORMAL type of container is usually used with FV, regular ELF images, etc. This commit adds the check for it and removes the "non valid use case" comment. Signed-off-by: Atharva Lele <atharva.lele@intel.com> * GenContainer: add comments explaining container types Add comments explaining use cases of each container type Signed-off-by: Atharva Lele <atharva.lele@intel.com> * OsLoader: add a check for number of files in classic container Classic Container needs to have the boot file in it. According to the fixed order, this is the second file in the container. Add a check to make sure there are atleast 2 files before attempting boot. Signed-off-by: Atharva Lele <atharva.lele@intel.com> * QEMU: replace IAS references in boot options with container Clean up IAS reference from boot options list Signed-off-by: Atharva Lele <atharva.lele@intel.com> Signed-off-by: Atharva Lele <atharva.lele@intel.com> Signed-off-by: Chirag Vijay Kolhe <chirag.vijay.kolhe@intel.com>
2022-12-14 03:06:45 +08:00
return "Verify boot image";
Use LF line endings in the repository Convert the line endings stored for all text files in the repository to LF. The majority previously used DOS-style CRLF line endings. Add a .gitattributes file to enforce this and treat certain extensions as never being text files. Update PatchCheck.py to insist on LF line endings rather than CRLF. However, its other checks fail on this commit due to lots of pre-existing complaints that it only notices because the line endings have changed. Silicon/QemuSocPkg/FspBin/Patches/0001-Build-QEMU-FSP-2.0-binaries.patch needs to be treated as binary since it contains a mixture of line endings. This change has implications depending on the client platform you are using the repository from: * Windows The usual configuration for Git on Windows means that text files will be checked out to the work tree with DOS-style CRLF line endings. If that's not the case then you can configure Git to do so for the entire machine with: git config --global core.autocrlf true or for just the repository with: git config core.autocrlf true Line endings will be normalised to LF when they are committed to the repository. If you commit a text file with only LF line endings then it will be converted to CRLF line endings in your work tree. * Linux, MacOS and other Unices The usual configuration for Git on such platforms is to check files out of the repository with LF line endings. This is probably the right thing for you. In the unlikely even that you are using Git on Unix but editing or compiling on Windows for some reason then you may need to tweak your configuration to force the use of CRLF line endings as described above. * General For more information see https://docs.github.com/en/get-started/getting-started-with-git/configuring-git-to-handle-line-endings . Fixes: https://github.com/slimbootloader/slimbootloader/issues/1400 Signed-off-by: Mike Crowe <mac@mcrowe.com>
2021-11-10 19:36:23 +08:00
case 0x40A0:
OsLoader Cleanup (IAS) (#1778) * OsLoader: remove references to IAS images Change IAS references to 'Boot Image' since IAS support is deprecated. Signed-off-by: Atharva Lele <atharva.lele@intel.com> * ContainerLib: add container type defines Add comments to indicate the use cases of each container type Signed-off-by: Atharva Lele <atharva.lele@intel.com> * OsLoader: Use container defines instead of IAS defines This commit also changes some comments referencing IAS instead of a container. Signed-off-by: Atharva Lele <atharva.lele@intel.com> * OsLoader: remove ParseIasImage() since it is deprecated Remove deprecated functionality and header include. Signed-off-by: Atharva Lele <atharva.lele@intel.com> Signed-off-by: Chirag Vijay Kolhe <chirag.vijay.kolhe@intel.com> * OsLoader: add check for normal container type and fix comment NORMAL type of container is usually used with FV, regular ELF images, etc. This commit adds the check for it and removes the "non valid use case" comment. Signed-off-by: Atharva Lele <atharva.lele@intel.com> * GenContainer: add comments explaining container types Add comments explaining use cases of each container type Signed-off-by: Atharva Lele <atharva.lele@intel.com> * OsLoader: add a check for number of files in classic container Classic Container needs to have the boot file in it. According to the fixed order, this is the second file in the container. Add a check to make sure there are atleast 2 files before attempting boot. Signed-off-by: Atharva Lele <atharva.lele@intel.com> * QEMU: replace IAS references in boot options with container Clean up IAS reference from boot options list Signed-off-by: Atharva Lele <atharva.lele@intel.com> Signed-off-by: Atharva Lele <atharva.lele@intel.com> Signed-off-by: Chirag Vijay Kolhe <chirag.vijay.kolhe@intel.com>
2022-12-14 03:06:45 +08:00
return "Process boot image type";
Use LF line endings in the repository Convert the line endings stored for all text files in the repository to LF. The majority previously used DOS-style CRLF line endings. Add a .gitattributes file to enforce this and treat certain extensions as never being text files. Update PatchCheck.py to insist on LF line endings rather than CRLF. However, its other checks fail on this commit due to lots of pre-existing complaints that it only notices because the line endings have changed. Silicon/QemuSocPkg/FspBin/Patches/0001-Build-QEMU-FSP-2.0-binaries.patch needs to be treated as binary since it contains a mixture of line endings. This change has implications depending on the client platform you are using the repository from: * Windows The usual configuration for Git on Windows means that text files will be checked out to the work tree with DOS-style CRLF line endings. If that's not the case then you can configure Git to do so for the entire machine with: git config --global core.autocrlf true or for just the repository with: git config core.autocrlf true Line endings will be normalised to LF when they are committed to the repository. If you commit a text file with only LF line endings then it will be converted to CRLF line endings in your work tree. * Linux, MacOS and other Unices The usual configuration for Git on such platforms is to check files out of the repository with LF line endings. This is probably the right thing for you. In the unlikely even that you are using Git on Unix but editing or compiling on Windows for some reason then you may need to tweak your configuration to force the use of CRLF line endings as described above. * General For more information see https://docs.github.com/en/get-started/getting-started-with-git/configuring-git-to-handle-line-endings . Fixes: https://github.com/slimbootloader/slimbootloader/issues/1400 Signed-off-by: Mike Crowe <mac@mcrowe.com>
2021-11-10 19:36:23 +08:00
case 0x40B0:
return "Process ELF/MultiBoot";
case 0x40E0:
return "Kernel setup";
case 0x40F0:
return "TPM IndicateReadyToBoot";
case 0x4100:
return "FSP ReadyToBoot/EndOfFirmware notify";
Use LF line endings in the repository Convert the line endings stored for all text files in the repository to LF. The majority previously used DOS-style CRLF line endings. Add a .gitattributes file to enforce this and treat certain extensions as never being text files. Update PatchCheck.py to insist on LF line endings rather than CRLF. However, its other checks fail on this commit due to lots of pre-existing complaints that it only notices because the line endings have changed. Silicon/QemuSocPkg/FspBin/Patches/0001-Build-QEMU-FSP-2.0-binaries.patch needs to be treated as binary since it contains a mixture of line endings. This change has implications depending on the client platform you are using the repository from: * Windows The usual configuration for Git on Windows means that text files will be checked out to the work tree with DOS-style CRLF line endings. If that's not the case then you can configure Git to do so for the entire machine with: git config --global core.autocrlf true or for just the repository with: git config core.autocrlf true Line endings will be normalised to LF when they are committed to the repository. If you commit a text file with only LF line endings then it will be converted to CRLF line endings in your work tree. * Linux, MacOS and other Unices The usual configuration for Git on such platforms is to check files out of the repository with LF line endings. This is probably the right thing for you. In the unlikely even that you are using Git on Unix but editing or compiling on Windows for some reason then you may need to tweak your configuration to force the use of CRLF line endings as described above. * General For more information see https://docs.github.com/en/get-started/getting-started-with-git/configuring-git-to-handle-line-endings . Fixes: https://github.com/slimbootloader/slimbootloader/issues/1400 Signed-off-by: Mike Crowe <mac@mcrowe.com>
2021-11-10 19:36:23 +08:00
default:
return NULL;
}
}
/**
Wrapper function to print LinuxLoader Measure Point information.
**/
VOID
PrintLinuxMeasurePoint (
VOID
)
{
BL_PERF_DATA *PerfData;
PerfData = GetPerfDataPtr ();
PrintMeasurePoint (PerfData, LinuxPerfIdToStr);
}