Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström (Intel)" <thomas_os@shipmail.org>
To: Ramalingam C <ramalingam.c@intel.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Cc: Hellstrom Thomas <thomas.hellstrom@intel.com>,
	Matthew Auld <matthew.auld@intel.com>
Subject: Re: [Intel-gfx] [PATCH v5 6/9] drm/i915/gt: offset handling for multiple copy engines
Date: Thu, 24 Mar 2022 17:20:28 +0100	[thread overview]
Message-ID: <6eebe04c-da24-600d-1c46-8ae341d7a061@shipmail.org> (raw)
In-Reply-To: <20220321224459.12223-7-ramalingam.c@intel.com>


On 3/21/22 23:44, Ramalingam C wrote:
> Handle the src and dst chunk offsets for different instances of the copy
> engines.
>
> Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
> ---
>   drivers/gpu/drm/i915/gt/intel_migrate.c | 3 +++
>   1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_migrate.c b/drivers/gpu/drm/i915/gt/intel_migrate.c
> index 39a5f8ae664d..5f6341f91622 100644
> --- a/drivers/gpu/drm/i915/gt/intel_migrate.c
> +++ b/drivers/gpu/drm/i915/gt/intel_migrate.c
> @@ -614,6 +614,9 @@ static int emit_copy(struct i915_request *rq,
>   	u32 instance = rq->engine->instance;
>   	u32 *cs;
>   
> +	src_offset += (u64)rq->engine->instance << 32;
> +	dst_offset += (u64)rq->engine->instance << 32;
> +

Again, these are nops since the offsets are 32-bit.

Also the instance selection is already handled in the functon, so I 
think this patch can be dropped.


>   	cs = intel_ring_begin(rq, ver >= 8 ? 10 : 6);
>   	if (IS_ERR(cs))
>   		return PTR_ERR(cs);

  reply	other threads:[~2022-03-24 16:20 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 22:44 [Intel-gfx] [PATCH v5 0/9] drm/i915/ttm: Evict and restore of compressed object Ramalingam C
2022-03-21 22:44 ` [Intel-gfx] [PATCH v5 1/9] drm/i915/gt: Use XY_FAST_COLOR_BLT to clear obj on graphics ver 12+ Ramalingam C
2022-03-22 10:10   ` Thomas Hellström
2022-03-21 22:44 ` [Intel-gfx] [PATCH v5 2/9] drm/i915/gt: Optimize the migration and clear loop Ramalingam C
2022-03-24 15:35   ` Thomas Hellström (Intel)
2022-03-21 22:44 ` [Intel-gfx] [PATCH v5 3/9] drm/i915/gt: Clear compress metadata for Flat-ccs objects Ramalingam C
2022-03-24 16:14   ` Thomas Hellström (Intel)
2022-03-28 18:59     ` Ramalingam C
2022-03-21 22:44 ` [Intel-gfx] [PATCH v5 4/9] drm/i915/selftest_migrate: Consider the possible roundup of size Ramalingam C
2022-03-21 22:44 ` [Intel-gfx] [PATCH v5 5/9] drm/i915/selftest_migrate: Check CCS meta data clear Ramalingam C
2022-03-21 22:44 ` [Intel-gfx] [PATCH v5 6/9] drm/i915/gt: offset handling for multiple copy engines Ramalingam C
2022-03-24 16:20   ` Thomas Hellström (Intel) [this message]
2022-03-28 18:56     ` Ramalingam C
2022-03-21 22:44 ` [Intel-gfx] [PATCH v5 7/9] drm/ttm: Add a parameter to add extra pages into ttm_tt Ramalingam C
2022-03-21 22:44 ` [Intel-gfx] [PATCH v5 8/9] drm/i915/gem: Add extra pages in ttm_tt for ccs data Ramalingam C
2022-03-24 16:28   ` Thomas Hellström
2022-03-28 18:57     ` Ramalingam C
2022-03-21 22:44 ` [Intel-gfx] [PATCH v5 9/9] drm/i915/migrate: Evict and restore the flatccs capable lmem obj Ramalingam C
2022-03-22 11:20   ` [Intel-gfx] [PATCH v6 " Ramalingam C
2022-03-22  1:47 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/ttm: Evict and restore of compressed object (rev3) Patchwork
2022-03-22  1:49 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-22  1:53 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2022-03-22  2:16 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-03-22 12:02 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/ttm: Evict and restore of compressed object (rev4) Patchwork
2022-03-22 12:04 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-22 12:08 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2022-03-22 12:34 ` [Intel-gfx] ✗ Fi.CI.BAT: 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=6eebe04c-da24-600d-1c46-8ae341d7a061@shipmail.org \
    --to=thomas_os@shipmail.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.auld@intel.com \
    --cc=ramalingam.c@intel.com \
    --cc=thomas.hellstrom@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