The only dependency PiSmmCpuDxeSmm actually has on CpuConfigLib is some type definitions from the library interface; that is, the header file. No functions are called and no extern variables are used from the library instance.
By not linking against CpuConfigLib in our PiSmmCpuDxeSmm port, we can also avoid importing the dynamic PCD "PcdCpuConfigContextBuffer" to OvmfPkg later on. That PCD is internal to the CpuConfigLib instance, and to such a portion of the Quark_EDKII_v1.1.0/IA32FamilyCpuBasePkg/CpuMpDxe driver that we are not going to rely on for bringing SMM to OVMF. Suggested-by: Paolo Bonzini <pbonz...@redhat.com> Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Laszlo Ersek <ler...@redhat.com> --- OvmfPkg/QuarkPort/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.inf | 1 - 1 file changed, 1 deletion(-) diff --git a/OvmfPkg/QuarkPort/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.inf b/OvmfPkg/QuarkPort/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.inf index 0e84a66..806c706 100644 --- a/OvmfPkg/QuarkPort/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.inf +++ b/OvmfPkg/QuarkPort/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.inf @@ -101,7 +101,6 @@ [LibraryClasses] MemoryAllocationLib DebugAgentLib HobLib - CpuConfigLib PciLib LocalApicLib UefiCpuLib -- 1.8.3.1 _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
