From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Ramalingam C <ramalingam.c@intel.com>
Cc: intel-gfx@lists.freedesktop.org, matthew.auld@intel.com,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Perform execbuffer object locking as a separate step
Date: Thu, 17 Jun 2021 12:07:31 +0200 [thread overview]
Message-ID: <ee87e13a-4025-5745-28cb-dfc3d170ec64@linux.intel.com> (raw)
In-Reply-To: <20210617095620.GA15664@intel.com>
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 <ramalingam.c@intel.com>
>
>
Thanks for reviewing!
/Thomas
WARNING: multiple messages have this Message-ID (diff)
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Ramalingam C <ramalingam.c@intel.com>
Cc: intel-gfx@lists.freedesktop.org, matthew.auld@intel.com,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Perform execbuffer object locking as a separate step
Date: Thu, 17 Jun 2021 12:07:31 +0200 [thread overview]
Message-ID: <ee87e13a-4025-5745-28cb-dfc3d170ec64@linux.intel.com> (raw)
In-Reply-To: <20210617095620.GA15664@intel.com>
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 <ramalingam.c@intel.com>
>
>
Thanks for reviewing!
/Thomas
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-06-17 10:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 11:36 [PATCH] drm/i915: Perform execbuffer object locking as a separate step Thomas Hellström
2021-06-15 11:36 ` [Intel-gfx] " Thomas Hellström
2021-06-15 12:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-06-15 19:56 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-06-17 9:56 ` [PATCH] " Ramalingam C
2021-06-17 9:56 ` [Intel-gfx] " Ramalingam C
2021-06-17 10:07 ` Thomas Hellström [this message]
2021-06-17 10:07 ` Thomas Hellström
2021-06-17 10:19 ` Maarten Lankhorst
2021-06-17 10:19 ` [Intel-gfx] " Maarten Lankhorst
2021-06-17 15:35 ` Tang, CQ
2021-06-17 15:35 ` Tang, CQ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ee87e13a-4025-5745-28cb-dfc3d170ec64@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=ramalingam.c@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.