On 2022-10-20 16:59, Christian König wrote: > Am 20.10.22 um 16:49 schrieb Michel Dänzer: >> On 2022-10-18 11:08, jiadong.zhu@xxxxxxx wrote: >>> From: "Jiadong.Zhu" <Jiadong.Zhu@xxxxxxx> >>> >>> The software ring is created to support priority context while there is only >>> one hardware queue for gfx. >>> >>> Every software ring has its fence driver and could be used as an ordinary ring >>> for the GPU scheduler. >>> Multiple software rings are bound to a real ring with the ring muxer. The >>> packages committed on the software ring are copied to the real ring. >>> >>> v2: Use array to store software ring entry. >>> v3: Remove unnecessary prints. >>> v4: Remove amdgpu_ring_sw_init/fini functions, >>> using gtt for sw ring buffer for later dma copy >>> optimization. >>> v5: Allocate ring entry dynamically in the muxer. >>> v6: Update comments for the ring muxer. >>> v7: Modify for function naming. >>> v8: Combine software ring functions into amdgpu_ring_mux.c >> I tested patches 1-4 of this series (since Christian clearly nacked patch 5). I hit the oops below. > > As long as you don't try to reset the GPU you can also test patch 5. Sure, I can test it once there's a fix for the oops. -- Earthling Michel Dänzer | https://redhat.com Libre software enthusiast | Mesa and Xwayland developer
