<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 13, 2015, at 3:24 PM, Edward Chicopee <<a href="mailto:edward.chicopee@gmail.com" class="">edward.chicopee@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class=""><div class=""><div class=""><div class="">After finding out OVMF doesn't do SMM (on the
EDK2-devel list), I decided to try working on a MinnowboardMax (hello
minnow list too!)<br class=""><br class=""></div>I can see with the MinnowboardMax serial port debug output that if I write 0x01 to port 0xB2, it prints some things like <br class="">"PiSmmCommunicationHandler Enter"<br class=""></div>"PiSmmCommunicationHandler CommunicateHeader - 0"<br class="">etc<br class=""></div>But when I search through the source code such lines don't seem to be present.<br class=""><br class="">Eventually I found that they exist in a binary-only package, MinMAX076\Vlv2BinaryPkg\IA32DEBUG\IA32\PiSmmCommunicationSmm.efi<br class=""></div>Running
strings on the binary seems to imply that it was linked against things
like MdePkg\Library\BaseDebugLibSerialPort\DebugLib.c<br class=""><br class="">As I did
with OVMF, I just put a "DebugPrint (0xFFFFFFFF, "Hi from SMM\n"); into
PiSmmCore.c. I see printout at boot time, but not at runtime upon
forcing an SMI. I assume this is because it's just using some DXE
DebugPrint which goes away at runtime? And I assume the reason the
binary package can continue to DebugPrint into runtime is because it has
(static?) linked against the DebugLib.c and so it contains all the code
it needs internally? Or maybe the serial port configuration gets screwed up at runtime? But then I would expect after the first PiSmmCommunicationHandler print for it to be reconfigured properly.<br class=""><br class=""></div>I can see that PiSmmCode.inf says
MdePkg/MdePkg.dec is under [Packages], and DebugLib is under
[LibraryClasses], so maybe it's some other reason I can't see my
DebugPrint in PiSmmCore.c at runtime only?<br class=""><div class=""><br class=""></div></div></div></blockquote><div><br class=""></div><div>Ed,</div><div><br class=""></div><div>The INF defines the Library Class (think API) that the driver consumes. There is not a 1:1 mapping between a Library Class (API) and a Library Instance (Implementation). </div><div><br class=""></div><div>The DSC defines the which Library Instance is linked against the driver. The idea is the library choices are pushed into the platform build, and don’t exist in the INF. So for example if you get Reference Code for the Silicon you don’t need to modify it to use a different debug scheme. </div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="">So any help on how to
see the print and/or (static?) link against the DebugLib.c that so </div></div></div></blockquote><div><br class=""></div><div>All linking in the edk2 is static linking. Dynamic stuff is all done in code via Protocols. </div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="">I can
keep printing at runtime would be very appreciated.<br class=""><br class=""></div></div></div></blockquote><div><br class=""></div><div>I don’t know the specifics of your platform but the best way to see what is going on is to generate a build report. You do this by adding a -y build.log to the build command. You can lookup the driver you care about and it will show you what libraries where used. If those libraries depended on libraries it will show you that too. </div><div><br class=""></div><div>A quick way to figure out the different DebugLib instances is to do something like:</div><div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures; color: #c33720" class="">~/work/src/edk2</span><span style="font-variant-ligatures: no-common-ligatures; color: #34bd26" class="">(master)</span><span style="font-variant-ligatures: no-common-ligatures; color: #afad24" class="">></span>git grep DebugLib -- *.inf | grep LIBRARY_CLASS </div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">ArmPkg/Library/SemiHostingDebugLib/SemiHostingDebugLib.inf:24: LIBRARY_CLASS = DebugLib|BASE SEC DXE_CORE DXE_DRIVER DXE_RUNTIME_DRIVER DXE_SAL_DRIVER DXE_SMM_DRIVER UEFI_APPLICATION UEFI_DRIVER</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">IntelFrameworkModulePkg/Library/PeiDxeDebugLibReportStatusCode/PeiDxeDebugLibReportStatusCode.inf:24: LIBRARY_CLASS = DebugLib|DXE_CORE DXE_DRIVER DXE_RUNTIME_DRIVER DXE_SAL_DRIVER DXE_SMM_DRIVER SMM_CORE PEIM SEC PEI_CORE UEFI_APPLICATION UEFI_DRIVER</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">IntelFspPkg/Library/BaseFspDebugLibSerialPort/BaseFspDebugLibSerialPort.inf:21: LIBRARY_CLASS = DebugLib</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">MdePkg/Library/BaseDebugLibNull/BaseDebugLibNull.inf:23: LIBRARY_CLASS = DebugLib </div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">MdePkg/Library/BaseDebugLibSerialPort/BaseDebugLibSerialPort.inf:24: LIBRARY_CLASS = DebugLib </div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">MdePkg/Library/UefiDebugLibConOut/UefiDebugLibConOut.inf:25: LIBRARY_CLASS = DebugLib|DXE_CORE DXE_DRIVER DXE_RUNTIME_DRIVER DXE_SAL_DRIVER DXE_SMM_DRIVER UEFI_APPLICATION UEFI_DRIVER </div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">MdePkg/Library/UefiDebugLibStdErr/UefiDebugLibStdErr.inf:25: LIBRARY_CLASS = DebugLib|DXE_CORE DXE_DRIVER DXE_RUNTIME_DRIVER DXE_SAL_DRIVER DXE_SMM_DRIVER UEFI_APPLICATION UEFI_DRIVER </div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">OvmfPkg/Library/PlatformDebugLibIoPort/PlatformDebugLibIoPort.inf:24: LIBRARY_CLASS = DebugLib</div><div class=""><br class=""></div></div><div>This will show you the set of Library Instances that produce the DebugLib LibraryClass, and what module types they support. </div><div><br class=""></div><div>Good luck,</div><div><br class=""></div><div>Andrew Fish</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="">Ed<br class=""></div></div>
------------------------------------------------------------------------------<br class="">Dive into the World of Parallel Programming. The Go Parallel Website,<br class="">sponsored by Intel and developed in partnership with Slashdot Media, is your<br class="">hub for all things parallel software development, from weekly thought<br class="">leadership blogs to news, videos, case studies, tutorials and more. Take a<br class="">look and join the conversation now. <a href="http://goparallel.sourceforge.net/_______________________________________________" class="">http://goparallel.sourceforge.net/_______________________________________________</a><br class="">edk2-devel mailing list<br class=""><a href="mailto:edk2-devel@lists.sourceforge.net" class="">edk2-devel@lists.sourceforge.net</a><br class="">https://lists.sourceforge.net/lists/listinfo/edk2-devel<br class=""></div></blockquote></div><br class=""></body></html>