tests: unit tests for core/mem

We can exercise the memory subsystem through unit tests with a little
bit of coaxing. We need to create a number of fake data objects in order
to get it to build. This is less than ideal, but once we've got good
test coverage and confidence in our tests we can begin refactoring.

Had this unit test already been in place, commit 33c4ab1b ("mem: fix
regression in recent memscan changes") would have never been required
because buggy commit a1331f8d ("memscan: pass enum syslinux_memmap_types
around") would have broke the unit test. Ordinarily, this unit test
would have been part of the bugfix commit 33c4ab1b, but the bugfix needs
to be backported to 5.xx on its own.

test_mem_init_reserved() tests whether SMT_RESERVED regions are
incorrectly added to the memory subsystems's freelist.

Signed-off-by: Matt Fleming <matt.fleming@intel.com>

1 files changed, 1 insertions, 0 deletions

diff --git a/Makefile b/Makefile
index e9c16545..cceb66ef 100644
--- a/Makefile
+++ b/Makefile
@@ -103,6 +103,7 @@ $(filter-out $(private-targets), $(MAKECMDGOALS)):
 
 unittest:
 	printf "Executing unit tests\n"
+	$(MAKE) -C core/mem/tests all
 	$(MAKE) -C com32/lib/syslinux/tests all
 
 regression: