Re: [Intel-gfx] [PATCH 12/21] drm/i915: Mark up address spaces that may need to allocate

Quoting Tvrtko Ursulin (2019-09-25 16:59:26) > > On 25/09/2019 09:23, Chris Wilson wrote: > > Quoting Tvrtko Ursulin (2019-09-23 09:10:26) > >> > >> On 20/09/2019 17:35, Chris Wilson wrote: > >>> Quoting Tvrtko Ursulin (2019-09-20 17:22:42) > > On 02/09/2019 05:02, Chris Wilson wrote: >

Re: [Intel-gfx] [PATCH 12/21] drm/i915: Mark up address spaces that may need to allocate

On 25/09/2019 09:23, Chris Wilson wrote: Quoting Tvrtko Ursulin (2019-09-23 09:10:26) On 20/09/2019 17:35, Chris Wilson wrote: Quoting Tvrtko Ursulin (2019-09-20 17:22:42) On 02/09/2019 05:02, Chris Wilson wrote: Since we cannot allocate underneath the vm->mutex (it is used in the

Re: [Intel-gfx] [PATCH 12/21] drm/i915: Mark up address spaces that may need to allocate

Quoting Tvrtko Ursulin (2019-09-23 09:10:26) > > On 20/09/2019 17:35, Chris Wilson wrote: > > Quoting Tvrtko Ursulin (2019-09-20 17:22:42) > >> > >> On 02/09/2019 05:02, Chris Wilson wrote: > >>> Since we cannot allocate underneath the vm->mutex (it is used in the > >>> direct-reclaim paths), we

Re: [Intel-gfx] [PATCH 12/21] drm/i915: Mark up address spaces that may need to allocate

On 20/09/2019 17:35, Chris Wilson wrote: Quoting Tvrtko Ursulin (2019-09-20 17:22:42) On 02/09/2019 05:02, Chris Wilson wrote: Since we cannot allocate underneath the vm->mutex (it is used in the direct-reclaim paths), we need to shift the allocations off into a mutexless worker with fence

Re: [Intel-gfx] [PATCH 12/21] drm/i915: Mark up address spaces that may need to allocate

Quoting Tvrtko Ursulin (2019-09-20 17:22:42) > > On 02/09/2019 05:02, Chris Wilson wrote: > > Since we cannot allocate underneath the vm->mutex (it is used in the > > direct-reclaim paths), we need to shift the allocations off into a > > mutexless worker with fence recursion prevention. To know

Re: [Intel-gfx] [PATCH 12/21] drm/i915: Mark up address spaces that may need to allocate

On 02/09/2019 05:02, Chris Wilson wrote: Since we cannot allocate underneath the vm->mutex (it is used in the direct-reclaim paths), we need to shift the allocations off into a mutexless worker with fence recursion prevention. To know when we need this protection, we mark up the address spaces

[Intel-gfx] [PATCH 12/21] drm/i915: Mark up address spaces that may need to allocate

Since we cannot allocate underneath the vm->mutex (it is used in the direct-reclaim paths), we need to shift the allocations off into a mutexless worker with fence recursion prevention. To know when we need this protection, we mark up the address spaces that do allocate before insertion.

[Intel-gfx] [PATCH 12/21] drm/i915: Mark up address spaces that may need to allocate

Since we cannot allocate underneath the vm->mutex (it is used in the direct-reclaim paths), we need to shift the allocations off into a mutexless worker with fence recursion prevention. To know when we need this protection, we mark up the address spaces that do allocate before insertion.