[Mesa-dev] [PATCH 1/2] radeonsi: set a per-buffer flag that disables inter-process sharing (v4)

Nicolai Hähnle nhaehnle at gmail.com
Fri Sep 1 10:23:18 UTC 2017


On 01.09.2017 11:58, Michel Dänzer wrote:
> On 29/08/17 11:47 PM, Christian König wrote:
>> From: Marek Olšák <marek.olsak at amd.com>
>>
>> For lower overhead in the CS ioctl.
>> Winsys allocators are not used with interprocess-sharable resources.
>>
>> v2: It shouldn't crash anymore, but the kernel will reject the new flag.
>> v3 (christian): Rename the flag, avoid sending those buffers in the BO list.
>> v4 (christian): Remove setting the kernel flag for now
> 
> This change seems to have caused a GPU hang when running piglit on my
> Kaveri with the radeon kernel driver. Haven't been able to isolate it to
> a specific test, seems to only happen when running multiple tests
> concurrently. There's a GPUVM fault before the hang, I suspect it's related:
> 
> radeon 0000:00:01.0: GPU fault detected: 146 0x0ae6760c
> radeon 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x000001D7
> radeon 0000:00:01.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0607600C
> VM fault (0x0c, vmid 3) at page 471, read from 'CPF' (0x43504600) (118)
> 
> 
> Any ideas?

Only that "read from CPF" means it can only be one of:

- command buffers
- indirect draw data
- predication data (conditional render)

(I hope I didn't miss anything)

Hmm, actually, I think CI has unavoidable VM faults related to 
ARB_sparse_buffers, so this may be benign. You could try to exclude the 
ARB_sparse_buffers tests.

Cheers,
Nicolai
-- 
Lerne, wie die Welt wirklich ist,
Aber vergiss niemals, wie sie sein sollte.


More information about the mesa-dev mailing list