From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
ramalingam.c@intel.com
Cc: matthew.auld@intel.com
Subject: Re: [Intel-gfx] [PATCH v3 10/12] drm/i915/ttm: accelerated move implementation
Date: Mon, 14 Jun 2021 19:55:03 +0200 [thread overview]
Message-ID: <0e309744-4d13-69de-2ad8-ee0df5cd46c1@linux.intel.com> (raw)
In-Reply-To: <20210614162612.294869-11-thomas.hellstrom@linux.intel.com>
On 6/14/21 6:26 PM, Thomas Hellström wrote:
> From: Ramalingam C <ramalingam.c@intel.com>
>
> Invokes the pipelined page migration through blt, for
> i915_ttm_move requests of eviction and also obj clear.
>
> Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
> ---
> v2:
> - subfunction for accel_move (Thomas)
> - engine_pm_get/put around context_move/clear (Thomas)
> - Invalidation at accel_clear (Thomas)
> v3:
> - conflict resolution s/&bo->mem/bo->resource/g
> ---
> drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 87 +++++++++++++++++++++----
> 1 file changed, 74 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
> index bf33724bed5c..08b72c280cb5 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
> @@ -15,6 +15,9 @@
> #include "gem/i915_gem_ttm.h"
> #include "gem/i915_gem_mman.h"
>
> +#include "gt/intel_migrate.h"
> +#include "gt/intel_engine_pm.h"
> +
> #define I915_PL_LMEM0 TTM_PL_PRIV
> #define I915_PL_SYSTEM TTM_PL_SYSTEM
> #define I915_PL_STOLEN TTM_PL_VRAM
> @@ -282,6 +285,61 @@ i915_ttm_resource_get_st(struct drm_i915_gem_object *obj,
> return intel_region_ttm_node_to_st(obj->mm.region, res);
> }
>
> +static int i915_ttm_accel_move(struct ttm_buffer_object *bo,
> + struct ttm_resource *dst_mem,
> + struct sg_table *dst_st)
> +{
> + struct drm_i915_private *i915 = container_of(bo->bdev, typeof(*i915),
> + bdev);
> + struct ttm_resource_manager *src_man =
> + ttm_manager_type(bo->bdev, bo->resource->mem_type);
> + struct drm_i915_gem_object *obj = i915_ttm_to_gem(bo);
> + struct sg_table *src_st;
> + struct i915_request *rq;
> + int ret;
> +
> + if (!i915->gt.migrate.context)
> + return -EINVAL;
> +
> + if (!bo->ttm || !ttm_tt_is_populated(bo->ttm)) {
> + if (bo->type == ttm_bo_type_kernel)
> + return -EINVAL;
> +
> + if (bo->ttm &&
> + !(bo->ttm->page_flags & TTM_PAGE_FLAG_ZERO_ALLOC))
> + return 0;
> +
> + intel_engine_pm_get(i915->gt.migrate.context->engine);
> + ret = intel_context_migrate_clear(i915->gt.migrate.context, NULL,
> + dst_st->sgl, I915_CACHE_NONE,
> + dst_mem->mem_type >= TTM_PL_PRIV,
Here we should probably use I915_PL_LMEM0 instead of TTM_PL_PRIV, but
since this test will replaced by gpu_binds_iomem() in an upcoming
patch, doesn't matter really.
> + 0, &rq);
> +
> + if (!ret && rq) {
> + i915_request_wait(rq, 0, HZ);
Could be a MAX_SCHEDULE_TIMEOUT here to avoid surprises in case the
queue to the blitter is getting long?
> + i915_request_put(rq);
> + }
> + intel_engine_pm_put(i915->gt.migrate.context->engine);
> + } else {
> + src_st = src_man->use_tt ? i915_ttm_tt_get_st(bo->ttm) :
> + obj->ttm.cached_io_st;
> +
> + intel_engine_pm_get(i915->gt.migrate.context->engine);
> + ret = intel_context_migrate_copy(i915->gt.migrate.context,
> + NULL, src_st->sgl, I915_CACHE_NONE,
> + bo->resource->mem_type >= TTM_PL_PRIV,
> + dst_st->sgl, I915_CACHE_NONE,
> + dst_mem->mem_type >= TTM_PL_PRIV, &rq);
> + if (!ret && rq) {
> + i915_request_wait(rq, 0, HZ);
Same thing here.
With that fixed,
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
_______________________________________________
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-14 17:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 16:26 [Intel-gfx] [PATCH v3 00/12] i915 TTM sync accelerated migration and clear Thomas Hellström
2021-06-14 16:26 ` [Intel-gfx] [PATCH v3 01/12] drm/i915: Reference objects on the ww object list Thomas Hellström
2021-06-14 16:26 ` [Intel-gfx] [PATCH v3 02/12] drm/i915: Break out dma_resv ww locking utilities to separate files Thomas Hellström
2021-06-14 16:26 ` [Intel-gfx] [PATCH v3 03/12] drm/i915: Introduce a ww transaction helper Thomas Hellström
2021-06-14 16:26 ` [Intel-gfx] [PATCH v3 04/12] drm/i915/gt: Add an insert_entry for gen8_ppgtt Thomas Hellström
2021-06-14 16:26 ` [Intel-gfx] [PATCH v3 05/12] drm/i915/gt: Add a routine to iterate over the pagetables of a GTT Thomas Hellström
2021-06-14 16:26 ` [Intel-gfx] [PATCH v3 06/12] drm/i915/gt: Export the pinned context constructor and destructor Thomas Hellström
2021-06-14 16:26 ` [Intel-gfx] [PATCH v3 07/12] drm/i915/gt: Pipelined page migration Thomas Hellström
2021-06-15 14:45 ` Matthew Auld
2021-06-14 16:26 ` [Intel-gfx] [PATCH v3 08/12] drm/i915/gt: Pipelined clear Thomas Hellström
2021-06-15 14:47 ` Matthew Auld
2021-06-14 16:26 ` [Intel-gfx] [PATCH v3 09/12] drm/i915/gt: Setup a default migration context on the GT Thomas Hellström
2021-06-14 16:26 ` [Intel-gfx] [PATCH v3 10/12] drm/i915/ttm: accelerated move implementation Thomas Hellström
2021-06-14 17:55 ` Thomas Hellström [this message]
2021-06-15 10:06 ` [Intel-gfx] [PATCH v3] " Ramalingam C
2021-06-14 16:26 ` [Intel-gfx] [PATCH v3 11/12] drm/i915/gem: Zap the client blt code Thomas Hellström
2021-06-14 16:33 ` Matthew Auld
2021-06-14 16:40 ` Thomas Hellström
2021-06-14 16:26 ` [Intel-gfx] [PATCH v3 12/12] drm/i915/gem: Zap the i915_gem_object_blt code Thomas Hellström
2021-06-14 16:43 ` Matthew Auld
2021-06-15 0:55 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for i915 TTM sync accelerated migration and clear Patchwork
2021-06-15 1:24 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-06-15 10:19 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-06-15 11:45 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for i915 TTM sync accelerated migration and clear (rev2) 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=0e309744-4d13-69de-2ad8-ee0df5cd46c1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox