Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrzej Hajda <andrzej.hajda@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
	Matthew Auld <matthew.auld@intel.com>,
	Andrzej Hajda <andrzej.hajda@intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [Intel-gfx] [PATCH v2 0/2] drm/i915: refactor i915_vma_move_to_active
Date: Wed, 19 Oct 2022 23:59:04 +0200	[thread overview]
Message-ID: <20221019215906.295296-1-andrzej.hajda@intel.com> (raw)

This patchset refactors code related to i915_vma_move_to_active.
I hope 1st patch is quite straightforward.
For the 2nd, I am not sure where to put the helper, any better proposition
welcome.

v2:
    - moved i915_request_await_object to _i915_vma_move_to_active (Tvrtko)

Regards
Andrzej


Andrzej Hajda (2):
  drm/i915: call i915_request_await_object from _i915_vma_move_to_active
  drm/i915/selftests: add igt_vma_move_to_active_unlocked

 .../gpu/drm/i915/gem/i915_gem_execbuffer.c    | 17 ++++-----
 .../i915/gem/selftests/i915_gem_client_blt.c  | 22 +++---------
 .../i915/gem/selftests/i915_gem_coherency.c   |  4 +--
 .../drm/i915/gem/selftests/i915_gem_context.c | 16 +++------
 .../drm/i915/gem/selftests/i915_gem_mman.c    | 10 ++----
 .../drm/i915/gem/selftests/igt_gem_utils.c    |  8 ++---
 .../drm/i915/gem/selftests/igt_gem_utils.h    | 14 ++++++++
 drivers/gpu/drm/i915/gt/intel_renderstate.c   |  4 +--
 drivers/gpu/drm/i915/gt/intel_workarounds.c   |  4 +--
 drivers/gpu/drm/i915/gt/selftest_execlists.c  | 14 ++------
 drivers/gpu/drm/i915/gt/selftest_hangcheck.c  | 35 +++----------------
 drivers/gpu/drm/i915/gt/selftest_lrc.c        | 33 ++++-------------
 drivers/gpu/drm/i915/gt/selftest_mocs.c       |  5 ++-
 drivers/gpu/drm/i915/gt/selftest_rps.c        |  8 ++---
 .../gpu/drm/i915/gt/selftest_workarounds.c    | 22 ++++--------
 drivers/gpu/drm/i915/gvt/scheduler.c          |  5 ++-
 drivers/gpu/drm/i915/i915_perf.c              |  4 +--
 drivers/gpu/drm/i915/i915_vma.c               |  5 +++
 drivers/gpu/drm/i915/i915_vma.h               |  1 +
 drivers/gpu/drm/i915/selftests/i915_request.c |  9 ++---
 drivers/gpu/drm/i915/selftests/igt_spinner.c  | 20 ++---------
 21 files changed, 77 insertions(+), 183 deletions(-)

-- 
2.34.1


             reply	other threads:[~2022-10-19 21:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 21:59 Andrzej Hajda [this message]
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
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=20221019215906.295296-1-andrzej.hajda@intel.com \
    --to=andrzej.hajda@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.auld@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