From: Matthew Auld <matthew.auld@intel.com>
To: Andrzej Hajda <andrzej.hajda@intel.com>, intel-gfx@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH v2 1/2] drm/i915: call i915_request_await_object from _i915_vma_move_to_active
Date: Wed, 16 Nov 2022 09:47:53 +0000 [thread overview]
Message-ID: <e850681f-a3d3-1f6c-0af7-3ce8ac24deaa@intel.com> (raw)
In-Reply-To: <3e63077f-2f62-7a52-21f7-095d1db5a7b5@intel.com>
On 15/11/2022 18:13, Andrzej Hajda wrote:
> On 08.11.2022 11:24, Matthew Auld wrote:
>> On 19/10/2022 22:59, Andrzej Hajda wrote:
>>> Since almost all calls to i915_vma_move_to_active are prepended with
>>> i915_request_await_object, let's call the latter from
>>> _i915_vma_move_to_active by default and add flag allowing bypassing it.
>>> Adjust all callers accordingly.
>>> The patch should not introduce functional changes.
>>>
>>> Signed-off-by: Andrzej Hajda <andrzej.hajda@intel.com>
>>
>> I thought someone already reviewed this series. Anyway,
>> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
>
> Gently ping for merge.
Pushed to gt-next. Thanks.
>
> Regards
> Andrzej
>
next prev parent reply other threads:[~2022-11-16 9:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 21:59 [Intel-gfx] [PATCH v2 0/2] drm/i915: refactor i915_vma_move_to_active Andrzej Hajda
2022-10-19 21:59 ` [Intel-gfx] [PATCH v2 1/2] drm/i915: call i915_request_await_object from _i915_vma_move_to_active Andrzej Hajda
2022-10-21 11:57 ` Tvrtko Ursulin
2022-11-08 10:24 ` Matthew Auld
2022-11-15 18:13 ` Andrzej Hajda
2022-11-16 9:47 ` Matthew Auld [this message]
2022-10-19 21:59 ` [Intel-gfx] [PATCH v2 2/2] drm/i915/selftests: add igt_vma_move_to_active_unlocked Andrzej Hajda
2022-11-08 10:28 ` Matthew Auld
2022-10-19 22:40 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: refactor i915_vma_move_to_active Patchwork
2022-10-19 23:02 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-10-21 13:52 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: refactor i915_vma_move_to_active (rev2) Patchwork
2022-10-21 23:17 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
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=e850681f-a3d3-1f6c-0af7-3ce8ac24deaa@intel.com \
--to=matthew.auld@intel.com \
--cc=andrzej.hajda@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=rodrigo.vivi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox