i915: Perform execbuffer object locking as a
> separate step
>
> To help avoid evicting already resident buffers from the batch we're
> processing, perform locking as a separate step.
>
> Signed-off-by: Thomas Hellström
> ---
> .../gpu/drm/i915/gem/i915_gem_execbuffer.c
Op 15-06-2021 om 13:36 schreef Thomas Hellström:
> To help avoid evicting already resident buffers from the batch we're
> processing, perform locking as a separate step.
>
> Signed-off-by: Thomas Hellström
> ---
> .../gpu/drm/i915/gem/i915_gem_execbuffer.c| 25 ---
> 1 file ch
On 6/17/21 11:56 AM, Ramalingam C wrote:
On 2021-06-15 at 13:36:00 +0200, Thomas Hellström wrote:
To help avoid evicting already resident buffers from the batch we're
processing, perform locking as a separate step.
Looks reasonable to me.
Reviewed-by: Ramalingam C
Thanks for reviewing!
On 2021-06-15 at 13:36:00 +0200, Thomas Hellström wrote:
> To help avoid evicting already resident buffers from the batch we're
> processing, perform locking as a separate step.
>
Looks reasonable to me.
Reviewed-by: Ramalingam C
> Signed-off-by: Thomas Hellström
> ---
> .../gpu/drm/i915/gem/
To help avoid evicting already resident buffers from the batch we're
processing, perform locking as a separate step.
Signed-off-by: Thomas Hellström
---
.../gpu/drm/i915/gem/i915_gem_execbuffer.c| 25 ---
1 file changed, 21 insertions(+), 4 deletions(-)
diff --git a/drivers/
