a9de470cc7
Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
33 lines
506 B
C
33 lines
506 B
C
/* SPDX-License-Identifier: BSD-3-Clause
|
|
* Copyright(c) 2010-2014 Intel Corporation
|
|
*/
|
|
|
|
#include <stdio.h>
|
|
#include <stdint.h>
|
|
|
|
#include <rte_prefetch.h>
|
|
|
|
#include "test.h"
|
|
|
|
/*
|
|
* Prefetch test
|
|
* =============
|
|
*
|
|
* - Just test that the macro can be called and validate the compilation.
|
|
* The test always return success.
|
|
*/
|
|
|
|
static int
|
|
test_prefetch(void)
|
|
{
|
|
int a;
|
|
|
|
rte_prefetch0(&a);
|
|
rte_prefetch1(&a);
|
|
rte_prefetch2(&a);
|
|
|
|
return 0;
|
|
}
|
|
|
|
REGISTER_TEST_COMMAND(prefetch_autotest, test_prefetch);
|