vlib: startup multi-arch variant configuration
Support for startup node multi-arch variant selection through startup.conf. This is to facilitate unit, functional testing and benchmarking of non-default multi-arch variant node code path. Also added parameters to make test, to specific using multi-arch variants in unit testing. Type: improvement Signed-off-by: Ray Kinsella <mdr@ashroe.eu> Change-Id: I94fd332bb629683b7a7dd770ee9f615a9a424060
This commit is contained in:

committed by
Damjan Marion

parent
a568a19b29
commit
4830e4f78f
@@ -380,6 +380,10 @@ help:
|
||||
@echo " TEST='bfd.BFDAPITestCase.test_add_bfd' selects a single test named test_add_bfd from test_bfd.py/BFDAPITestCase"
|
||||
@echo " TEST='*.*.test_add_bfd' selects all test functions named test_add_bfd from all files/classes"
|
||||
@echo ""
|
||||
@echo " VARIANT=<variant> - specify which march node variant to unit test"
|
||||
@echo " e.g. VARIANT=avx2 test the avx2 march variants"
|
||||
@echo " e.g. VARIANT=avx512 test the avx512 march variants"
|
||||
@echo ""
|
||||
@echo " VPP_ZOMBIE_NOCHECK=1 - skip checking for vpp (zombie) processes (CAUTION)"
|
||||
@echo " COREDUMP_SIZE=<size> - pass <size> as unix { coredump-size <size> } argument to vpp"
|
||||
@echo " e.g. COREDUMP_SIZE=4g"
|
||||
|
Reference in New Issue
Block a user