Hi,
Regarding EFIAPI calling convention, the UEFI 2.3.1 specification writes:
"All public interfaces of a UEFI module must follow the UEFI calling
convention. Public interfaces include the image entry point, UEFI event
handlers, and protocol member functions. The type EFIAPI is used to indicate
conformance to the calling conventions defined in this section. Non public
interfaces, such as private functions and static library calls, are not
required to follow the UEFI calling conventions and may be optimized by the
compiler"
Specifically I am interested in UEFI event handlers.
I have a function that registered with CreateEvent as a timer, and then
registered with SetTimer to be polled periodically.
So I understand this function (call it foo()) must have EFIAPI calling
convention (because it will be called periodically by the uefi system)
Do functions that are called by foo() also need to be in EFIAPI convention?
Specifically, every function that foo() calls, and all the functions those
functions call, and so forth, all need to be EFIAPI convention?
Thanks,
Ben.
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
