On Thu, Mar 21, 2013 at 12:25 PM, Kinney, Michael D <michael.d.kin...@intel.com> wrote: > Given that the only consumer of DEBUG_CLEAR_MEMORY() is the UEFI Memory > Manager in the DXE Core, I do not think adding more versions of it makes > sense. Another implementation option is to move the checks for clearing of > page zero into the implementation of the DEBUG_CLEAR_MEMORY() macro itself > and update the definition of DEBUG_CLEAR_MEMORY() to state that address range > 0x0-0xfff is ignored. >
I've thought about it more, and the SetMem means that avoiding the range for DEBUG_CLEAR_MEMORY does not matter. So, I'll give my Reviewed-by for the second change as well. -Jordan ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
