All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.auld@intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 1/2] drm/i915/ttm: Reorganize the ttm move code
Date: Tue, 2 Nov 2021 08:52:24 +0000	[thread overview]
Message-ID: <393737f9-5336-013c-8dc8-ab8f49f3d3f5@intel.com> (raw)
In-Reply-To: <20211101183851.291015-2-thomas.hellstrom@linux.intel.com>

On 01/11/2021 18:38, Thomas Hellström wrote:
> We are about to introduce failsafe- and asynchronous migration and
> ttm moves.
> This will add complexity and code to the TTM move code so it makes sense
> to split it out to a separate file to make the i915 TTM code easer to
> digest.
> Split the i915 TTM move code out and since we will have to change the name
> of the gpu_binds_iomem() and cpu_maps_iomem() functions anyway,
> we alter the name of gpu_binds_iomem() to i915_ttm_gtt_binds_lmem() which
> is more reflecting what it is used for.
> With this we also add some more documentation. Otherwise there should be
> no functional change.
> 
> Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>

WARNING: multiple messages have this Message-ID (diff)
From: Matthew Auld <matthew.auld@intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 1/2] drm/i915/ttm: Reorganize the ttm move code
Date: Tue, 2 Nov 2021 08:52:24 +0000	[thread overview]
Message-ID: <393737f9-5336-013c-8dc8-ab8f49f3d3f5@intel.com> (raw)
In-Reply-To: <20211101183851.291015-2-thomas.hellstrom@linux.intel.com>

On 01/11/2021 18:38, Thomas Hellström wrote:
> We are about to introduce failsafe- and asynchronous migration and
> ttm moves.
> This will add complexity and code to the TTM move code so it makes sense
> to split it out to a separate file to make the i915 TTM code easer to
> digest.
> Split the i915 TTM move code out and since we will have to change the name
> of the gpu_binds_iomem() and cpu_maps_iomem() functions anyway,
> we alter the name of gpu_binds_iomem() to i915_ttm_gtt_binds_lmem() which
> is more reflecting what it is used for.
> With this we also add some more documentation. Otherwise there should be
> no functional change.
> 
> Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>

  reply	other threads:[~2021-11-02  8:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-01 18:38 [PATCH v2 0/2] drm/i915: Failsafe migration blits Thomas Hellström
2021-11-01 18:38 ` [Intel-gfx] " Thomas Hellström
2021-11-01 18:38 ` [PATCH v2 1/2] drm/i915/ttm: Reorganize the ttm move code Thomas Hellström
2021-11-01 18:38   ` [Intel-gfx] " Thomas Hellström
2021-11-02  8:52   ` Matthew Auld [this message]
2021-11-02  8:52     ` Matthew Auld
2021-11-01 18:38 ` [PATCH v2 2/2] drm/i915/ttm: Failsafe migration blits Thomas Hellström
2021-11-01 18:38   ` [Intel-gfx] " Thomas Hellström
2021-11-02 13:55   ` Matthew Auld
2021-11-02 13:55     ` Matthew Auld
2021-11-02 14:14     ` Thomas Hellström
2021-11-02 14:14       ` [Intel-gfx] " Thomas Hellström
2021-11-01 22:33 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Failsafe migration blits (rev2) Patchwork
2021-11-01 23:05 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-11-02  2:59 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-11-02  5:58 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Failsafe migration blits (rev3) Patchwork
2021-11-02  6:29 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-11-02  7:47 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-11-02  8:18   ` Thomas Hellström
2021-11-02 15:41     ` Vudum, Lakshminarayana
2021-11-02 15:38 ` [Intel-gfx] ✓ Fi.CI.IGT: success " 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=393737f9-5336-013c-8dc8-ab8f49f3d3f5@intel.com \
    --to=matthew.auld@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=thomas.hellstrom@linux.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.