Re: [Mesa-dev] [RFC] New gallium flags for using different contexts in several threads

2016-12-18 Thread Axel Davy
On 18/12/2016 18:34, Nicolai Hähnle wrote: Then again, why not just call flush unconditionally? If the flush was unnecessary, it should be a no-op, and the driver should already have a fast path for that anyway. I just looked at radeon source with amdgpu, and it looks like to me a flush

Re: [Mesa-dev] [RFC] New gallium flags for using different contexts in several threads

2016-12-18 Thread Ilia Mirkin
On Sun, Dec 18, 2016 at 12:43 PM, Nicolai Hähnle wrote: > On 18.12.2016 17:40, Axel Davy wrote: >> >> On 18/12/2016 16:57, Nicolai Hähnle wrote: >>> >>> >>> >>> I'm happy to be convinced otherwise if I missed something, but using >>> multiple contexts from different threads,

Re: [Mesa-dev] [RFC] New gallium flags for using different contexts in several threads

2016-12-18 Thread Axel Davy
On 18/12/2016 18:34, Nicolai Hähnle wrote: On 18.12.2016 17:37, Axel Davy wrote: On 18/12/2016 16:57, Nicolai Hähnle wrote: On 18.12.2016 13:38, Axel Davy wrote: Currently there is no real specification on what is allowed for using different contexts in several threads, or when you map/unmap

Re: [Mesa-dev] [RFC] New gallium flags for using different contexts in several threads

2016-12-18 Thread Nicolai Hähnle
On 18.12.2016 17:40, Axel Davy wrote: On 18/12/2016 16:57, Nicolai Hähnle wrote: I'm happy to be convinced otherwise if I missed something, but using multiple contexts from different threads, or using Map/UnmapBuffer from one context but sourcing the buffer from draw calls in another context

Re: [Mesa-dev] [RFC] New gallium flags for using different contexts in several threads

2016-12-18 Thread Nicolai Hähnle
On 18.12.2016 17:37, Axel Davy wrote: On 18/12/2016 16:57, Nicolai Hähnle wrote: On 18.12.2016 13:38, Axel Davy wrote: Currently there is no real specification on what is allowed for using different contexts in several threads, or when you map/unmap a resource in a thread, but uses it in

Re: [Mesa-dev] [RFC] New gallium flags for using different contexts in several threads

2016-12-18 Thread Axel Davy
On 18/12/2016 16:57, Nicolai Hähnle wrote: I'm happy to be convinced otherwise if I missed something, but using multiple contexts from different threads, or using Map/UnmapBuffer from one context but sourcing the buffer from draw calls in another context are all perfectly supported OpenGL

Re: [Mesa-dev] [RFC] New gallium flags for using different contexts in several threads

2016-12-18 Thread Axel Davy
On 18/12/2016 16:57, Nicolai Hähnle wrote: On 18.12.2016 13:38, Axel Davy wrote: Currently there is no real specification on what is allowed for using different contexts in several threads, or when you map/unmap a resource in a thread, but uses it in another for draw calls. For the gallium

Re: [Mesa-dev] [RFC] New gallium flags for using different contexts in several threads

2016-12-18 Thread Nicolai Hähnle
On 18.12.2016 13:38, Axel Davy wrote: Currently there is no real specification on what is allowed for using different contexts in several threads, or when you map/unmap a resource in a thread, but uses it in another for draw calls. For the gallium nine CSMT patchset, I've figured out it would

[Mesa-dev] [RFC] New gallium flags for using different contexts in several threads

2016-12-18 Thread Axel Davy
Currently there is no real specification on what is allowed for using different contexts in several threads, or when you map/unmap a resource in a thread, but uses it in another for draw calls. For the gallium nine CSMT patchset, I've figured out it would be better to add flags to describe what