When running the dmadev_autotest, run the suite of copy tests on the
skeleton driver created for API testing too, rather than just destroying
the driver instances once the API tests are complete. This helps to
sanity check the tests themselves are reasonable.
Signed-off-by: Bruce Richardson <bruce.richard...@intel.com>
Reviewed-by: Kevin Laatz <kevin.la...@intel.com>
---
app/test/test_dmadev.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/app/test/test_dmadev.c b/app/test/test_dmadev.c
index f4537a87c1..b0fba1d84e 100644
--- a/app/test/test_dmadev.c
+++ b/app/test/test_dmadev.c
@@ -254,14 +254,13 @@ test_apis(void)
int id;
int ret;
- if (rte_vdev_init(pmd, NULL) < 0)
- return TEST_SKIPPED;
+ /* attempt to create skeleton instance - ignore errors due to one being
already present */
+ rte_vdev_init(pmd, NULL);
id = rte_dma_get_dev_id_by_name(pmd);
if (id < 0)
return TEST_SKIPPED;
printf("\n### Test dmadev infrastructure using skeleton driver\n");
ret = test_dma_api(id);
- rte_vdev_uninit(pmd);
return ret;
}
--
2.30.2
