On 2021/9/3 23:38, Walsh, Conor wrote:
>
>> This is a tradeoff point. If we changed the log level of dmadev, it is
>> difficult to
>> know where the test case fails.
>>
>> So I prefer add more meaningful information, at least print out the function
>> name.
>>
>> And V19 add format function name
> This is a tradeoff point. If we changed the log level of dmadev, it is
> difficult to
> know where the test case fails.
>
> So I prefer add more meaningful information, at least print out the function
> name.
>
> And V19 add format function name in log default, so the rte_dmadev's log
> will
On 02/09/2021 14:13, Chengwen Feng wrote:
This patch add dmadev API test which based on 'dma_skeleton' vdev. The
test cases could be executed using 'dmadev_autotest' command in test
framework.
Signed-off-by: Chengwen Feng
Signed-off-by: Bruce Richardson
---
MAINTAINERS| 1 +
This is a tradeoff point. If we changed the log level of dmadev, it is
difficult to know where the test case fails.
So I prefer add more meaningful information, at least print out the function
name.
And V19 add format function name in log default, so the rte_dmadev's log will
show like:
rte_d
Hi Chengwen,
The output from the API tests is not very straightforward to interpret if you
are not familiar with these tests.
Could we change the log level of the dmadev library before and after the API
tests using something similar to
The code I have included inline below?
> +static int
> +te
This patch add dmadev API test which based on 'dma_skeleton' vdev. The
test cases could be executed using 'dmadev_autotest' command in test
framework.
Signed-off-by: Chengwen Feng
Signed-off-by: Bruce Richardson
---
MAINTAINERS| 1 +
app/test/meson.build | 4 +
app/tes
6 matches
Mail list logo
