[PATCH 0/5] dma/ioat: fix issues with stopping and restarting device
Bruce Richardson
bruce.richardson at intel.com
Mon Jan 16 17:38:56 CET 2023
On Mon, Jan 16, 2023 at 04:09:19PM +0000, Walsh, Conor wrote:
> Hi Bruce,
>
> This patchset breaks the dmadev autotest for IOAT on IceLake.
>
> Trace below:
>
> ### Test dmadev instance 0 [0000:00:01.0] IOAT.status: ACTIVE
> [0x100242880] DMA Dev 0: Running copy Tests Ops submitted: 85120 Ops
> completed: 85120 Errors: 0 DMA Dev 0: Running stop-start Tests
> IOAT.status: ACTIVE [0x100242880] IOAT.status: ACTIVE [0x100242880] Ops
> submitted: 1 Ops completed: 1 Errors: 0 DMA Dev 0: Running
> burst capacity Tests Ops submitted: 65536 Ops completed: 65536
> Errors: 0 DMA Dev 0: Running error handling Tests (errors expected) In
> test_failure_in_full_burst:390 - Error, missing expected failed copy, 0.
> has_error is not set In runtest:58 - Error, not all submitted jobs are
> reported as completed In test_dma:940 - Error, test failure for device 0
> Test Faileded: 16 Ops completed: 0 Errors: 0 RTE>>IOAT:
> ioat_dmadev_remove(): Closing 0000:00:01.0 on NUMA node 0
>
> Thanks, Conor.
>
Thanks for catching this, Conor. I was testing on a system using noiommu
mode, so those error tests were getting skipped. I'll investigate and do a
v2.
/Bruce
More information about the dev
mailing list