From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
matthew.auld@intel.com
Subject: [Intel-gfx] [PATCH 0/2] drm/i915, drm/ttm: Update the ttm_move_memcpy() interface
Date: Thu, 24 Jun 2021 21:30:43 +0200 [thread overview]
Message-ID: <20210624193045.5087-1-thomas.hellstrom@linux.intel.com> (raw)
The ttm_move_memcpy() function was intended to be able to be used async
under a fence.
We are going to utilize that as a fallback if the gpu clearing blit fails
before we set up CPU- or GPU ptes to the memory region.
But to accomplish that the bo argument to ttm_move_memcpy() needs to be
replaced.
Patch 1 reorganizes the i915 ttm move code a bit to make the change
in patch 2 smaller.
Patch 2 updates the ttm_move_memcpy() interface.
Thomas Hellström (2):
drm/i915/ttm: Reorganize the ttm move code somewhat
drm/ttm, drm/i915: Update ttm_move_memcpy for async use
drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 70 ++++++++++++++-----------
drivers/gpu/drm/ttm/ttm_bo_util.c | 20 +++----
include/drm/ttm/ttm_bo_driver.h | 2 +-
3 files changed, 51 insertions(+), 41 deletions(-)
--
2.31.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
matthew.auld@intel.com
Subject: [PATCH 0/2] drm/i915, drm/ttm: Update the ttm_move_memcpy() interface
Date: Thu, 24 Jun 2021 21:30:43 +0200 [thread overview]
Message-ID: <20210624193045.5087-1-thomas.hellstrom@linux.intel.com> (raw)
The ttm_move_memcpy() function was intended to be able to be used async
under a fence.
We are going to utilize that as a fallback if the gpu clearing blit fails
before we set up CPU- or GPU ptes to the memory region.
But to accomplish that the bo argument to ttm_move_memcpy() needs to be
replaced.
Patch 1 reorganizes the i915 ttm move code a bit to make the change
in patch 2 smaller.
Patch 2 updates the ttm_move_memcpy() interface.
Thomas Hellström (2):
drm/i915/ttm: Reorganize the ttm move code somewhat
drm/ttm, drm/i915: Update ttm_move_memcpy for async use
drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 70 ++++++++++++++-----------
drivers/gpu/drm/ttm/ttm_bo_util.c | 20 +++----
include/drm/ttm/ttm_bo_driver.h | 2 +-
3 files changed, 51 insertions(+), 41 deletions(-)
--
2.31.1
next reply other threads:[~2021-06-24 19:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 19:30 Thomas Hellström [this message]
2021-06-24 19:30 ` [PATCH 0/2] drm/i915, drm/ttm: Update the ttm_move_memcpy() interface Thomas Hellström
2021-06-24 19:30 ` [Intel-gfx] [PATCH 1/2] drm/i915/ttm: Reorganize the ttm move code somewhat Thomas Hellström
2021-06-24 19:30 ` Thomas Hellström
2021-06-30 14:19 ` [Intel-gfx] " Matthew Auld
2021-06-30 14:19 ` Matthew Auld
2021-06-30 15:27 ` [Intel-gfx] " Thomas Hellström
2021-06-30 15:27 ` Thomas Hellström
2021-06-30 16:54 ` [Intel-gfx] " Matthew Auld
2021-06-30 16:54 ` Matthew Auld
2021-06-30 17:00 ` [Intel-gfx] " Daniel Vetter
2021-06-30 17:00 ` Daniel Vetter
2021-06-24 19:30 ` [Intel-gfx] [PATCH 2/2] drm/ttm, drm/i915: Update ttm_move_memcpy for async use Thomas Hellström
2021-06-24 19:30 ` Thomas Hellström
2021-06-28 11:21 ` [Intel-gfx] " Thomas Hellström
2021-06-28 11:21 ` Thomas Hellström
2021-07-12 11:29 ` [Intel-gfx] " Christian König
2021-07-12 11:29 ` Christian König
2021-06-30 14:43 ` [Intel-gfx] " Matthew Auld
2021-06-30 14:43 ` Matthew Auld
2021-06-24 23:05 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915, drm/ttm: Update the ttm_move_memcpy() interface Patchwork
2021-06-25 7:39 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-06-25 21:22 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915, drm/ttm: Update the ttm_move_memcpy() interface (rev2) Patchwork
2021-06-25 22:27 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=20210624193045.5087-1-thomas.hellstrom@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 \
/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.